@polymorphism-tech/morph-spec 4.3.7 → 4.6.0

package/framework/skills/level-1-workflows/phase-tasks/references/tasks-example.md

@@ -0,0 +1,231 @@
+# Tasks - Photo Processing Pipeline
+
+> Example of a well-structured tasks.md. This is a filled-in reference — not a template.
+> All tasks are atomic (15–60 min), independently commitable, and directly traceable to spec.md.
+
+| Task ID | Type | Title | Status |
+|---------|------|-------|--------|
+| T001 | Contract | Define C# contracts and interfaces | Done |
+| T002 | Domain | Create ProcessingJob entity and enum | Done |
+| T003 | Infra | EF Core migration and DbContext setup | Done |
+| T004 | Infra | Azure Blob Storage service | Done |
+| T005 | Service | Implement PhotoProcessingService | In Progress |
+| T006 | Job | Implement Hangfire background job | Pending |
+| T007 | API | Upload and status endpoints (Minimal API) | Pending |
+| T008 | UI | Blazor upload page component | Pending |
+| T009 | UI | Blazor status polling page | Pending |
+| T010 | Test | Unit tests for PhotoProcessingService | Pending |
+| T011 | Test | Integration tests for upload + status API | Pending |
+
+**Status Values:** `Pending | In Progress | Blocked | Done`
+
+---
+
+## Phase 1: Contracts & Data Model
+
+### T001: Define C# contracts and interfaces
+- **Type:** Contract
+- **Priority:** 1
+- **Estimate:** 30min
+- **Assigned:** dotnet-senior
+- **Dependencies:** None
+
+**Description:**
+Define all service interfaces, command/result records, and DTOs needed for the feature. These become the API contract other tasks depend on — implement data model and services against these interfaces.
+
+**Deliverables:**
+- [ ] Create: `src/Application/PhotoProcessing/Interfaces/IPhotoProcessingService.cs`
+- [ ] Create: `src/Application/PhotoProcessing/Commands/UploadPhotoCommand.cs`
+- [ ] Create: `src/Application/PhotoProcessing/Queries/GetJobStatusQuery.cs`
+- [ ] Create: `src/Application/PhotoProcessing/DTOs/JobStatusDto.cs`
+
+---
+
+### T002: Create ProcessingJob entity and enum
+- **Type:** Domain
+- **Priority:** 1
+- **Estimate:** 30min
+- **Assigned:** dotnet-senior
+- **Dependencies:** T001
+
+**Description:**
+Create the `ProcessingJob` domain entity and `ProcessingStatus` enum per the data model in spec.md. Entity must use private setters and expose domain methods for state transitions (`MarkProcessing()`, `MarkCompleted()`, `MarkFailed()`).
+
+**Deliverables:**
+- [ ] Create: `src/Domain/Entities/ProcessingJob.cs`
+- [ ] Create: `src/Domain/Enums/ProcessingStatus.cs`
+
+---
+
+### T003: EF Core migration and DbContext setup
+- **Type:** Infrastructure
+- **Priority:** 1
+- **Estimate:** 45min
+- **Assigned:** dotnet-senior
+- **Dependencies:** T002
+
+**Description:**
+Add `ProcessingJob` to `AppDbContext`, configure via Fluent API (column lengths, indexes, defaults), and create initial migration. Verify migration applies cleanly to a local SQL Server instance.
+
+**Deliverables:**
+- [ ] Update: `src/Infrastructure/Persistence/AppDbContext.cs`
+- [ ] Create: `src/Infrastructure/Persistence/Configurations/ProcessingJobConfiguration.cs`
+- [ ] Run: `dotnet ef migrations add AddProcessingJob`
+- [ ] Verify: migration applies without errors
+
+---
+
+## Phase 2: Infrastructure Services
+
+### T004: Azure Blob Storage service
+- **Type:** Infrastructure
+- **Priority:** 1
+- **Estimate:** 45min
+- **Assigned:** azure-architect
+- **Dependencies:** None
+
+**Description:**
+Implement `IBlobStorageService` with upload and generate-URL operations using `Azure.Storage.Blobs` SDK. Register as scoped in DI. Add connection string to `appsettings.json` (placeholder) and Key Vault reference for production.
+
+**Deliverables:**
+- [ ] Create: `src/Infrastructure/Storage/IBlobStorageService.cs`
+- [ ] Create: `src/Infrastructure/Storage/AzureBlobStorageService.cs`
+- [ ] Create: `src/Infrastructure/Storage/FakeBlobStorageService.cs` (for simulation mode)
+- [ ] Update: `src/Infrastructure/DependencyInjection.cs`
+
+---
+
+### T005: Implement PhotoProcessingService
+- **Type:** Service
+- **Priority:** 2
+- **Estimate:** 1h
+- **Assigned:** dotnet-senior
+- **Dependencies:** T001, T002, T003, T004
+
+**Description:**
+Implement `IPhotoProcessingService` with `UploadAsync` (validate → blob upload → create job → enqueue Hangfire job) and `GetStatusAsync`. Use result pattern for validation errors; throw `NotFoundException` for missing jobs.
+
+**Deliverables:**
+- [ ] Create: `src/Application/PhotoProcessing/PhotoProcessingService.cs`
+- [ ] Update: `src/Application/DependencyInjection.cs`
+
+---
+
+### T006: Implement Hangfire background job
+- **Type:** Job
+- **Priority:** 2
+- **Estimate:** 1h
+- **Assigned:** dotnet-senior
+- **Dependencies:** T002, T004
+
+**Description:**
+Implement `IPhotoProcessingJob` that: sets status = Processing → downloads original from Blob → calls AI API → uploads processed photo → sets status = Completed. On exception: increment RetryCount, set Failed if >= 3. Add `[AutomaticRetry(Attempts = 3)]` attribute.
+
+**Deliverables:**
+- [ ] Create: `src/Application/PhotoProcessing/PhotoProcessingJob.cs`
+- [ ] Create: `src/Application/PhotoProcessing/FakePhotoProcessingJob.cs` (simulation mode)
+
+---
+
+## Phase 3: API Endpoints
+
+### T007: Upload and status endpoints (Minimal API)
+- **Type:** API
+- **Priority:** 2
+- **Estimate:** 45min
+- **Assigned:** dotnet-senior
+- **Dependencies:** T005
+
+**Description:**
+Create two endpoints per spec.md:
+- `POST /api/upload` — multipart/form-data, returns `{ jobId }`, maps to `UploadPhotoCommand`
+- `GET /api/status/{jobId}` — returns `JobStatusDto`
+- `GET /api/download/{jobId}` — redirects to Blob URL if Completed, else 404
+
+**Deliverables:**
+- [ ] Create: `src/Web/Endpoints/PhotoProcessingEndpoints.cs`
+- [ ] Update: `src/Web/Program.cs` to register endpoint group
+
+---
+
+## Phase 4: UI Components
+
+### T008: Blazor upload page component
+- **Type:** UI
+- **Priority:** 2
+- **Estimate:** 1h
+- **Assigned:** blazor-builder
+- **Dependencies:** T007
+
+**Description:**
+Blazor Server page at `/upload`. File input with client-side validation (type + size before submit). Loading state during upload. Redirect to `/processing/{jobId}` on success. Error message display per spec wireframe.
+
+**Deliverables:**
+- [ ] Create: `src/Web/Pages/Upload.razor`
+- [ ] Create: `src/Web/Pages/Upload.razor.cs`
+
+---
+
+### T009: Blazor status polling page
+- **Type:** UI
+- **Priority:** 3
+- **Estimate:** 1h
+- **Assigned:** blazor-builder
+- **Dependencies:** T007
+
+**Description:**
+Blazor Server page at `/processing/{jobId}`. Polls `GET /api/status/{jobId}` every 5 seconds using `PeriodicTimer`. Shows status label + progress indicator. "Download" button when Completed. "Retry" suggestion when Failed. Stops polling on terminal state.
+
+**Deliverables:**
+- [ ] Create: `src/Web/Pages/ProcessingStatus.razor`
+- [ ] Create: `src/Web/Pages/ProcessingStatus.razor.cs`
+
+---
+
+## Phase 5: Tests
+
+### T010: Unit tests for PhotoProcessingService
+- **Type:** Test
+- **Priority:** 2
+- **Estimate:** 1h
+- **Assigned:** dotnet-senior
+- **Dependencies:** T005
+
+**Description:**
+Unit tests covering: happy path upload, invalid file type rejection, file too large rejection, status retrieval for each status value, not-found case. Use Moq for `IBlobStorageService` and `IProcessingJobRepository`. FluentAssertions for assertions.
+
+**Deliverables:**
+- [ ] Create: `tests/Unit/Application/PhotoProcessing/PhotoProcessingServiceTests.cs`
+
+---
+
+### T011: Integration tests for upload + status API
+- **Type:** Test
+- **Priority:** 3
+- **Estimate:** 1h
+- **Assigned:** dotnet-senior
+- **Dependencies:** T007, T010
+
+**Description:**
+Integration tests using `WebApplicationFactory` + in-memory SQLite (or TestContainers for SQL Server). Tests: POST /api/upload returns 200 with jobId, GET /api/status/{jobId} returns correct status, GET /api/download/{completedJobId} returns redirect.
+
+**Deliverables:**
+- [ ] Create: `tests/Integration/Api/PhotoProcessingEndpointTests.cs`
+- [ ] Create: `tests/Integration/Fixtures/PhotoProcessingApiFixture.cs`
+
+---
+
+## Summary
+
+| Phase | Tasks | Estimate |
+|-------|-------|----------|
+| Contracts & Data Model | T001–T003 | 1h45m |
+| Infrastructure Services | T004–T006 | 2h45m |
+| API Endpoints | T007 | 45m |
+| UI Components | T008–T009 | 2h |
+| Tests | T010–T011 | 2h |
+| **Total** | **11 tasks** | **~9h15m** |
+
+---
+
+*MORPH-SPEC by Polymorphism Tech*

package/framework/skills/level-1-workflows/phase-tasks/scripts/validate-tasks.mjs

@@ -0,0 +1,112 @@
+#!/usr/bin/env node
+/**
+ * validate-tasks.mjs
+ *
+ * Validates a MORPH-SPEC tasks.md file for structure and completeness.
+ * Executed locally by Claude via Bash — output returned to Claude.
+ *
+ * Usage:
+ *   node validate-tasks.mjs <tasks-file>
+ *   node validate-tasks.mjs .morph/features/my-feature/3-tasks/tasks.md
+ *
+ * Checks:
+ *   - Summary table exists with T### IDs and valid statuses
+ *   - Each task header has T### format
+ *   - Each task has Type, Priority, Estimate, Dependencies fields
+ *   - Each task has at least one deliverable checkbox
+ *   - Task IDs are sequential (no gaps)
+ *   - Reports counts by status
+ */
+
+import { readFileSync, existsSync } from 'fs';
+
+const taskFile = process.argv[2];
+
+if (!taskFile) {
+  console.error(JSON.stringify({ error: 'Usage: validate-tasks.mjs <tasks-file>' }));
+  process.exit(1);
+}
+
+if (!existsSync(taskFile)) {
+  console.error(JSON.stringify({ error: `File not found: ${taskFile}` }));
+  process.exit(1);
+}
+
+const content = readFileSync(taskFile, 'utf-8');
+const lines = content.split('\n');
+
+const errors = [];
+const warnings = [];
+
+// 1. Parse summary table (| T001 | Type | Title | Status |)
+const tableRows = lines.filter(l => /^\|\s*T\d{3}/.test(l));
+const VALID_STATUSES = new Set(['Pending', 'In Progress', 'Blocked', 'Done']);
+const summaryTasks = [];
+
+for (const row of tableRows) {
+  const parts = row.split('|').map(s => s.trim()).filter(Boolean);
+  if (parts.length < 4) continue;
+  const [id, , , status] = parts;
+  summaryTasks.push({ id, status });
+  if (!VALID_STATUSES.has(status)) {
+    errors.push(`Task ${id}: invalid status '${status}' — must be one of: ${[...VALID_STATUSES].join(', ')}`);
+  }
+}
+
+if (summaryTasks.length === 0) {
+  errors.push('No summary table found — expected rows matching | T### | Type | Title | Status |');
+}
+
+// 2. Parse task headers (### T001: Title)
+const taskHeaders = lines
+  .map((l, i) => ({ line: i + 1, match: l.match(/^###\s+(T\d{3}):\s+(.+)/) }))
+  .filter(r => r.match);
+
+// Check sequential IDs
+const ids = taskHeaders.map(r => parseInt(r.match[1].slice(1)));
+for (let i = 0; i < ids.length; i++) {
+  if (ids[i] !== i + 1) {
+    warnings.push(`Task ID gap or duplicate near T${String(ids[i]).padStart(3, '0')} (expected T${String(i + 1).padStart(3, '0')})`);
+    break;
+  }
+}
+
+// 3. Check each task section has required fields
+for (const { line, match } of taskHeaders) {
+  const taskId = match[1];
+  // Collect lines in this task section (until next ### or end)
+  const start = line; // 1-indexed
+  let end = lines.length;
+  for (let i = start; i < lines.length; i++) {
+    if (i > start - 1 && /^#{1,3}\s/.test(lines[i])) { end = i; break; }
+  }
+  const section = lines.slice(start, end).join('\n');
+
+  if (!/\*\*Type:\*\*/.test(section))       errors.push(`${taskId}: missing **Type:** field`);
+  if (!/\*\*Priority:\*\*/.test(section))   errors.push(`${taskId}: missing **Priority:** field`);
+  if (!/\*\*Estimate:\*\*/.test(section))   errors.push(`${taskId}: missing **Estimate:** field`);
+  if (!/\*\*Dependencies:\*\*/.test(section)) warnings.push(`${taskId}: missing **Dependencies:** field`);
+  if (!/- \[ \]/.test(section))             warnings.push(`${taskId}: no deliverable checkboxes found`);
+}
+
+// 4. Status counts
+const statusCounts = {};
+for (const { status } of summaryTasks) {
+  statusCounts[status] = (statusCounts[status] ?? 0) + 1;
+}
+
+const result = {
+  file: taskFile,
+  valid: errors.length === 0,
+  tasks: {
+    total: summaryTasks.length,
+    byStatus: statusCounts,
+    completed: statusCounts['Done'] ?? 0,
+    remaining: (summaryTasks.length) - (statusCounts['Done'] ?? 0),
+  },
+  errors,
+  warnings,
+};
+
+console.log(JSON.stringify(result, null, 2));
+process.exit(errors.length > 0 ? 1 : 0);

package/framework/skills/level-1-workflows/phase-uiux/SKILL.md

@@ -0,0 +1,246 @@
+---
+name: phase-uiux
+description: MORPH-SPEC Phase 1.5 (UI/UX). Creates design-system.md, mockups.md, components.md, and flows.md using Figma/Playwright/Context7 MCPs. Use after setup for features with frontend UI components, pages, dashboards, forms, wizards, or visual interactions requiring design documentation.
+argument-hint: "[feature-name]"
+user-invocable: false
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+# MORPH UI/UX Design - FASE 1.5
+
+> INTERNAL: Workflow skill used by /morph-proposal during automated phase orchestration. Not a user command.
+
+Fase condicional para features com front-end. Coleta requisitos de UI/UX, gera wireframes, specs de componentes e fluxos de usuário.
+
+## Pré-requisitos
+
+- [ ] FASE 1 (Setup) concluída
+- [ ] Feature tem keywords de UI detectadas (blazor, ui, component, page, dashboard, wizard, form, chart)
+- [ ] `uiux-designer` agent ativado
+
+## Ferramentas Recomendadas
+
+> **Ref:** `framework/skills/level-0-meta/tool-usage-guide/SKILL.md` para guia completo.
+> **Ref:** `framework/standards/integration/mcp/mcp-tools.md` para referência MCP.
+
+| Ação | Ferramenta | Alternativa |
+|------|------------|-------------|
+| Verificar design system existente | **Read** `.morph/context/design-system.md` | — |
+| Ler screenshots do usuário | **Read** (arquivo de imagem) | — |
+| Buscar variáveis CSS existentes | **Grep** `--root:` em `*.css,*.scss` | — |
+| Encontrar componentes existentes | **Glob** `**/Components/**/*.razor` ou `**/components/**/*.tsx` | — |
+| Extrair design tokens do Figma | **Figma MCP** `get_file({ fileKey })` | Read CSS/SCSS variables |
+| Documentação de componentes UI | **Context7 MCP** `query_docs({ libraryId, query })` | **WebSearch** + **WebFetch** |
+| 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 |
+| Testar layout responsivo | **Playwright MCP** `browser_resize()` + `browser_take_screenshot()` | Manual testing |
+| Referências de design externas | **WebSearch** + **WebFetch** | — |
+| Renderizar templates UI | **Bash** `npx morph-spec template render docs/ui-mockups ...` | — |
+| Gerar design system de CSS existente | **Bash** `npx morph-spec generate design-system --scan` | — |
+| Atualizar state | **Bash** `npx morph-spec state mark-output ...` | — |
+
+**MCPs desta fase:** Figma (design tokens), Playwright (preview, inspeção, responsividade), Context7 (docs de componentes).
+
+**Anti-padrões:**
+- ❌ WebSearch para docs MudBlazor (use Context7 MCP — mais preciso)
+- ❌ Task agent para ler um screenshot (use Read direto na imagem)
+- ❌ Adivinhar props de componentes (use Context7 para API real)
+
+---
+
+## Workflow
+
+### Passo 0: Verificar Design System Existe
+
+**CRITICAL:** Antes de iniciar a FASE UI/UX, verifique se um design system existe:
+
+```bash
+npx morph-spec detect-agents "{feature description}"
+```
+
+Se nenhum design system for detectado (verificar output):
+
+1. **Opção A - Scaffold automático:**
+   - O sistema criará automaticamente um design system ao avançar para implementação
+   - Você pode gerar manualmente agora: `npx morph-spec generate design-system`
+
+2. **Opção B - Criar manualmente:**
+   - Crie `.morph/context/design-system.md` (project-level, compartilhado)
+   - Ou `.morph/features/$ARGUMENTS/2-ui/design-system.md` (feature-specific)
+
+3. **Opção C - Scan existing CSS:**
+   - Se o projeto já tem CSS com variáveis: `npx morph-spec generate design-system --scan`
+
+**⚠️ IMPORTANTE:**
+- Design system é **obrigatório** para features UI
+- Gate automático bloqueará implementação (FASE 5) se design system não existir
+- Melhor criar agora para garantir consistência visual
+
+### Passo 1: Detectar Se Fase É Necessária
+
+Verifique se agentes ativos incluem `uiux-designer`:
+
+```bash
+npx morph-spec state get $ARGUMENTS
+```
+
+Se `uiux-designer` NÃO estiver nos `activeAgents`, pule esta fase e continue para FASE 2 (Design).
+
+### Passo 2: Coletar Input do Usuário
+
+**SEMPRE perguntar ao usuário PRIMEIRO:**
+
+1. **Layout e estilo**:
+   - Você tem alguma ideia de layout em mente?
+   - Tem alguma referência visual? (sites, apps, screenshots)
+   - Como imagina o fluxo do usuário?
+
+2. **Componentes e interações**:
+   - Quais os principais componentes desta tela/página?
+   - Quais estados precisam ser considerados? (loading, error, empty, success)
+
+3. **Imagens de referência**:
+   - Tem imagens de exemplo que eu possa analisar?
+   - Se SIM: use Read tool para ler screenshots e extrair padrões
+
+### Passo 3: Decidir Biblioteca UI
+
+Escolha entre **Fluent UI Blazor** (recomendado para AI-first) ou **MudBlazor** (componentes complexos):
+
+**Critérios:**
+- Fluent UI: Para dashboards, forms simples, AI components, Microsoft design language
+- MudBlazor: Para data grids avançadas, charts complexos, material design
+
+**Documente a decisão em `decisions.md`.**
+
+### Passo 4: Gerar Deliverables
+
+Crie os seguintes arquivos em `.morph/features/$ARGUMENTS/`:
+
+> **Use templates:** Utilize `npx morph-spec template render` para gerar os arquivos a partir dos templates em `.morph/framework/templates/docs/`. Templates disponíveis: `ui-design-system`, `ui-mockups`, `ui-components`, `ui-flows`.
+
+#### 4.1. `ui-design-system.md`
+
+**Se design system project-level existe (`.morph/context/design-system.md`):**
+- Referencie-o nos specs: "Uses project design system at .morph/context/design-system.md"
+- Crie `ui-design-system.md` apenas se houver cores/componentes **específicos** da feature
+
+**Se não existe:**
+- Crie design system feature-level completo com:
+  - Paleta de cores (primary, secondary, accent, semantic)
+  - Tipografia (heading scales, body text, code)
+  - Spacing e layout (grid, margins, paddings)
+  - Componentes base (buttons, inputs, cards)
+
+#### 4.2. `ui-mockups.md`
+
+Wireframes ASCII + descrições:
+- Layout geral de cada tela/página
+- Posicionamento de componentes
+- Responsividade (desktop, tablet, mobile)
+- Estados (loading, error, empty, success)
+
+#### 4.3. `ui-components.md`
+
+Specs técnicas de componentes Fluent UI/MudBlazor:
+- Componente a usar (FluentButton, MudDataGrid, etc.)
+- Props e configurações
+- Eventos e bindings
+- Validações e estados
+
+#### 4.4. `ui-flows.md`
+
+Fluxos de usuário completos:
+- User stories
+- Diagramas de fluxo (texto/ASCII)
+- Edge cases (o que acontece se...?)
+- Validações e feedback
+
+### CHECKPOINT: Validar Deliverables UI
+
+**⏸️ PAUSE - Antes de prosseguir para acessibilidade:**
+
+- [ ] Design system definido (project-level ou feature-level)?
+- [ ] Wireframes cobrem TODOS os estados (loading, error, empty, success)?
+- [ ] Componentes especificados com props reais da biblioteca UI escolhida?
+- [ ] Fluxos de usuário completos com edge cases?
+- [ ] Biblioteca UI escolhida documentada como ADR em `decisions.md`?
+
+**❌ Se alguma checkbox NÃO estiver marcada:**
+→ Voltar e completar o deliverable faltante
+
+**✅ Se TODAS as checkboxes estiverem marcadas:**
+→ Prosseguir para validação de acessibilidade
+
+---
+
+### Passo 5: Validar Acessibilidade e Responsividade
+
+Documente nos arquivos UI:
+- **WCAG 2.1 Level AA** compliance
+  - Contraste de cores adequado
+  - Labels acessíveis para screen readers
+  - Navegação por teclado
+- **Responsive breakpoints**
+  - Desktop (>1200px)
+  - Tablet (768px - 1199px)
+  - Mobile (<768px)
+
+### Passo 6: Atualizar State
+
+```bash
+npx morph-spec state set $ARGUMENTS phase uiux-design
+npx morph-spec state mark-output $ARGUMENTS ui-design-system
+npx morph-spec state mark-output $ARGUMENTS ui-mockups
+npx morph-spec state mark-output $ARGUMENTS ui-components
+npx morph-spec state mark-output $ARGUMENTS ui-flows
+```
+
+> **Nota sobre formatos:** Os comandos `mark-output` aceitam TANTO kebab-case (`ui-design-system`)
+> QUANTO camelCase (`uiDesignSystem`). Ambos os formatos funcionam igualmente! Use o que for mais
+> confortável para você. Exemplos:
+> - `npx morph-spec state mark-output my-feature uiDesignSystem` ✅
+> - `npx morph-spec state mark-output my-feature ui-design-system` ✅
+
+## Outputs Gerados
+
+- `.morph/features/$ARGUMENTS/2-ui/design-system.md`
+- `.morph/features/$ARGUMENTS/2-ui/mockups.md`
+- `.morph/features/$ARGUMENTS/2-ui/components.md`
+- `.morph/features/$ARGUMENTS/2-ui/flows.md`
+- `.morph/features/$ARGUMENTS/1-design/decisions.md` (atualizado com ADR UI library)
+
+## PAUSA OBRIGATÓRIA
+
+Apresente ao usuário 3 ações sugeridas:
+
+1. **Aprovar UI/UX e prosseguir para design técnico**
+2. **Ajustar wireframes/componentes de telas específicas**
+3. **Revisar biblioteca UI escolhida (Fluent UI / MudBlazor)**
+
+## Critérios de Avanço
+
+- [x] Input do usuário coletado (layout, referências)
+- [x] Biblioteca UI escolhida e justificada (ADR)
+- [x] 4 deliverables criados (design-system, mockups, components, flows)
+- [x] Acessibilidade WCAG 2.1 documentada
+- [x] Responsividade especificada
+- [x] State atualizado
+- [x] Usuário aprovou UI/UX
+
+---
+
+## Outputs desta Fase
+
+<!-- morph:outputs:uiux -->
+| Output | Caminho |
+|--------|---------|
+| `uiDesignSystem` | `.morph/features/{feature}/2-ui/design-system.md` |
+| `uiMockups` | `.morph/features/{feature}/2-ui/mockups.md` |
+| `uiComponents` | `.morph/features/{feature}/2-ui/components.md` |
+| `uiFlows` | `.morph/features/{feature}/2-ui/flows.md` |
+<!-- /morph:outputs -->
+
+---
+
+Continuar automaticamente para FASE 2 (Design) após aprovação.