npm - @polymorphism-tech/morph-spec - Versions diffs - 4.9.0 → 4.10.1 - Mend

@polymorphism-tech/morph-spec 4.9.0 → 4.10.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (164) hide show

package/framework/skills/level-0-meta/morph-replicate/SKILL.md CHANGED Viewed

@@ -4,58 +4,61 @@ description: Simplified workflow for converting HTML prototypes into functional
 user-invocable: true
 argument-hint: "[feature-name] [prototype-path]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - blazor
 ---
 # MORPH Replicate — HTML to Blazor Conversion
-> Workflow simplificado para replicar prototipos HTML em Blazor.
-> Use quando tiver um prototipo HTML pronto e precisar converter para codigo Blazor funcional.
+> Simplified workflow for replicating HTML prototypes in Blazor.
+> Use when you have a ready HTML prototype and need to convert it to functional Blazor code.
-## Comando
+## Command
 ```bash
 /morph:replicate {feature-name} {prototype-path}
 ```
-**Exemplo:**
+**Example:**
 ```bash
 /morph:replicate ui-redesign prototipo/
 ```
 ---
-## Workflow Simplificado
+## Simplified Workflow
-### FASE 1: ANALISE DO PROTOTIPO
+### PHASE 1: PROTOTYPE ANALYSIS
-1. **Ler todos os arquivos HTML em `{prototype-path}/`**
+1. **Read all HTML files in `{prototype-path}/`**
    ```bash
-   # Encontrar todos os arquivos HTML
+   # Find all HTML files
    glob: {prototype-path}/**/*.html
-   glob: {prototype-path}/**/code.html  # Pattern comum de prototipos
+   glob: {prototype-path}/**/code.html  # Common prototype pattern
    ```
-2. **Extrair padroes de cada arquivo:**
-   - Layout (grid, flexbox, estrutura)
-   - Componentes (cards, buttons, forms, modals)
-   - Cores (extrair de inline styles e CSS)
-   - Fontes (font-family, sizes)
-   - Espacamentos (padding, margin, gap)
-   - Classes CSS usadas
+2. **Extract patterns from each file:**
+   - Layout (grid, flexbox, structure)
+   - Components (cards, buttons, forms, modals)
+   - Colors (extract from inline styles and CSS)
+   - Fonts (font-family, sizes)
+   - Spacing (padding, margin, gap)
+   - CSS classes used
-3. **Gerar mapeamento HTML → Blazor:**
+3. **Generate HTML → Blazor mapping:**
-   > Para tabela completa de mapeamentos, veja `references/blazor-html-mapping.md`
+   **Read the reference file first:** `references/blazor-html-mapping.md` — this contains the complete mapping table for HTML→Fluent UI and HTML→MudBlazor conversions. Load it before generating the prototype-specific mapping.
-   Documente os mapeamentos relevantes para este prototipo especifico:
+   Then document the relevant mappings for this specific prototype, citing the reference:
    ```markdown
-   ## Mapeamento HTML → Blazor (este prototipo)
-   - <elemento HTML> → <ComponenteBlazor>
+   ## HTML → Blazor Mapping (this prototype)
+   > Source: references/blazor-html-mapping.md
+   - <HTML element> → <BlazorComponent>
    ```
-4. **Gerar lista de classes CSS a criar:**
+4. **Generate list of CSS classes to create:**
    ```markdown
-   ## Classes CSS Necessarias
+   ## Required CSS Classes
    - [ ] .page-layout
    - [ ] .home-hero
@@ -65,72 +68,72 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
    - [ ] .animate-slideInUp
    ```
-**PAUSA:** Aprovar mapeamento e lista de CSS
+**PAUSE:** Approve mapping and CSS list
 ---
-### FASE 2: TASKS (Lista de Telas)
+### PHASE 2: TASKS (Screen List)
-Gerar lista de telas para implementar na ordem correta:
+Generate screen list to implement in correct order:
 ```markdown
-## Tasks de Implementacao
+## Implementation Tasks
 ### T001: Setup Design System
-- Criar/atualizar wwwroot/css/design-system.css
-- Adicionar todas as classes CSS listadas
-- Validar com `morph-spec validate`
-### T002: {Nome da Tela 1}
-- Ler: {prototype-path}/{tela1}.html
-- Criar/Atualizar: Pages/{Tela1}.razor
-- Componentes: FluentCard, FluentButton, etc.
+- Create/update wwwroot/css/design-system.css
+- Add all listed CSS classes
+- Validate with `morph-spec validate`
+### T002: {Screen Name 1}
+- Read: {prototype-path}/{screen1}.html
+- Create/Update: Pages/{Screen1}.razor
+- Components: FluentCard, FluentButton, etc.
 - CSS: .home-hero, .card-premium
-### T003: {Nome da Tela 2}
-- Ler: {prototype-path}/{tela2}.html
-- Criar/Atualizar: Pages/{Tela2}.razor
+### T003: {Screen Name 2}
+- Read: {prototype-path}/{screen2}.html
+- Create/Update: Pages/{Screen2}.razor
 - ...
-### TXXX: Validacao Final
-- Build completo
+### TXXX: Final Validation
+- Full build
 - `morph-spec validate`
-- Testar responsividade
+- Test responsiveness
 ```
-**PAUSA:** Aprovar lista de tasks
+**PAUSE:** Approve task list
 ---
-### FASE 3: IMPLEMENT (Por Tela)
+### PHASE 3: IMPLEMENT (Per Screen)
-Para cada tela, seguir este fluxo:
+For each screen, follow this flow:
-1. **Ler HTML do prototipo**
+1. **Read prototype HTML**
    ```
-   Read: {prototype-path}/{tela}.html
+   Read: {prototype-path}/{screen}.html
    ```
-2. **Ler arquivo .razor atual** (se existir)
+2. **Read current .razor file** (if exists)
    ```
-   Read: Pages/{Tela}.razor
+   Read: Pages/{Screen}.razor
    ```
-3. **Reescrever .razor usando Fluent UI/MudBlazor**
-   - Manter estrutura de layout do prototipo
-   - Substituir elementos HTML por componentes Blazor
-   - Aplicar classes CSS do design-system
+3. **Rewrite .razor using Fluent UI/MudBlazor**
+   - Keep prototype layout structure
+   - Replace HTML elements with Blazor components
+   - Apply design-system CSS classes
-4. **Adicionar CSS ao design-system.css**
-   - Se classe nova foi usada no .razor
-   - Seguir padrao de nomenclatura (prefixo por pagina)
+4. **Add CSS to design-system.css**
+   - If new class was used in .razor
+   - Follow naming pattern (prefix by page)
-5. **Build para validar**
+5. **Build to validate**
    ```bash
    dotnet build
    ```
-6. **Validar CSS**
+6. **Validate CSS**
    ```bash
    morph-spec validate src/MyApp.Web
    ```
@@ -139,38 +142,43 @@ Para cada tela, seguir este fluxo:
 ## Outputs
-Este workflow gera apenas:
+All outputs go in `.morph/features/{feature-name}/5-implement/`:
-| Arquivo | Descricao |
-|---------|-----------|
-| `.razor` files | Paginas convertidas |
-| `design-system.css` | CSS atualizado |
-| `recap.md` | Resumo da implementacao (ao final) |
+| File | Location | Description |
+|---------|----------|-----------|
+| `.razor` files | Project source (Pages/, Components/, Shared/) | Converted pages |
+| `design-system.css` | `wwwroot/css/design-system.css` | Updated CSS |
+| `recap.md` | `.morph/features/{feature-name}/5-implement/recap.md` | Implementation summary |
-**NAO gera:** proposal.md, spec.md, contracts.cs, tasks.json
+After completion, mark the output:
+```bash
+npx morph-spec state mark-output {feature-name} recap
+```
+**Does NOT generate:** proposal.md, spec.md, contracts.cs, tasks.md
 ---
-## Exemplo de Execucao
+## Execution Example
 ```markdown
 /morph:replicate checkout-redesign prototipo/checkout/
-📁 Analisando prototipo em prototipo/checkout/...
+📁 Analyzing prototype in prototipo/checkout/...
-**Arquivos encontrados:**
+**Files found:**
 - step1-cart.html
 - step2-payment.html
 - step3-confirmation.html
-**Padroes extraidos:**
+**Extracted patterns:**
-Cores:
+Colors:
 - Primary: #FF6B35
 - Secondary: #2D3047
 - Background: #FAFAFA
-Classes CSS a criar:
+CSS classes to create:
 - [ ] .checkout-layout
 - [ ] .checkout-steps
 - [ ] .checkout-form
@@ -178,39 +186,39 @@ Classes CSS a criar:
 - [ ] .payment-options
 - [ ] .confirmation-message
-Mapeamento HTML → Blazor:
+HTML → Blazor Mapping:
 - form.checkout-form → EditForm + FluentTextField
 - div.payment-card → FluentCard
 - button.btn-pay → FluentButton Accent
 ---
-⛔ **PAUSA OBRIGATORIA**
+⛔ **MANDATORY PAUSE**
-**Proximos passos:**
-1. ✅ Aprovar e gerar tasks de implementacao
-2. 🔄 Ajustar mapeamento
-3. 📋 Ver mais detalhes dos componentes
+**Next steps:**
+1. ✅ Approve and generate implementation tasks
+2. 🔄 Adjust mapping
+3. 📋 See more component details
 ```
 ---
-## Quando Usar
+## When to Use
-- ✅ Prototipo HTML pronto (Figma export, hand-coded, etc.)
-- ✅ Design ja aprovado pelo cliente
-- ✅ Apenas conversao visual (sem logica de negocio nova)
-- ✅ Codigo Blazor existente para atualizar
+- ✅ HTML prototype ready (hand-coded, exported, etc.)
+- ✅ Design already approved by client
+- ✅ Visual conversion only (no new business logic)
+- ✅ Existing Blazor code to update
-## Quando NAO Usar
+## When NOT to Use
-- ❌ Feature nova com logica complexa (use FULL MORPH)
-- ❌ Infraestrutura Azure necessaria (use FULL MORPH)
-- ❌ Sem prototipo definido (use STANDARD ou FULL MORPH)
+- ❌ New feature with complex logic (use FULL MORPH)
+- ❌ Azure infrastructure needed (use FULL MORPH)
+- ❌ No prototype defined (use STANDARD or FULL MORPH)
 ---
-## Referências
+## References
 - **Ref:** `framework/standards/frontend/blazor/html-conversion.md`
 - **Ref:** `framework/standards/frontend/design-system/naming.md`
@@ -219,4 +227,4 @@ Mapeamento HTML → Blazor:
 ---
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

package/framework/skills/level-0-meta/{simulation-checklist → morph-simulation-checklist}/SKILL.md RENAMED Viewed

@@ -3,6 +3,8 @@ name: morph:simulation-checklist
 description: Checklist for implementing mock/simulation clients for external .NET services (AI APIs, payments, email). Use when setting up simulation mode without real API access, when creating fake service implementations for development/testing, or when debugging external service integrations.
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+stacks:
+  - dotnet
 ---
 # Simulation Checklist
@@ -52,11 +54,33 @@ else
     services.AddProductionClients(configuration);
 ```
+## MORPH-SPEC Integration
+When implementing simulation as a morph-spec task:
+```bash
+# Track the simulation setup task
+npx morph-spec task start {feature} {task-id}
+# After implementation, validate the feature
+npx morph-spec validate-feature {feature}
+# Complete the task (triggers Tier-4 validators)
+npx morph-spec task done {feature} {task-id}
+```
+Reference the project's service lifetime patterns:
+```bash
+# Check existing DI patterns in the project
+grep -r "AddSingleton\|AddScoped\|AddTransient" src/ --include="*.cs" -l
+```
 ## Post-Implementation
 - [ ] Validate DI: `dotnet build && dotnet run` + health check
 - [ ] Test full flow end-to-end (not just unit tests)
 - [ ] Verify simulation logs — confirm mocks are being called
+- [ ] Run `npx morph-spec validate-feature {feature}` to check architecture compliance
 ## Common Errors

package/framework/skills/level-0-meta/{tool-usage-guide → morph-tool-usage-guide}/SKILL.md RENAMED Viewed

@@ -82,66 +82,67 @@ Feature with multiple active agents?
 ---
-## Comunicação com o Usuário
+## User Communication
-### AskUserQuestion vs. Texto Livre
+### AskUserQuestion vs. Plain Text
-| Situação | Ferramenta |
+| Situation | Tool |
 |---|---|
-| ≥2 opções mutuamente exclusivas | `AskUserQuestion` (options[]) |
-| Escolha binária sim/não | `AskUserQuestion` (2 options) |
-| Aprovação de plano | `ExitPlanMode` |
-| Explicação, progresso, confirmação | Texto direto |
+| ≥2 mutually exclusive options | `AskUserQuestion` (options[]) |
+| Binary yes/no choice | `AskUserQuestion` (2 options) |
+| Plan approval | `ExitPlanMode` |
+| Explanation, progress, confirmation | Direct text |
-**Regra:** NUNCA apresentar opções múltiplas como texto livre. Use `AskUserQuestion` com `options[]` para garantir escolha estruturada sem ambiguidade.
+**Rule:** NEVER present multiple options as plain text. Use `AskUserQuestion` with `options[]` to ensure structured, unambiguous choices.
 ### EnterPlanMode
-Use **ANTES** de iniciar implementação quando:
-- Refactor toca ≥5 arquivos ou muda arquitetura
-- Estimativa de tasks ≥20
-- Escolha entre ≥2 abordagens de design significativamente diferentes
+Use **BEFORE** starting implementation when:
+- Refactor touches ≥5 files or changes architecture
+- Estimated tasks ≥20
+- Choosing between ≥2 significantly different design approaches
-NÃO use para:
-- Correção pontual de 1-3 arquivos
-- Usuário já especificou abordagem detalhada
-- Fase implement com tasks.md já aprovado
+Do NOT use for:
+- Point fix of 1-3 files
+- User already specified detailed approach
+- Implement phase with tasks.md already approved
 ---
-### Regra de Leituras Paralelas (CRÍTICO)
+### Parallel Read Rule (CRITICAL)
-Arquivos independentes = uma única mensagem com múltiplas chamadas Read.
+Independent files = a single message with multiple Read calls.
 ```
-# ERRADO (sequencial)
+# WRONG (sequential)
 Read: state.json → Read: spec.md → Read: tasks.md  # 3 round-trips
-# CORRETO (paralelo, 1 round-trip)
+# CORRECT (parallel, 1 round-trip)
 Read: state.json + Read: spec.md + Read: tasks.md
 ```
-Critério: se a leitura de arquivo B não depende do CONTEÚDO de arquivo A, leia os dois juntos.
+Criterion: if reading file B does not depend on the CONTENT of file A, read both together.
-**Exemplos de independência:** spec.md ↔ decisions.md ↔ contracts.cs ↔ tasks.md (todos lidos juntos na investigação de uma fase).
+**Independence examples:** spec.md ↔ decisions.md ↔ contracts.cs ↔ tasks.md (all read together when investigating a phase).
 ---
 ## Tools Per Phase
-> Para detalhes de ferramentas por fase, veja `references/tools-per-phase.md`
+> For detailed per-phase tool tables, see `references/tools-per-phase.md`
-**Resumo rápido por fase:**
+**Quick summary by phase:**
-| Fase | MCPs principais | Dispatch subagents? |
-|------|----------------|---------------------|
-| Proposal | GitHub (opcional) | Não |
-| Setup | GitHub (opcional) | Não |
-| UI/UX | Playwright, Figma, Context7 | Não |
-| Design | Supabase, Context7, GitHub | Sim (domain-architect + schema em paralelo) |
-| Clarify | Context7, GitHub | Não |
-| Tasks | Context7, GitHub | Sim (quando spec tem 20+ reqs ou 3+ domínios) |
-| Implement | Supabase, Context7, Playwright, GitHub | Sim (quando tasks.total ≥ 6 e 2+ domínios) |
+| Phase | Primary MCPs | Dispatch subagents? |
+|-------|-------------|---------------------|
+| Proposal | GitHub (optional) | No |
+| Setup | GitHub (optional) | No |
+| UI/UX | Playwright, Context7 | No |
+| Design | Supabase, Context7, GitHub | Yes (domain-architect + schema in parallel) |
+| Clarify | Context7, GitHub | No |
+| Plan | Context7, GitHub | No |
+| Tasks | Context7, GitHub | Yes (when spec has 20+ reqs or 3+ domains) |
+| Implement | Supabase, Context7, Playwright, GitHub | Yes (when tasks.total ≥ 6 and 2+ domains) |
 ---
@@ -167,7 +168,6 @@ Critério: se a leitura de arquivo B não depende do CONTEÚDO de arquivo A, lei
 |-----|-------------|----------|
 | **Supabase** | Schema analysis, migrations, RLS | Grep + Read code files |
 | **GitHub** | Issues, PRs, repo metadata, code search | Bash `gh` CLI |
-| **Figma** | Design tokens, component specs | Read CSS/SCSS files |
 | **Context7** | Library documentation lookups | WebSearch + WebFetch |
 | **Playwright** | Browser automation, screenshots, page inspection, smoke tests | WebFetch (read-only), Manual testing |
 | **Azure** | Cloud resource management | Bash `az` CLI |
@@ -192,15 +192,15 @@ Before choosing a tool, ask:
    - Unknown files needing exploration → Glob/Grep, then Read
    - Complex multi-step analysis → Task subagent
-### Anti-Padrões Globais
+### Global Anti-Patterns
-- ❌ **WebFetch para URLs GitHub** → Use `gh api` ou `gh` CLI
-  - Correto: `gh api repos/owner/repo/git/trees/main --field recursive=1`
-  - Correto: `gh pr view 123`, `gh issue view 456`
-  - WebFetch para GitHub retorna HTML/redirect; `gh` usa a API autenticada
-- ❌ **Perguntas multi-opção como texto livre** → Use `AskUserQuestion` com `options[]`
-  - Correto: `AskUserQuestion({ question: "Qual abordagem?", options: [{label: "A"}, {label: "B"}] })`
-  - Texto livre cria ambiguidade e requer parse manual da resposta
+- ❌ **WebFetch for GitHub URLs** → Use `gh api` or `gh` CLI
+  - Correct: `gh api repos/owner/repo/git/trees/main --field recursive=1`
+  - Correct: `gh pr view 123`, `gh issue view 456`
+  - WebFetch for GitHub returns HTML/redirect; `gh` uses the authenticated API
+- ❌ **Multi-option questions as plain text** → Use `AskUserQuestion` with `options[]`
+  - Correct: `AskUserQuestion({ question: "Which approach?", options: [{label: "A"}, {label: "B"}] })`
+  - Plain text creates ambiguity and requires manual response parsing
 ---
@@ -216,7 +216,7 @@ For the canonical list of MCPs, their tools, phase relevance, and fallbacks, see
 |-------|-------------|----------|
 | Proposal | Context7 | WebSearch |
 | Setup | GitHub | `gh` CLI |
-| UI/UX | Playwright, Figma, Context7 | WebFetch, Read CSS |
+| UI/UX | Playwright, Context7 | WebFetch, Read CSS |
 | Design | Supabase, Context7, GitHub | Grep + Read code |
 | Clarify | Context7, GitHub | WebSearch |
 | Tasks | Context7, GitHub | WebSearch, `gh` CLI |

package/framework/skills/level-0-meta/{tool-usage-guide → morph-tool-usage-guide}/references/tools-per-phase.md RENAMED Viewed

@@ -62,7 +62,6 @@
 | Read user-provided screenshots | **Read** (image files) | Claude Code reads images natively |
 | Search for existing CSS variables | **Grep** `--root:` or `--color-` in `*.css,*.scss` | Find existing design tokens |
 | Find existing UI components | **Glob** `**/Components/**/*.razor` or `**/components/**/*.tsx` | Existing patterns |
-| Get Figma design tokens | **Figma MCP** `get_file({ fileKey })` | Extract colors, typography from Figma |
 | Look up component library API | **Context7 MCP** `query_docs({ libraryId, query })` | Accurate component props/events |
 | Preview de página existente | **Playwright MCP** `browser_navigate()` + `browser_take_screenshot()` | **WebFetch** URL |
 | Inspecionar estrutura da página | **Playwright MCP** `browser_snapshot()` | **WebFetch** + parse manual |
@@ -72,7 +71,7 @@
 | Generate design system from CSS | **Bash** `npx morph-spec generate design-system --scan` | CLI command |
 | Update state | **Bash** `npx morph-spec state mark-output {feature} uiDesignSystem && npx morph-spec state mark-output {feature} uiMockups && npx morph-spec state mark-output {feature} uiComponents && npx morph-spec state mark-output {feature} uiFlows` | CLI command |
-**MCPs used:** Figma (design tokens), Playwright (live preview, page inspection), Context7 (component docs).
+**MCPs used:** Playwright (live preview, page inspection), Context7 (component docs).
 **Anti-patterns:**
 - ❌ WebSearch for MudBlazor docs (use Context7 MCP — more accurate)

package/framework/skills/level-0-meta/{verification-before-completion → morph-verification-before-completion}/SKILL.md RENAMED Viewed

@@ -3,13 +3,14 @@ name: morph:verification-before-completion
 description: Phase-specific verification checklists and morph-spec validation commands for confirming MORPH-SPEC outputs are complete and correct. Use before marking any task done, before advancing to the next phase, before committing, or before creating PRs.
 user-invocable: true
 argument-hint: "[feature-name] [phase?]"
+allowed-tools: Read, Bash, Glob, Grep
 ---
 # Verification Before Completion — MORPH-SPEC Integrated
 > Never claim work is complete without running verification. Evidence before assertions.
 >
-> **Script:** Run `node .claude/skills/verification-before-completion/scripts/check-phase-outputs.mjs <feature> [phase]` to check required output files exist.
+> **Script:** Run `node .claude/skills/morph-verification-before-completion/scripts/check-phase-outputs.mjs <feature> [phase]` to check required output files exist.
 ## When to Use
@@ -52,16 +53,26 @@ argument-hint: "[feature-name] [phase?]"
 - [ ] All clarification questions answered by user
 - [ ] `spec.md` updated with Clarifications section
+- [ ] `clarifications.md` exists in `1-design/`
 - [ ] No unresolved ambiguities in spec
-### Phase 4 — Tasks
+### Phase 4 — Plan
-- [ ] `tasks.md` or `tasks.json` exists
+- [ ] `plan.md` exists in `.morph/features/{feature}/3-plan/`
+- [ ] Plan contains: Goal, Architecture, Execution Strategy, Task Groups
+- [ ] Each task has exact file paths and complete code
+- [ ] Execution strategy defined (single / subagents / agent-teams)
+- [ ] `morph-spec state mark-output {feature} plan` was called
+- [ ] User approved plan via `morph-spec approve {feature} plan`
+### Phase 5 — Tasks
+- [ ] `tasks.md` exists
 - [ ] All tasks have: ID, title, description, dependencies
 - [ ] Checkpoints defined (every 3 tasks)
 - [ ] `morph-spec state set {feature} tasks.total N` called
-### Phase 5 — Implement
+### Phase 6 — Implement
 - [ ] All tasks marked as completed
 - [ ] Build succeeds (`npm run build` or `dotnet build`)
@@ -74,17 +85,17 @@ argument-hint: "[feature-name] [phase?]"
 ## Verification Commands
 ```bash
-# Run content-aware validation
+# Run full feature validation
 npx morph-spec validate-feature {feature-name}
-# Run with specific phase
-npx morph-spec validate-feature {feature-name} --phase design
+# Check feature state and phase
+npx morph-spec state get {feature-name}
-# Check feature status
-npx morph-spec status {feature-name} --verbose
+# Check approval gates
+npx morph-spec approval-status {feature-name}
-# Run full project validation
-npx morph-spec validate
+# Check overall project status
+npx morph-spec status
 ```
 ---
@@ -100,7 +111,7 @@ Before running `morph-spec task done`:
 ```bash
 # Verify before marking done
-npx morph-spec validate-feature {feature} --phase implement
+npx morph-spec validate-feature {feature}
 npx morph-spec task done {feature} T001
 ```

package/framework/skills/level-0-meta/{verification-before-completion → morph-verification-before-completion}/scripts/check-phase-outputs.mjs RENAMED Viewed

@@ -35,10 +35,10 @@ const PHASE_OUTPUTS = {
     { file: '2-ui/flows.md', required: false },
   ],
   tasks: [
-    { file: '3-tasks/tasks.md', required: true },
+    { file: '4-tasks/tasks.md', required: true },
   ],
   implement: [
-    { file: '4-implement/recap.md', required: true },
+    { file: '5-implement/recap.md', required: true },
   ],
 };