@dv.nghiem/flowdeck 0.3.4 → 0.3.6

package/src/commands/fd-design.md

@@ -0,0 +1,64 @@
+---
+description: Design-first workflow for UI-heavy tasks — draft design artifacts, review implementation fidelity, or define design system rules
+argument-hint: [--mode=draft|review|system] [task-description] [--override]
+---
+
+# Design
+
+Run design-first workflow stages for user-facing tasks.
+
+**Input:** $ARGUMENTS — supports `--mode=draft|review|system` (default `draft`)
+
+## Mode: draft
+
+Use when creating/updating UI before implementation.
+
+### Required Stages
+
+1. discovery
+2. UX planning
+3. wireframe/layout planning
+4. visual system definition
+5. design approval
+6. implementation handoff
+
+### Process
+
+1. Classify task as UI-heavy (landing page, dashboard, admin panel, app screen, website/app UX)
+2. Delegate to `@design` agent for structured artifacts
+3. Persist outputs in planning state under `design_artifact`
+4. Mark:
+   - `requires_design_first: true`
+   - `design_stage: handoff_complete`
+   - `design_approved: true` only when approval criteria are met
+5. Record any bypass with explicit `design_override_reason`
+
+## Mode: review
+
+Use to review implemented UI against approved design artifact.
+
+### Process
+
+1. Load approved design artifact and changed UI files
+2. Delegate to `@design` with `design-audit` + `responsive-review`
+3. Report:
+   - design mismatches
+   - hierarchy/spacing issues
+   - CTA flow weaknesses
+   - responsive/accessibility concerns
+   - missing empty/error/loading/success states
+
+## Mode: system
+
+Use to generate/update design tokens and component behavior rules.
+
+### Process
+
+1. Delegate to `@design` with `design-system-definition`
+2. Generate/update token guidance and component rules
+3. Save summary in planning state `design_artifact.design_tokens_guidance`
+
+## Enforcement Notes
+
+- UI-heavy tasks must complete design approval before `/fd-execute`, unless `--override` is explicitly provided and logged.
+- Backend-only/infrastructure-only tasks skip this command.

package/src/commands/fd-discuss.md

@@ -50,6 +50,7 @@ Structure the discussion:
 2. **Constraints** — Technical constraints, deadlines, dependencies?
 3. **Acceptance criteria** — How will we know it's done?
 4. **Risks** — What could go wrong? Any known issues?
+5. **UI classification** — Is this task user-facing and UI-heavy (website/app/dashboard/admin/landing/onboarding)?
 
 Ask questions one at a time. Wait for answers before proceeding.
 
@@ -89,6 +90,7 @@ D-02: [Topic] — [Decision] ([Rationale])
 ## Completion
 
 Report: decisions captured, file path, and suggest running `/fd-plan`.
+If UI-heavy, also suggest running `/fd-design --mode=draft` before `/fd-execute`.
 
 ## Error Handling
 

package/src/commands/fd-execute.md

@@ -1,5 +1,5 @@
 ---
-description: Execute feature implementation from PLAN.md — TDD pipeline with coder, tester, reviewer, and STATE.md update
+description: Execute feature implementation from PLAN.md — TDD pipeline with backend-coder, frontend-coder, devops, tester, reviewer, and STATE.md update
 argument-hint: [--phase=N] [--override]
 ---
 
@@ -35,6 +35,10 @@ Verify prerequisites:
 - `.codebase/` directory exists
 - `STATE.md` has `plan_confirmed: true`
 - `PLAN.md` exists in current phase directory
+- If `requires_design_first: true`, require:
+  - `design_stage: handoff_complete`
+  - `design_approved: true`
+  - OR explicit `--override` with logged reason
 
 Initialize TDD state:
 ```yaml
@@ -79,7 +83,7 @@ Run failing tests:
 
 ### Step 7: Implement Minimum (GREEN)
 
-Spawn `@coder` to implement:
+Spawn the implementation agent selected by scope (`@backend-coder`, `@frontend-coder`, or `@devops`) to implement:
 - **Minimum code** to make failing tests pass
 - No speculative features
 - No over-engineering
@@ -160,7 +164,7 @@ User can override with `/fd-execute --override`:
 
 D-03: Fail fast with clear error
 - If guard check fails: abort with clear error and remediation
-- If @coder fails: report failure, offer retry or skip
+- If implementation agent fails: report failure, offer retry or skip
 - If @reviewer finds critical issues: return to Step 7 for fixes
 - No partial state saved on error
 

package/src/commands/fd-fix-bug.md

@@ -66,7 +66,7 @@ Confirm test fails. If it passes, the bug may already be fixed or the test is wr
 
 ### Step 7: GREEN — Implement Fix
 
-- **@coder**: Implement the minimum code change that makes the regression test pass
+- **Implementation agent (`@backend-coder` / `@frontend-coder` / `@devops`)**: Implement the minimum code change that makes the regression test pass
 - Do not refactor yet
 
 **GUARD: Do NOT proceed if test does not pass GREEN.**
@@ -101,7 +101,7 @@ Append entry to `.codebase/FAILURES.json`:
 
 ## Error Handling
 
-- **GUARD VIOLATION**: If coder attempts to skip RED or GREEN phase, block and return to correct phase
+- **GUARD VIOLATION**: If implementation agent attempts to skip RED or GREEN phase, block and return to correct phase
 - **Override mechanism**: User can override with `/fd-fix-bug --override` but every override is logged in `override_log`
 - If root cause unclear: spawn `@debug-specialist` for deeper analysis
 - If fix breaks tests: revert, reassess root cause, never suppress error

package/src/commands/fd-multi-repo.md

@@ -101,13 +101,13 @@ If any circular dependency is detected, the flow stops and reports the cycle. Ci
 
 Changes execute in dependency order. For each repo:
 
-1. `@coder` implements the changes in that repo
+1. Implementation agent (`@backend-coder`, `@frontend-coder`, or `@devops`) implements the changes in that repo based on scope
 2. `@tester` writes and runs tests for that repo's changes
 3. No downstream repo starts until the upstream repo's changes pass tests
 
-For non-breaking changes, `@coder` and `@tester` for a given repo run in parallel. For breaking changes, `@tester` must verify the upstream before `@coder` starts on any downstream.
+For non-breaking changes, implementation agent and `@tester` for a given repo run in parallel. For breaking changes, `@tester` must verify the upstream before downstream implementation starts.
 
-If a repo's `@coder` or `@tester` fails, that repo and all downstream repos in the dependency chain are paused. Upstream repos that completed are not rolled back — they remain deployed. The flow resumes once the failing repo is fixed.
+If a repo's implementation agent or `@tester` fails, that repo and all downstream repos in the dependency chain are paused. Upstream repos that completed are not rolled back — they remain deployed. The flow resumes once the failing repo is fixed.
 
 ### Step 5: Verify Integration
 

package/src/commands/fd-plan.md

@@ -82,6 +82,8 @@ Update STATE.md:
 - Set plan_file to path of saved PLAN.md
 - Set plan_confirmed: true
 - Update last_action to "Plan confirmed"
+- If task is UI-heavy, set `requires_design_first: true` and `design_stage: pending`
+- Suggest running `/fd-design --mode=draft` immediately after plan confirmation
 
 ## D-06 Compliance
 

package/src/commands/fd-quick.md

@@ -21,10 +21,13 @@ Parse `$ARGUMENTS` to determine:
 
 | Task Type | Signal Keywords | Agent |
 |-----------|-----------------|-------|
-| Write or edit code | implement, add, create, fix, refactor, update | `@coder` |
+| Backend code implementation | api, server, service, database, migration, endpoint, repository | `@backend-coder` |
+| Frontend code implementation | ui, frontend, component, page, css, style, react, screen | `@frontend-coder` |
+| DevOps and infra implementation | ci, cd, deploy, pipeline, workflow, docker, kubernetes, terraform | `@devops` |
 | Explore and understand | trace, map, find, explore, understand, what does | `@code-explorer` |
 | Review code quality | review, check, audit, analyze | `@reviewer` |
 | Security review | security, auth, vulnerability, injection, OWASP | `@security-auditor` |
+| UI design-first planning | landing page, dashboard, admin panel, onboarding UX, app screen, wireframe, design system | `@design` |
 | Design or architecture | design, architect, schema, API, structure | `@architect` |
 | Write tests | test, coverage, regression, TDD | `@tester` |
 | Documentation | docs, README, document, write | `@writer` |

package/src/commands/fd-verify.md

@@ -42,6 +42,12 @@ Review all changed files:
 - Quality: critical bugs, missing error handling, TDD discipline
 - Conventions: naming, patterns, import style
 - Test coverage >= 80% for changed files — flag as HIGH if below
+- If task is UI-heavy, include design fidelity review against approved design artifact
+
+**Check B2: UI Design Review (@design) — UI-heavy only**
+- Compare implemented UI to approved design artifact
+- Report hierarchy, spacing, CTA flow, responsiveness, accessibility, and missing state coverage gaps
+- Fail verification when severe design fidelity mismatch exists
 
 **Check C: Security Scan (@security-auditor)**
 - No hardcoded secrets

package/src/rules/common/agent-orchestration.md

@@ -10,14 +10,14 @@ FlowDeck provides 23 specialist agents. Each has a specific role. Using the righ
 | `@build-error-resolver` | Fix build failures and type errors | Immediately when build fails |
 | `@build-resolver` | Diagnose and fix build/compile failures | When build breaks and cause is unclear |
 | `@code-explorer` | Map unfamiliar codebase structure | Before modifying unfamiliar code |
-| `@coder` | Implement features and fixes | All code implementation |
+| `@backend-coder` | Implement features and fixes | All code implementation |
 | `@debug-specialist` | Root cause analysis for bugs | When a bug needs deep investigation |
 | `@discusser` | Extract requirements via Q&A | Starting a new feature or phase |
 | `@doc-updater` | Update docs after code changes | After implementation completes |
 | `@plan-checker` | Review PLAN.md before execution | Before executing any plan |
 | `@mapper` | Map codebase to .codebase/ docs | Running /fd-map-codebase |
 | `@orchestrator` | Coordinate multi-agent execution | Managing a full feature delivery |
-| `@parallel-coordinator` | Run parallel agent workstreams | When tasks can run simultaneously |
+| `@task-splitter` | Decompose parallel workstreams | When tasks can run simultaneously |
 | `@performance-optimizer` | Profile and fix performance issues | When app is slow or before release |
 | `@planner` | Create detailed implementation plans | Any multi-file feature |
 | `@refactor-guide` | Safe code restructuring | Reducing technical debt |
@@ -34,7 +34,7 @@ These situations should trigger agent use automatically:
 
 | Situation | Agent |
 |-----------|-------|
-| Complex feature spanning 3+ files | `@planner` first, then `@coder` |
+| Complex feature spanning 3+ files | `@planner` first, then `@backend-coder` |
 | Code was just written | `@reviewer` |
 | Build fails | `@build-error-resolver` |
 | Bug reported | `@debug-specialist` |
@@ -50,11 +50,11 @@ Independent agents can run simultaneously. Examples:
 ```
 Wave 1 (parallel):
   @researcher — research the library API
-  @coder     — implement the model and types
+  @backend-coder     — implement the model and types
   @tester    — write test cases
 
 Wave 2 (after Wave 1):
-  @coder     — implement service using Wave 1 research
+  @backend-coder     — implement service using Wave 1 research
   @reviewer  — review Wave 1 implementation
 ```
 
@@ -78,7 +78,7 @@ discuss → plan → execute → review
 |-------|-------|---------|
 | discuss | `@discusser` | `/fd-discuss` |
 | plan | `@planner` → `@plan-checker` | `/fd-plan` |
-| execute | `@orchestrator` → `@coder`, `@tester`, etc. | `/fd-new-feature` |
+| execute | `@orchestrator` → `@backend-coder`, `@tester`, etc. | `/fd-new-feature` |
 | review | `@reviewer` + `@security-auditor` | `/fd-review-code` |
 
 Do not skip phases. The orchestrator enforces phase gating automatically.

package/src/skills/app-shell-design/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: app-shell-design
+description: Define app shell structure, navigation model, and reusable surface patterns for web/mobile apps
+origin: FlowDeck
+---
+
+# App Shell Design Skill
+
+Standardizes navigation and page frame behavior across app surfaces.
+
+## When to Activate
+
+- New app or major app redesign
+- Task includes navigation, shell, or global layout work
+
+## Required Inputs
+
+- Core product flows
+- Platform targets (web/mobile)
+
+## Output Format
+
+- shell_structure
+- navigation_model
+- route_grouping
+- persistent_ui_regions
+- global_state_requirements
+
+## Example
+
+Use for: "Design app shell and navigation for a kanban productivity app."

package/src/skills/dashboard-design/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: dashboard-design
+description: Design dashboard information hierarchy, data density, and interaction patterns for analytics-heavy surfaces
+origin: FlowDeck
+---
+
+# Dashboard Design Skill
+
+Optimizes dashboard UX for scanability and actionability.
+
+## When to Activate
+
+- Task is dashboard or analytics UI
+- Dense data requires hierarchy decisions
+
+## Required Inputs
+
+- User roles
+- Primary dashboard decisions/actions
+- Key metrics
+
+## Output Format
+
+- dashboard_personas
+- information_hierarchy
+- section_structure
+- component_list
+- alert_and_empty_states
+
+## Example
+
+Use for: "Redesign SaaS operations dashboard for faster anomaly detection."

package/src/skills/decision-trace/SKILL.md

@@ -42,7 +42,7 @@ Use the `decision-trace` tool:
       "Move validation to edge (rejected: adds latency)"
     ],
     "risk_level": "medium",
-    "agent": "coder"
+    "agent": "backend-coder"
   }
 }
 ```

package/src/skills/design-audit/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: design-audit
+description: Audit implemented UI against approved design artifacts for hierarchy, consistency, responsiveness, and accessibility fidelity
+origin: FlowDeck
+---
+
+# Design Audit Skill
+
+Use this skill to evaluate UI output against an approved design spec before final verification.
+
+## When to Activate
+
+- Post-implementation review for UI-heavy tasks
+- `/fd-design --mode=review`
+- Any feature where design fidelity is a release criterion
+
+## Required Inputs
+
+- Approved design artifact
+- Implemented UI scope (screens/pages/components)
+- Review rubric (if available)
+
+## Output Format
+
+- mismatches
+- hierarchy_issues
+- spacing_issues
+- cta_flow_issues
+- responsiveness_issues
+- accessibility_issues
+- component_consistency_issues
+- missing_state_coverage
+- verdict (pass/fail)
+
+## Example
+
+Use for: "Review dashboard implementation against approved wireframe and token rules."

package/src/skills/design-system-definition/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: design-system-definition
+description: Define visual tokens and component behavior rules for consistent UI implementation
+origin: FlowDeck
+---
+
+# Design System Definition Skill
+
+Builds implementation-ready visual system guidance.
+
+## When to Activate
+
+- New user-facing surface
+- Existing UI has consistency issues
+- `/fd-design --mode=system`
+
+## Required Inputs
+
+- Brand direction or existing style baseline
+- Wireframe plan
+
+## Output Format
+
+- visual_direction
+- design_tokens_guidance
+- typography_rules
+- spacing_rules
+- component_behavior_rules
+- accessibility_notes
+
+## Example
+
+Use for: "Define tokens and component rules for SaaS dashboard redesign."

package/src/skills/frontend-handoff/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: frontend-handoff
+description: Convert approved design outputs into implementation-ready handoff checklists for frontend agents
+origin: FlowDeck
+---
+
+# Frontend Handoff Skill
+
+Ensures coding agents receive mandatory design context.
+
+## When to Activate
+
+- Design approval is complete
+- Frontend implementation is next
+
+## Required Inputs
+
+- Approved design artifact
+- Target implementation scope
+
+## Output Format
+
+- implementation_handoff_checklist
+- required_components
+- required_states
+- responsive_behavior_notes
+- acceptance_criteria
+
+## Example
+
+Use for: "Prepare handoff for landing page hero, pricing, and FAQ sections."

package/src/skills/landing-page-design/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: landing-page-design
+description: Design landing pages with clear value hierarchy, CTA flow, and conversion-oriented structure
+origin: FlowDeck
+---
+
+# Landing Page Design Skill
+
+Builds conversion-focused website structures before implementation.
+
+## When to Activate
+
+- Task is landing page or marketing site
+- User goal includes conversion improvement
+
+## Required Inputs
+
+- Product value proposition
+- Target audience
+- Primary CTA
+
+## Output Format
+
+- section_structure
+- message_hierarchy
+- cta_flow
+- trust_signals
+- responsive_behavior_notes
+
+## Example
+
+Use for: "Build a landing page for a new AI workflow product."

package/src/skills/multi-repo/SKILL.md

@@ -125,11 +125,11 @@ For any cross-repo change involving an API:
 
 1. **Write the new contract first** — `@architect` produces the updated interface definition before any code is written
 2. **Review the contract in isolation** — confirm all affected teams agree before implementation starts
-3. **Implement upstream against the new contract** — `@coder` in the upstream repo
-4. **Implement downstream against the new contract** — `@coder` in each consumer repo, independently
+3. **Implement upstream against the new contract** — `@backend-coder` in the upstream repo
+4. **Implement downstream against the new contract** — `@backend-coder` in each consumer repo, independently
 5. **Integration test** — verify upstream and downstream work together against the contract
 
-This pattern allows Wave 3 parallelism (upstream and downstream `@coder` agents can work simultaneously from the same contract) even across repos.
+This pattern allows Wave 3 parallelism (upstream and downstream `@backend-coder` agents can work simultaneously from the same contract) even across repos.
 
 ## Breaking vs Non-Breaking API Changes
 

package/src/skills/plan-task/SKILL.md

@@ -61,7 +61,7 @@ Activate when:
 ## Wave 1 — Foundation (parallel)
 
 ### Task 1.A — [Name]
-- **Agent**: @coder
+- **Agent**: @backend-coder
 - **File**: `src/models/subscription.ts`
 - **Scope**: Create Subscription model with id, userId, status, expiresAt
 - **Verify**: `npx tsc --noEmit` passes
@@ -74,7 +74,7 @@ Activate when:
 ## Wave 2 — Implementation (after Wave 1)
 
 ### Task 2.A — [Name]
-- **Agent**: @coder
+- **Agent**: @backend-coder
 - **Depends on**: Task 1.A, Task 1.B
 - **File**: `src/services/billing-service.ts`
 - **Scope**: Implement subscribe(), cancel(), handleWebhook()

package/src/skills/responsive-review/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: responsive-review
+description: Review responsive behavior and breakpoint fidelity against design intent
+origin: FlowDeck
+---
+
+# Responsive Review Skill
+
+Checks whether layouts and interactions stay usable across viewport sizes.
+
+## When to Activate
+
+- UI implementation review
+- Design review for mobile/tablet/desktop behavior
+
+## Required Inputs
+
+- Breakpoint strategy
+- Implemented UI
+
+## Output Format
+
+- breakpoint_coverage
+- layout_breakpoints_issues
+- interaction_breakpoints_issues
+- mobile_readability_issues
+- responsive_verdict
+
+## Example
+
+Use for: "Validate admin panel responsiveness before release."

package/src/skills/ui-ux-planning/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: ui-ux-planning
+description: Define UX structure and interaction model before UI implementation
+origin: FlowDeck
+---
+
+# UI UX Planning Skill
+
+Creates UX-first structure so implementation does not start from raw requirements.
+
+## When to Activate
+
+- Feature involves user-facing flows
+- Task mentions UX, onboarding, conversion, or usability
+
+## Required Inputs
+
+- Product goal
+- Target users
+- Constraints
+
+## Output Format
+
+- user_goals
+- target_audience
+- core_user_flows
+- page_map_or_screen_map
+- interaction_model
+
+## Example
+
+Use for: "Improve onboarding UX for first-time users."

package/src/skills/wireframe-planning/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: wireframe-planning
+description: Produce wireframe-level layout plans with section hierarchy and component intent
+origin: FlowDeck
+---
+
+# Wireframe Planning Skill
+
+Defines structure and layout intent before visual polish and coding.
+
+## When to Activate
+
+- After UX planning and before implementation
+- Task requires new page/screen structure
+
+## Required Inputs
+
+- UX flows
+- page/screen map
+
+## Output Format
+
+- section_structure
+- layout_plan
+- component_list
+- state_list
+
+## Example
+
+Use for: "Create wireframe plan for a settings page and billing screen."

package/dist/services/model-router.d.ts

@@ -1,35 +0,0 @@
-export type TaskType = "planning" | "implementation" | "debugging" | "review" | "testing" | "documentation" | "analysis" | "security" | "orchestration";
-export interface ModelRoute {
-    primary: string;
-    fallback?: string;
-    high_risk_override?: string;
-    temperature?: number;
-    reasoning_effort?: "low" | "medium" | "high";
-}
-export type ModelRouterConfig = Record<TaskType, ModelRoute>;
-export declare function getRouterConfig(dir: string): ModelRouterConfig;
-export interface RoutedModel {
-    model: string;
-    temperature: number;
-    reasoning_effort?: "low" | "medium" | "high";
-    task_type: TaskType;
-    is_high_risk: boolean;
-    is_override: boolean;
-}
-export declare function routeModel(dir: string, task_type: TaskType, risk_score?: number): RoutedModel;
-/**
- * Build agent configuration array for multi-agent orchestration.
- * Requires OpenCode runtime integration to be functional.
- * @deprecated Stub - requires OpenCode client.session.create() API
- */
-export declare function buildAgentConfig(dir: string, agents: Array<{
-    name: string;
-    task_type: TaskType;
-    risk_score?: number;
-}>): Array<{
-    name: string;
-    model: string;
-    temperature: number;
-    reasoningEffort?: string;
-}>;
-//# sourceMappingURL=model-router.d.ts.map

package/dist/services/model-router.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"model-router.d.ts","sourceRoot":"","sources":["../../src/services/model-router.ts"],"names":[],"mappings":"AASA,MAAM,MAAM,QAAQ,GAChB,UAAU,GACV,gBAAgB,GAChB,WAAW,GACX,QAAQ,GACR,SAAS,GACT,eAAe,GACf,UAAU,GACV,UAAU,GACV,eAAe,CAAA;AAEnB,MAAM,WAAW,UAAU;IACzB,OAAO,EAAE,MAAM,CAAA;IACf,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,kBAAkB,CAAC,EAAE,MAAM,CAAA;IAC3B,WAAW,CAAC,EAAE,MAAM,CAAA;IACpB,gBAAgB,CAAC,EAAE,KAAK,GAAG,QAAQ,GAAG,MAAM,CAAA;CAC7C;AAED,MAAM,MAAM,iBAAiB,GAAG,MAAM,CAAC,QAAQ,EAAE,UAAU,CAAC,CAAA;AAc5D,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,GAAG,iBAAiB,CAS9D;AAED,MAAM,WAAW,WAAW;IAC1B,KAAK,EAAE,MAAM,CAAA;IACb,WAAW,EAAE,MAAM,CAAA;IACnB,gBAAgB,CAAC,EAAE,KAAK,GAAG,QAAQ,GAAG,MAAM,CAAA;IAC5C,SAAS,EAAE,QAAQ,CAAA;IACnB,YAAY,EAAE,OAAO,CAAA;IACrB,WAAW,EAAE,OAAO,CAAA;CACrB;AAED,wBAAgB,UAAU,CACxB,GAAG,EAAE,MAAM,EACX,SAAS,EAAE,QAAQ,EACnB,UAAU,SAAM,GACf,WAAW,CAqBb;AAED;;;;GAIG;AACH,wBAAgB,gBAAgB,CAC9B,GAAG,EAAE,MAAM,EACX,MAAM,EAAE,KAAK,CAAC;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,SAAS,EAAE,QAAQ,CAAC;IAAC,UAAU,CAAC,EAAE,MAAM,CAAA;CAAE,CAAC,GACxE,KAAK,CAAC;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC;IAAC,WAAW,EAAE,MAAM,CAAC;IAAC,eAAe,CAAC,EAAE,MAAM,CAAA;CAAE,CAAC,CAUvF"}