@polymorphism-tech/morph-spec 4.10.0 → 4.10.2

package/framework/skills/level-0-meta/morph-frontend-review/SKILL.md

@@ -1,31 +1,34 @@
 ---
 name: morph:frontend-review
-description: Auditoria completa do frontend — valida design outputs (design-system, contraste WCAG,
-  mockups), scan estático de acessibilidade (TSX + Razor), screenshots responsivos em 3
-  breakpoints via Playwright, axe-core a11y em runtime, e SEO (Next.js metadata). Cobre Next.js
-  e Blazor. Disparado ao final do phase-uiux e pós-implementação.
+description: Complete frontend audit — validates design outputs (design-system, WCAG contrast,
+  mockups), static accessibility scan (TSX + Razor), responsive screenshots at 3
+  breakpoints via Playwright, axe-core a11y at runtime, and SEO (Next.js metadata). Covers Next.js
+  and Blazor. Triggered at end of phase-uiux and post-implementation.
 argument-hint: "[feature-name]"
 user-invocable: true
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep,
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion,
   mcp__playwright__browser_navigate, mcp__playwright__browser_resize,
   mcp__playwright__browser_take_screenshot, mcp__playwright__browser_snapshot,
   mcp__playwright__browser_evaluate, mcp__playwright__browser_console_messages
 cliVersion: "4.8.19"
+stacks:
+  - blazor
+  - nextjs
 ---
 
 # Frontend Review
 
-> Auditoria completa do frontend: design outputs, acessibilidade estática + runtime, screenshots
-> responsivos e SEO. Disparado ao final do `phase-uiux` (valida design) e pós-implementação
-> (valida código implementado).
+> Complete frontend audit: design outputs, static + runtime accessibility, responsive
+> screenshots and SEO. Triggered at end of `phase-uiux` (validates design) and post-implementation
+> (validates implemented code).
 
-> **Nota sobre MCP:** O prefixo `mcp__playwright__` corresponde ao nome do servidor Playwright
-> conforme configurado no `settings.json` do projeto. Se o servidor tiver nome diferente (ex:
-> `plugin_playwright_playwright`), ajuste o prefixo nos calls abaixo.
+> **Note about MCP:** The `mcp__playwright__` prefix corresponds to the Playwright server name
+> as configured in the project's `settings.json`. If the server has a different name (e.g.,
+> `plugin_playwright_playwright`), adjust the prefix in the calls below.
 
 ---
 
-## Step 0 — Detectar Contexto e Stack
+## Step 0 — Detect Context and Stack
 
 ```bash
 node .claude/skills/morph-post-implementation/scripts/detect-stack.mjs
@@ -33,128 +36,128 @@ node .claude/skills/morph-post-implementation/scripts/detect-stack.mjs
 
 Output JSON: `{ stack: "DOTNET" | "NEXTJS" | "FULLSTACK" | "UNKNOWN", frontendPath, backendPath, startCommand }`
 
-Além do stack, determinar o **contexto** examinando o que existe:
+Beyond the stack, determine the **context** by examining what exists:
 
 ```bash
-# Verificar se design outputs existem
+# Check if design outputs exist
 ls .morph/features/$ARGUMENTS/2-ui/ 2>/dev/null
 
-# Verificar se arquivos frontend implementados existem
+# Check if implemented frontend files exist
 find . -name "*.tsx" -o -name "*.razor" 2>/dev/null | head -5
 ```
 
-- Se `.morph/features/$ARGUMENTS/2-ui/ui-design-system.md` existe → contexto inclui **design validation**
-- Se arquivos frontend implementados existem (`.tsx`, `.razor`) → contexto inclui **implementation validation**
-- Ambos podem coexistir
+- If `.morph/features/$ARGUMENTS/2-ui/ui-design-system.md` exists → context includes **design validation**
+- If implemented frontend files exist (`.tsx`, `.razor`) → context includes **implementation validation**
+- Both can coexist
 
-Guarde `stack`, `frontendPath`, `startCommand` e o contexto detectado — todos os passos dependem deles.
+Store `stack`, `frontendPath`, `startCommand` and the detected context — all steps depend on them.
 
 ---
 
-## Step 1 — Validação de Design Outputs (se contexto inclui design validation)
+## Step 1 — Design Outputs Validation (if context includes design validation)
 
 ```bash
-npx morph-spec validate-feature $ARGUMENTS --phase uiux
+npx morph-spec validate-feature $ARGUMENTS
 ```
 
-Verificar existência e qualidade dos 4 outputs obrigatórios em `.morph/features/$ARGUMENTS/2-ui/`:
+Verify existence and quality of the 4 mandatory outputs in `.morph/features/$ARGUMENTS/2-ui/`:
 
 ```
-[ ] ui-design-system.md — paleta de cores, tokens de tipografia, espaçamento
-[ ] ui-mockups.md — wireframes com estados responsivos
-[ ] ui-components.md — specs técnicas dos componentes
-[ ] ui-flows.md — jornadas de usuário e edge cases
-[ ] Contraste WCAG AA: cores primárias e de texto ≥ 4.5:1 (verificar ui-design-system.md)
-[ ] Touch targets documentados: ≥ 44x44px para mobile
-[ ] Estados de loading/error/empty definidos nos mockups
+[ ] ui-design-system.md — color palette, typography tokens, spacing
+[ ] ui-mockups.md — wireframes with responsive states
+[ ] ui-components.md — technical component specs
+[ ] ui-flows.md — user journeys and edge cases
+[ ] WCAG AA Contrast: primary and text colors ≥ 4.5:1 (check ui-design-system.md)
+[ ] Documented touch targets: ≥ 44x44px for mobile
+[ ] Loading/error/empty states defined in mockups
 ```
 
-**🚫 BLOCK** se `validate-feature` falhar ou outputs obrigatórios ausentes.
+**🚫 BLOCK** if `validate-feature` fails or mandatory outputs missing.
 
-Leia `ui-design-system.md` e verifique manualmente se as cores primária e de texto têm razão de
-contraste ≥ 4.5:1. Ferramentas de referência: WebAIM Contrast Checker (critérios WCAG 2.1 AA).
+Read `ui-design-system.md` and manually verify that primary and text colors have a contrast ratio
+≥ 4.5:1. Reference tools: WebAIM Contrast Checker (WCAG 2.1 AA criteria).
 
 ---
 
-## Step 2 — Scan Estático de Acessibilidade
+## Step 2 — Static Accessibility Scan
 
 ```bash
 node .claude/skills/morph-frontend-review/scripts/scan-accessibility.mjs $frontendPath
 ```
 
-O script detecta automaticamente a extensão dos arquivos para determinar Next.js (`.tsx`) vs
-Blazor (`.razor`). Se `frontendPath` não estiver definido, o script usa `.` (raiz do projeto).
+The script automatically detects file extensions to determine Next.js (`.tsx`) vs
+Blazor (`.razor`). If `frontendPath` is not defined, the script uses `.` (project root).
 
-**Checks implementados:**
+**Checks implemented:**
 
-| ID | Severidade | Arquivos | Verifica |
+| ID | Severity | Files | Checks |
 |----|-----------|---------|---------|
-| `IMG_MISSING_ALT` | CRITICAL | .tsx, .razor | `<img` sem atributo `alt=` |
-| `INPUT_MISSING_LABEL` | HIGH | .tsx, .razor | `<input`/`<InputText`/`<FluentTextField` sem `aria-label`, `aria-labelledby`, ou `<label for=` associado |
-| `HEADING_HIERARCHY` | HIGH | .tsx, .razor | Salto de nível em headings (H1→H3 pulando H2) |
-| `LINK_NO_TEXT` | HIGH | .tsx, .razor | `<a` vazio ou com apenas ícone e sem `aria-label` |
-| `BUTTON_NO_TEXT` | HIGH | .tsx, .razor | `<button`/`<FluentButton` sem texto e sem `aria-label` |
-| `AUTOPLAY_MEDIA` | MEDIUM | .tsx, .razor | `<video`/`<audio` com `autoPlay` sem `muted` |
-| `FLUENT_CHECKBOX_NO_LABEL` | MEDIUM | .razor | `<FluentCheckbox` sem `Label=` |
+| `IMG_MISSING_ALT` | CRITICAL | .tsx, .razor | `<img` missing `alt=` attribute |
+| `INPUT_MISSING_LABEL` | HIGH | .tsx, .razor | `<input`/`<InputText`/`<FluentTextField` without `aria-label`, `aria-labelledby`, or associated `<label for=` |
+| `HEADING_HIERARCHY` | HIGH | .tsx, .razor | Heading level skip (H1→H3 skipping H2) |
+| `LINK_NO_TEXT` | HIGH | .tsx, .razor | `<a` empty or with only icon and no `aria-label` |
+| `BUTTON_NO_TEXT` | HIGH | .tsx, .razor | `<button`/`<FluentButton` no text and no `aria-label` |
+| `AUTOPLAY_MEDIA` | MEDIUM | .tsx, .razor | `<video`/`<audio` with `autoPlay` without `muted` |
+| `FLUENT_CHECKBOX_NO_LABEL` | MEDIUM | .razor | `<FluentCheckbox` without `Label=` |
 
-**🚫 BLOCK** se qualquer finding CRITICAL ou count de HIGH ≥ 3.
+**🚫 BLOCK** if any CRITICAL finding or HIGH count ≥ 3.
 
-Corrija todos os CRITICALs antes de continuar. Para HIGH < 3, registre no resumo como warnings.
+Fix all CRITICALs before continuing. For HIGH < 3, record in summary as warnings.
 
 ---
 
-## Step 3 — Scan de Código Frontend (se contexto inclui implementation validation)
+## Step 3 — Frontend Code Scan (if context includes implementation validation)
 
-### Se NEXTJS ou FULLSTACK:
+### If NEXTJS or FULLSTACK:
 
 ```bash
 node .claude/skills/morph-code-review-nextjs/scripts/scan-nextjs.mjs $frontendPath
 ```
 
-> Pular se já executado pelo `post-implementation` na mesma sessão.
+> Skip if already run by `post-implementation` in the same session.
 
-**🚫 BLOCK** se CRITICAL findings encontrados.
+**🚫 BLOCK** if CRITICAL findings found.
 
-### Se DOTNET ou FULLSTACK (Blazor):
+### If DOTNET or FULLSTACK (Blazor):
 
-Verificar manualmente as categorias principais do checklist para o feature implementado:
+Manually verify the main checklist categories for the implemented feature:
 
 ```
-[ ] Componentes Blazor com parâmetros tipados corretamente
-[ ] EventCallback<T> para eventos — sem Action/Func diretos
-[ ] Dispose implementado onde há subscriptions (IDisposable)
-[ ] Sem lógica de negócio nos arquivos .razor (separar em @code ou classes)
-[ ] StateHasChanged() chamado apenas quando necessário
-[ ] Formulários com EditForm e DataAnnotationsValidator
-[ ] Campos obrigatórios com [Required] e mensagens de erro definidas
+[ ] Blazor components with correctly typed parameters
+[ ] EventCallback<T> for events — no direct Action/Func
+[ ] Dispose implemented where there are subscriptions (IDisposable)
+[ ] No business logic in .razor files (separate into @code or classes)
+[ ] StateHasChanged() called only when necessary
+[ ] Forms with EditForm and DataAnnotationsValidator
+[ ] Required fields with [Required] and defined error messages
 ```
 
-**🚫 BLOCK** se qualquer item CRITICAL for encontrado.
+**🚫 BLOCK** if any CRITICAL item is found.
 
 ---
 
-## Step 4 — Screenshots Responsivos (Playwright MCP)
+## Step 4 — Responsive Screenshots (Playwright MCP)
 
-### 4a. Detectar Dev Server
+### 4a. Detect Dev Server
 
 ```bash
 node .claude/skills/morph-post-implementation/scripts/detect-dev-server.mjs "$startCommand"
 ```
 
-### 4b. Se dev server disponível (exit 0):
+### 4b. If dev server available (exit 0):
 
-Extraia as URLs principais da feature lendo `spec.md`:
+Extract the main feature URLs by reading `spec.md`:
 
 ```bash
 Read: .morph/features/$ARGUMENTS/1-design/spec.md
 ```
 
-Para cada página principal (máximo 3), capture screenshots nos 3 breakpoints:
+For each main page (max 3), capture screenshots at 3 breakpoints:
 
 ```javascript
 // Mobile (375px)
 await mcp__playwright__browser_resize({ width: 375, height: 812 });
-await mcp__playwright__browser_navigate({ url: '<url-da-feature>' });
+await mcp__playwright__browser_navigate({ url: '<feature-url>' });
 await mcp__playwright__browser_take_screenshot({
   type: 'png',
   filename: `.morph/features/${ARGUMENTS}/visual-screenshots/mobile-<page>.png`
@@ -162,7 +165,7 @@ await mcp__playwright__browser_take_screenshot({
 
 // Tablet (768px)
 await mcp__playwright__browser_resize({ width: 768, height: 1024 });
-await mcp__playwright__browser_navigate({ url: '<url-da-feature>' });
+await mcp__playwright__browser_navigate({ url: '<feature-url>' });
 await mcp__playwright__browser_take_screenshot({
   type: 'png',
   filename: `.morph/features/${ARGUMENTS}/visual-screenshots/tablet-<page>.png`
@@ -170,45 +173,45 @@ await mcp__playwright__browser_take_screenshot({
 
 // Desktop (1440px)
 await mcp__playwright__browser_resize({ width: 1440, height: 900 });
-await mcp__playwright__browser_navigate({ url: '<url-da-feature>' });
+await mcp__playwright__browser_navigate({ url: '<feature-url>' });
 await mcp__playwright__browser_take_screenshot({
   type: 'png',
   filename: `.morph/features/${ARGUMENTS}/visual-screenshots/desktop-<page>.png`
 });
 ```
 
-Screenshots salvos em: `.morph/features/$ARGUMENTS/visual-screenshots/`
-(funciona tanto na fase `2-ui` quanto na `5-implement`)
+Screenshots saved to: `.morph/features/$ARGUMENTS/visual-screenshots/`
+(works in both phase `2-ui` and `5-implement`)
 
-### 4c. Se dev server NÃO disponível (exit 1):
+### 4c. If dev server NOT available (exit 1):
 
-**⚠️ ATENÇÃO: Dev server não encontrado.**
+**⚠️ WARNING: Dev server not found.**
 
-Solicite confirmação explícita ao usuário antes de pular os screenshots:
+Request explicit user confirmation before skipping screenshots:
 
 ```
-Dev server não detectado. Screenshots responsivos via Playwright não podem ser capturados.
+Dev server not detected. Responsive screenshots via Playwright cannot be captured.
 
-Opções:
-1. Inicie manualmente o servidor e re-execute /morph:frontend-review
-2. Confirme explicitamente que deseja pular os screenshots e por quê
+Options:
+1. Start the server manually and re-run /morph:frontend-review
+2. Explicitly confirm you want to skip screenshots and why
 
-Não é possível prosseguir para axe-core sem dev server.
+Cannot proceed to axe-core without dev server.
 ```
 
-**Aguarde resposta antes de continuar.**
+**Wait for response before continuing.**
 
 ---
 
-## Step 5 — axe-core Runtime (Playwright MCP, se dev server ativo)
+## Step 5 — axe-core Runtime (Playwright MCP, if dev server active)
 
-Para cada página da feature (usar as mesmas URLs do Step 4):
+For each feature page (use the same URLs from Step 4):
 
 ```javascript
-// Navegar para a página
-await mcp__playwright__browser_navigate({ url: '<url-da-feature>' });
+// Navigate to the page
+await mcp__playwright__browser_navigate({ url: '<feature-url>' });
 
-// Injetar axe-core via CDN e executar scan WCAG 2.1 AA
+// Inject axe-core via CDN and run WCAG 2.1 AA scan
 await mcp__playwright__browser_evaluate({
   function: `async () => {
     if (!window.axe) {
@@ -234,11 +237,11 @@ await mcp__playwright__browser_evaluate({
 });
 ```
 
-Agrupar violations por impacto:
-- `critical` / `serious` → **🚫 BLOCK** (não criar PR)
-- `moderate` / `minor` → reportar como warnings no resumo, não bloqueiam
+Group violations by impact:
+- `critical` / `serious` → **🚫 BLOCK** (do not create PR)
+- `moderate` / `minor` → report as warnings in summary, non-blocking
 
-Verificar também erros de console relacionados a acessibilidade:
+Also check for accessibility-related console errors:
 
 ```javascript
 await mcp__playwright__browser_console_messages({ level: 'error' });
@@ -248,111 +251,111 @@ await mcp__playwright__browser_console_messages({ level: 'error' });
 
 ## Step 6 — SEO Check (Next.js only)
 
-Varrer arquivos `page.tsx` da feature para verificar metadata:
+Scan feature `page.tsx` files to verify metadata:
 
 ```bash
-# Buscar páginas da feature
+# Find feature pages
 find . -name "page.tsx" -path "*$ARGUMENTS*" 2>/dev/null
 
-# Verificar se têm metadata
+# Check if they have metadata
 grep -l "export const metadata\|export async function generateMetadata" $(find . -name "page.tsx" -path "*$ARGUMENTS*" 2>/dev/null)
 ```
 
-Checklist por página:
+Checklist per page:
 
 ```
-[ ] export const metadata com title e description
-[ ] og:title e og:description (Open Graph)
-[ ] og:image definida (para compartilhamento social)
-[ ] Sem título duplicado entre páginas
-[ ] robots não bloqueia indexação das páginas públicas
+[ ] export const metadata with title and description
+[ ] og:title and og:description (Open Graph)
+[ ] og:image defined (for social sharing)
+[ ] No duplicate titles between pages
+[ ] robots doesn't block public page indexing
 ```
 
-> SEO não bloqueia PR — reportar como warnings no resumo final.
+> SEO doesn't block PR — report as warnings in final summary.
 
 ---
 
-## Step 7 — Checklist de Design Responsivo
+## Step 7 — Responsive Design Checklist
 
-Após visualizar os screenshots do Step 4:
+After viewing Step 4 screenshots:
 
 ```
-[ ] Mobile (375px): sem scroll horizontal, botões ≥ 44px, texto legível
-[ ] Tablet (768px): layout adapta (sidebar colapsa, grid ajusta colunas)
-[ ] Desktop (1440px): aproveita espaço disponível, sem conteúdo esticado
-[ ] Navegação funciona em todos os breakpoints
-[ ] Formulários acessíveis em mobile (labels visíveis, inputs grandes o suficiente)
+[ ] Mobile (375px): no horizontal scroll, buttons ≥ 44px, legible text
+[ ] Tablet (768px): layout adapts (sidebar collapses, grid adjusts columns)
+[ ] Desktop (1440px): uses available space, no stretched content
+[ ] Navigation works on all breakpoints
+[ ] Forms accessible on mobile (visible labels, large enough inputs)
 ```
 
-Se screenshots não foram capturados (dev server indisponível), marcar como "não verificado" e
-registrar no resumo.
+If screenshots were not captured (dev server unavailable), mark as "unverified" and
+record in summary.
 
 ---
 
-## Step 8 — Resumo e Artefatos
+## Step 8 — Summary and Artifacts
 
-Criar arquivo de resumo consolidado:
+Create consolidated summary file:
 
 ```bash
 mkdir -p ".morph/features/$ARGUMENTS/visual-screenshots"
 ```
 
-Salvar em `.morph/features/$ARGUMENTS/visual-screenshots/morph:frontend-review-summary.md`:
+Save to `.morph/features/$ARGUMENTS/visual-screenshots/morph:frontend-review-summary.md`:
 
 ```markdown
 # Frontend Review — {feature}
 
-**Data:** {data}
-**Stack:** {stack detectado}
-**Contexto:** design validation | implementation validation | ambos
+**Date:** {date}
+**Stack:** {detected stack}
+**Context:** design validation | implementation validation | both
 
-## Resultados
+## Results
 
 ### Step 1 — Design Outputs
 - validate-feature: ✅ PASS / 🚫 BLOCK
-- Outputs verificados: ui-design-system.md, ui-mockups.md, ui-components.md, ui-flows.md
-- Contraste WCAG: {resultado}
+- Outputs verified: ui-design-system.md, ui-mockups.md, ui-components.md, ui-flows.md
+- WCAG Contrast: {result}
 
-### Step 2 — Scan de Acessibilidade Estática
-- Arquivos escaneados: {N}
+### Step 2 — Static Accessibility Scan
+- Files scanned: {N}
 - Findings: {total} ({CRITICAL: N, HIGH: N, MEDIUM: N})
 - Status: ✅ PASS / 🚫 BLOCK
 
-### Step 3 — Scan de Código Frontend
-- Status: ✅ PASS / 🚫 BLOCK / ⏭️ pulado (já executado)
+### Step 3 — Frontend Code Scan
+- Status: ✅ PASS / 🚫 BLOCK / ⏭️ skipped (already run)
 
-### Step 4 — Screenshots Responsivos
-- Mobile (375px): {paths ou "não capturado"}
-- Tablet (768px): {paths ou "não capturado"}
-- Desktop (1440px): {paths ou "não capturado"}
+### Step 4 — Responsive Screenshots
+- Mobile (375px): {paths or "not captured"}
+- Tablet (768px): {paths or "not captured"}
+- Desktop (1440px): {paths or "not captured"}
 
 ### Step 5 — axe-core Runtime
-- Violations críticas/sérias: {N} → ✅ / 🚫
+- Critical/serious violations: {N} → ✅ / 🚫
 - Warnings (moderate/minor): {N}
 
 ### Step 6 — SEO (Next.js)
-- Páginas com metadata: {N}/{total}
-- Gaps: {lista ou "nenhum"}
+- Pages with metadata: {N}/{total}
+- Gaps: {list or "none"}
 
-## Status Geral
+## Overall Status
 
 **{✅ PASS / 🚫 BLOCK}**
 
-{Se BLOCK: motivo(s) listados aqui}
+{If BLOCK: reason(s) listed here}
 ```
 
 ---
 
-## Resumo dos BLOCKs
+## Block Summary
 
-| Step | Condição de BLOCK |
+| Step | Block Condition |
 |------|-------------------|
-| Step 1 | `validate-feature` falhou ou outputs obrigatórios ausentes |
-| Step 2 | Qualquer finding CRITICAL ou HIGH ≥ 3 no scan estático |
-| Step 3 | Qualquer finding CRITICAL no scan de código |
-| Step 5 | Dev server ativo + axe-core violations `critical` ou `serious` |
+| Step 1 | `validate-feature` failed or mandatory outputs missing |
+| Step 2 | Any CRITICAL finding or HIGH ≥ 3 in static scan |
+| Step 3 | Any CRITICAL finding in code scan |
+| Step 5 | Dev server active + axe-core violations `critical` or `serious` |
 
-**Todos os BLOCKs devem ser resolvidos antes de criar o PR (quando executado pós-implementação).**
+**All BLOCKs must be resolved before creating the PR (when run post-implementation).**
 
 ---
 

package/framework/skills/level-0-meta/morph-init/SKILL.md

@@ -125,13 +125,13 @@ uiLibrary:         shadcn | fluent-ui | mudblazor | null
 monorepo:          true | false
 frontendPath:      src/frontend (if monorepo)
 backendPath:       src/backend (if monorepo)
-architectureStyle: vertical-slice | null   ← novo
+architectureStyle: vertical-slice | null   ← new
 ```
 
-**VSA detection:** `architectureStyle: "vertical-slice"` se qualquer um destes existir:
-- `Abstractions/IHandler.cs` encontrado pelo Glob
-- `Pipelines/ValidationDecorator.cs` encontrado pelo Glob
-- 2+ pastas com sufixo `Feature` em `Features/` (ex: `BookFeature`, `OrderFeature`)
+**VSA detection:** `architectureStyle: "vertical-slice"` if any of these exist:
+- `Abstractions/IHandler.cs` found by Glob
+- `Pipelines/ValidationDecorator.cs` found by Glob
+- 2+ folders with `Feature` suffix in `Features/` (e.g., `BookFeature`, `OrderFeature`)
 
 ---
 
@@ -143,9 +143,9 @@ Ask at most 3 questions, only those that apply:
 
 | # | Question | Condition | Purpose |
 |---|----------|-----------|---------|
-| 1 | *"Em uma frase: qual é o objetivo principal do **[ProjectName]**?"* | Always | README.md Overview |
-| 2 | *"Confirmo: frontend em `{frontendPath}`, backend em `{backendPath}`. Correto?"* | Monorepo detected | Validate paths before persisting |
-| 3 | *"Supabase Cloud (managed) ou self-hosted?"* | Supabase detected | MCP URL configuration |
+| 1 | *"In one sentence: what is the main purpose of **[ProjectName]**?"* | Always | README.md Overview |
+| 2 | *"Confirmed: frontend at `{frontendPath}`, backend at `{backendPath}`. Correct?"* | Monorepo detected | Validate paths before persisting |
+| 3 | *"Supabase Cloud (managed) or self-hosted?"* | Supabase detected | MCP URL configuration |
 
 Do **not** ask about technology already confirmed by file evidence.
 
@@ -200,7 +200,7 @@ Read `.morph/config/config.json` and merge into `project`:
 }
 ```
 
-**Se `architectureStyle: "vertical-slice"` foi detectado no Step 3**, adicione também:
+**If `architectureStyle: "vertical-slice"` was detected in Step 3**, also add:
 
 ```json
 {
@@ -210,7 +210,7 @@ Read `.morph/config/config.json` and merge into `project`:
 }
 ```
 
-E informe o usuário:
+And inform the user:
 
 ```
 ✓ Detected: Vertical Slice Architecture (IHandler.cs / *Feature folders)
@@ -218,12 +218,12 @@ E informe o usuário:
   → morph-spec will use vsa-architect + contracts-vsa.cs for features
 ```
 
-> Esta key é o que ativa o `vsa-architect` em vez do `domain-architect` durante `/morph-proposal`.
+> This key is what activates `vsa-architect` instead of `domain-architect` during `/morph-proposal`.
 
-**Se o projeto ainda não existe (novo projeto VSA do zero)**, informe também:
+**If the project doesn't exist yet (new VSA project from scratch)**, also inform:
 
 ```
-Para criar um novo projeto VSA:
+To create a new VSA project:
    dotnet new install https://github.com/polymorphism-tech/Morph_Template_VerticalSliceArchitecture
    dotnet new vsa -n MyProject
    cd MyProject && npx morph-spec init
@@ -324,6 +324,35 @@ Use `AskUserQuestion` with header `"{MCP} failed"` and these options:
 
 ---
 
+## Step 7.7 — Run Doctor
+
+After all configuration is complete, run the health check to verify everything is properly installed:
+
+```bash
+npx morph-spec doctor
+```
+
+This validates: config.json integrity, agents.json presence, hooks installation, skills distribution, required command files, and state.json schema version. Fix any reported issues before proceeding.
+
+---
+
+## Step 7.8 — Workflow Selection
+
+If the project stack suggests a non-standard workflow, ask the user:
+
+| Stack | Default Workflow | Alternative |
+|-------|-----------------|-------------|
+| Node.js CLI (no UI) | `nodejs-cli` (skips uiux/clarify/sync) | `standard` |
+| .NET + Blazor | `standard` (all phases) | — |
+| Next.js | `standard` (all phases) | — |
+
+For Node.js CLI projects, update config:
+```json
+{ "workflow": "nodejs-cli" }
+```
+
+---
+
 ## Step 8 — Final Output
 
 Before printing the summary, check `~/.claude/settings.local.json` for `env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS`. If set to `"1"`, mark Agent Teams as enabled; otherwise show the warning.