@polymorphism-tech/morph-spec 4.3.7 → 4.6.0

package/framework/{skills/level-2-domains → agents}/integrations/clerk-auth.md

@@ -1,6 +1,10 @@
-# Clerk Auth
+---
+name: clerk-auth
+description: Clerk Auth specialist for Clerk SDK integration, social login, JWT session management, and user management in Next.js and .NET projects. Use when integrating Clerk authentication, implementing social login flows, managing user sessions with Clerk JWT, or protecting routes with Clerk middleware.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** clerk, auth, login, signup, authentication, session, jwt, user
+# Clerk Auth
 
 Autenticação SaaS com Clerk para .NET/Blazor. SDK: `Clerk.Net.AspNetCore.Security`.
 
@@ -105,4 +109,4 @@ public class ClerkWebhookController(IUserService users) : ControllerBase
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

package/framework/{skills/level-2-domains/integrations/hangfire-orchestrator.md → agents/integrations/hangfire-integration.md}

@@ -1,3 +1,9 @@
+---
+name: hangfire-orchestrator-integration
+description: Hangfire integration specialist for connecting background jobs with external services, implementing webhook handlers, and building event-driven workflows in .NET. Use when integrating Hangfire with third-party APIs, processing webhooks asynchronously, or designing event-driven job pipelines.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
 # Hangfire Orchestrator
 
 **Tier:** 3 (Specialist)
@@ -61,4 +67,4 @@ framework/standards/backend/integrations/hangfire/jobs.md
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

package/framework/{skills/level-2-domains → agents}/integrations/resend-email.md

@@ -1,6 +1,10 @@
-# Resend Email
+---
+name: resend-email
+description: Resend Email specialist for transactional email, HTML/React email templates, Resend API integration, and notification systems in .NET and Next.js. Use when implementing email notifications, integrating Resend API, creating transactional email templates, or configuring email delivery in MORPH-SPEC projects.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** resend, email, envio, transactional, notification, send email, template
+# Resend Email
 
 Transactional email via Resend for .NET. REST API, no official SDK. Simple, developer-friendly.
 
@@ -116,4 +120,4 @@ public interface IEmailService
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

package/framework/{skills/level-2-domains → agents}/quality/code-analyzer.md

@@ -1,11 +1,15 @@
-# Code Analyzer
+---
+name: code-analyzer
+description: Code Analyzer specialist for refactoring, complexity analysis, technical debt assessment, and identifying code smells in .NET/TypeScript codebases. Use when analyzing code quality, identifying refactoring opportunities, assessing technical debt, or reviewing code for duplication and architecture violations.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** analyze, review, refactor, clean, smell, duplicate, architecture, quality, debt, unused, dead code, code review, code quality
+# Code Analyzer
 
 Deep code analysis specialist. Automates architecture review, clean code checks, and duplication detection.
 
-> **Ref:** `framework/standards/coding.md` for naming conventions.
-> **Ref:** `framework/standards/architecture.md` for architectural patterns.
+> **Ref:** `framework/standards/core/coding.md` for naming conventions.
+> **Ref:** `framework/standards/core/architecture.md` for architectural patterns.
 > **Ref:** `.claude/skills/checklists/code-review.md` for runtime pattern checks.
 
 ---
@@ -232,4 +236,4 @@ After analysis, generate a summary:
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

package/framework/{skills/level-2-domains → agents}/quality/testing-specialist.md

@@ -1,6 +1,10 @@
-# Testing Specialist
+---
+name: testing-specialist
+description: Testing Specialist for test strategy, TDD/BDD implementation, unit and integration tests using xUnit, Vitest, and Jest, and quality assurance automation. Use when designing test strategies, implementing TDD cycles, writing unit/integration tests, or improving test coverage in .NET and TypeScript projects.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
 
-> **Layer:** 2 | **Load:** on-keyword | **Keywords:** test, testing, mock, fake, simulation, unit test, integration test
+# Testing Specialist
 
 Especialista em testes, mocking e simulação para projetos .NET.
 
@@ -123,4 +127,4 @@ services.AddSingleton<IReplicateClient, FakeReplicateClient>();
 
 ---
 
-*MORPH-SPEC by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

package/framework/commands/morph-apply.md

@@ -60,7 +60,7 @@ Para completar as fases de planejamento, execute:
 
 ### Arquivos Necessários
 
-- [ ] Feature existe em `.morph/project/outputs/{feature}/`
+- [ ] Feature existe em `.morph/features/{feature}/`
 - [ ] `spec.md` está aprovado
 - [ ] `tasks.json` tem tasks definidas
 - [ ] `contracts.cs` define as interfaces
@@ -68,10 +68,10 @@ Para completar as fases de planejamento, execute:
 ## Workflow
 
 1. **Carregue o contexto**:
-   - Leia `.morph/project/outputs/{feature}/spec.md`
-   - Leia `.morph/project/outputs/{feature}/tasks.json`
-   - Leia `.morph/project/outputs/{feature}/contracts.cs`
-   - Leia framework/standards/ e .morph/project/standards/ para padrões
+   - Leia `.morph/features/{feature}/1-design/spec.md`
+   - Leia `.morph/features/{feature}/3-tasks/tasks.md`
+   - Leia `.morph/features/{feature}/1-design/contracts.cs`
+   - Leia framework/standards/ e .morph/context/ para padrões
 
 2. **Inicialize state tracking**:
    ```bash
@@ -116,11 +116,11 @@ Para completar as fases de planejamento, execute:
 
 ## Padrões Obrigatórios
 
-Siga sempre (priorize project/standards/ se houver):
+Siga sempre (priorize context/ se houver):
 - `framework/standards/coding.md` - Padrões base do MORPH
-- `.morph/project/standards/coding.md` - Padrões específicos do projeto
-- `.morph/project/standards/architecture.md` - Estrutura de projeto
-- `.morph/project/standards/azure.md` - Recursos e custos
+- `.morph/context/coding.md` - Padrões específicos do projeto
+- `.morph/context/architecture.md` - Estrutura de projeto
+- `.morph/context/azure.md` - Recursos e custos
 
 ---
 

package/framework/commands/morph-archive.md

@@ -1,11 +1,11 @@
 # Archive MORPH Feature
 
-Arquive uma feature concluída, movendo-a de `project/outputs/` para `project/archive/`.
+Arquive uma feature concluída, movendo-a de `features/` para `archive/`.
 
 ## Pré-requisitos
 
 Verifique antes de arquivar:
-- [ ] Feature existe em `.morph/project/outputs/{feature}/`
+- [ ] Feature existe em `.morph/features/{feature}/`
 - [ ] Todas as tasks estão completas
 - [ ] `recap.md` está preenchido
 - [ ] Código está em produção (ou staging)
@@ -13,23 +13,23 @@ Verifique antes de arquivar:
 ## Workflow
 
 1. **Valide a conclusão**:
-   - Leia `.morph/project/outputs/{feature}/tasks.json`
+   - Leia `.morph/features/{feature}/3-tasks/tasks.md`
    - Verifique que todas tasks estão completadas
    - Confirme com o usuário se pode arquivar
 
 2. **Complete o recap**:
-   - Atualize `.morph/project/outputs/{feature}/recap.md`
+   - Atualize `.morph/features/{feature}/4-implement/recap.md`
    - Preencha métricas finais
    - Documente lições aprendidas
 
 3. **Extraia specs**:
    - Se a feature define comportamento permanente
-   - Copie spec relevante para `.morph/project/specs/`
+   - Copie spec relevante para `.morph/specs/`
    - Isso vira a "verdade atual" do sistema
 
 4. **Mova para archive**:
    ```
-   .morph/project/outputs/{feature}/  →  .morph/project/archive/{feature}/
+   .morph/features/{feature}/  →  .morph/archive/{feature}/
    ```
 
 5. **Atualize métricas do projeto**:
@@ -62,7 +62,7 @@ Apresente resumo do arquivamento:
 ╠════════════════════════════════════════════╣
 ║ ARCHIVED TO                                ║
 ╠════════════════════════════════════════════╣
-║ .morph/project/archive/{feature}/          ║
+║ .morph/archive/{feature}/                  ║
 ╚════════════════════════════════════════════╝
 ```
 
@@ -70,7 +70,7 @@ Apresente resumo do arquivamento:
 
 Se houver specs extraídas:
 ```
-Specs extracted to .morph/project/specs/:
+Specs extracted to .morph/specs/:
 - {domain}/spec.md - {description}
 ```
 

package/framework/commands/morph-infra.md

@@ -41,7 +41,7 @@ Quando o usuário solicitar `/morph-infra init`:
        └── app-insights.bicep
    ```
 
-2. Copiar templates de `.morph/templates/infrastructure/...`
+2. Copiar templates de `.morph/framework/templates/infrastructure/...`
 
 3. Substituir placeholders:
    - `{{APP_NAME}}` → nome do projeto

package/framework/commands/morph-proposal.md

@@ -34,10 +34,10 @@ npx morph-spec state get {feature-name}
 
 4. **Crie a estrutura:**
    ```
-   .morph/project/outputs/{feature-name}/
-   ├── proposal.md
-   ├── spec.md (iniciar)
-   └── tasks.json (iniciar)
+   .morph/features/{feature-name}/
+   ├── 0-proposal/proposal.md
+   ├── 1-design/spec.md (iniciar)
+   └── 3-tasks/tasks.md (iniciar)
    ```
 
 5. **Preencha `proposal.md`** baseado em `framework/templates/proposal.md`
@@ -59,7 +59,7 @@ Apresente: resumo da proposta, agentes ativados, custo estimado, 3 itens de paus
 
 ## 3. Após Aprovação do Proposal → FASE 1: SETUP (auto, sem pausa)
 
-**Ler:** `.claude/skills/workflows/phase-setup.md` para instruções detalhadas.
+**Ler:** `.claude/skills/level-1-workflows/phase-setup.md` para instruções detalhadas.
 
 Resumo: carregar contexto do projeto, confirmar stack, listar agentes ativos, atualizar state.
 
@@ -70,14 +70,14 @@ Resumo: carregar contexto do projeto, confirmar stack, listar agentes ativos, at
 ## 4. FASE 1.5: UI/UX (condicional)
 
 Verificar se `uiux-designer` está nos `activeAgents`:
-- **Se SIM:** Ler `.claude/skills/workflows/phase-uiux.md` e executar. **PAUSA OBRIGATORIA** após gerar deliverables UI.
+- **Se SIM:** Ler `.claude/skills/level-1-workflows/phase-uiux.md` e executar. **PAUSA OBRIGATORIA** após gerar deliverables UI.
 - **Se NÃO:** Pular para FASE 2.
 
 ---
 
 ## 5. FASE 2: DESIGN
 
-**Ler:** `.claude/skills/workflows/phase-design.md` para instruções detalhadas.
+**Ler:** `.claude/skills/level-1-workflows/phase-design.md` para instruções detalhadas.
 
 Resumo: gerar spec.md, contracts.cs, decisions.md com ADRs, estimar custos.
 
@@ -89,7 +89,7 @@ Apresente: spec, contracts, decisions, custos. 3 itens de pausa (aprovar, ajusta
 
 ## 6. Após Aprovação do Design → FASE 3: CLARIFY (interativo)
 
-**Ler:** `.claude/skills/workflows/phase-clarify.md` para instruções detalhadas.
+**Ler:** `.claude/skills/level-1-workflows/phase-clarify.md` para instruções detalhadas.
 
 Resumo: identificar ambiguidades, gerar 3-7 perguntas, aguardar respostas, atualizar spec com clarificações e edge cases.
 
@@ -99,7 +99,7 @@ Resumo: identificar ambiguidades, gerar 3-7 perguntas, aguardar respostas, atual
 
 ## 7. FASE 4: TASKS
 
-**Ler:** `.claude/skills/workflows/phase-tasks.md` para instruções detalhadas.
+**Ler:** `.claude/skills/level-1-workflows/phase-tasks.md` para instruções detalhadas.
 
 Resumo: quebrar spec em tasks T001-TXXX, definir dependências, checkpoints, estimativas.
 

package/framework/commands/morph-status.md

@@ -22,7 +22,7 @@ Este comando automaticamente mostra:
 ### 1. Configuração MORPH
 - [ ] `.morph/project.md` existe e está preenchido
 - [ ] `.morph/config/config.json` configurado
-- [ ] `.morph/standards/` presentes
+- [ ] `.morph/framework/standards/` presentes
 
 ### 2. Detalhes de Feature Específica
 
@@ -34,14 +34,14 @@ npx morph-spec state get {feature-name}
 
 ### 3. Features Arquivadas
 
-Verifique `.morph/project/archive/` manualmente se necessário:
+Verifique `.morph/archive/` manualmente se necessário:
 - Quantas features concluídas
 - Tempo total gasto
 - Custo acumulado
 
 ### 4. Specs Ativas
 
-Verifique `.morph/project/specs/` para specs consolidadas.
+Verifique `.morph/specs/` para specs consolidadas.
 
 ## Output
 

package/framework/commands/morph-troubleshoot.md

@@ -37,7 +37,7 @@ npx morph-spec troubleshoot {keywords}
 
 Se o índice retornar poucos resultados, o CLI automaticamente busca nos arquivos:
 - `framework/standards/*.md`
-- `.morph/standards/*.md`
+- `.morph/framework/standards/*.md`
 
 ### Nível 3: Web Search (Se necessário)