@polymorphism-tech/morph-spec 4.8.18 → 4.9.0

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

@@ -1,11 +1,11 @@
 ---
-name: morph-init
+name: morph:init
 description: >
   LLM-powered project initialization. Installs morph-spec infrastructure if
   needed, auto-installs required plugins (superpowers, context7), analyzes any
   project structure intelligently, generates rich context/README.md and
   config.json, and configures MCPs. Use once per project after installing
-  @polymorphism-tech/morph-spec. Re-run with /morph-init refresh to update
+  @polymorphism-tech/morph-spec. Re-run with /morph:init refresh to update
   context as the project evolves.
 argument-hint: "[refresh]"
 user-invocable: true
@@ -15,7 +15,7 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 # morph-init — LLM-Powered Project Initialization
 
 > Run once after `npm install @polymorphism-tech/morph-spec`.
-> Re-run as `/morph-init refresh` when your project evolves.
+> Re-run as `/morph:init refresh` when your project evolves.
 
 ---
 
@@ -55,7 +55,7 @@ claude plugin install superpowers@claude-plugins-official
 claude plugin install context7@claude-plugins-official
 ```
 
-**If the command succeeds:** `✓ {plugin} installed. Restart Claude Code after /morph-init completes.`
+**If the command succeeds:** `✓ {plugin} installed. Restart Claude Code after /morph:init completes.`
 
 **If the command fails:** Show this and **STOP** — do not continue:
 
@@ -63,7 +63,7 @@ claude plugin install context7@claude-plugins-official
 Plugin {plugin} could not be installed automatically.
 Run manually and restart Claude Code:
   claude plugin install {plugin}
-Then re-run /morph-init.
+Then re-run /morph:init.
 ```
 
 Both `superpowers` and `context7` are required. Do not continue if either is missing.

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

@@ -1,5 +1,5 @@
 ---
-name: morph-replicate
+name: morph:replicate
 description: Simplified workflow for converting HTML prototypes into functional Blazor components, extracting design patterns and mapping HTML elements to Fluent UI/MudBlazor equivalents. Use when an approved HTML prototype exists and needs conversion to Blazor without a full MORPH-SPEC spec pipeline.
 user-invocable: true
 argument-hint: "[feature-name] [prototype-path]"
@@ -14,12 +14,12 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ## Comando
 
 ```bash
-/morph-replicate {feature-name} {prototype-path}
+/morph:replicate {feature-name} {prototype-path}
 ```
 
 **Exemplo:**
 ```bash
-/morph-replicate ui-redesign prototipo/
+/morph:replicate ui-redesign prototipo/
 ```
 
 ---
@@ -154,7 +154,7 @@ Este workflow gera apenas:
 ## Exemplo de Execucao
 
 ```markdown
-/morph-replicate checkout-redesign prototipo/checkout/
+/morph:replicate checkout-redesign prototipo/checkout/
 
 📁 Analisando prototipo em prototipo/checkout/...
 

package/framework/skills/level-0-meta/morph-replicate/references/blazor-html-mapping.md

@@ -1,7 +1,7 @@
 # HTML → Blazor Component Mapping Reference
 
 > Reference for converting HTML prototype elements to Fluent UI / MudBlazor equivalents.
-> Used during FASE 1 of the `/morph-replicate` workflow.
+> Used during FASE 1 of the `/morph:replicate` workflow.
 
 ## Common Component Mappings
 

package/framework/skills/level-0-meta/post-implementation/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: post-implementation
+name: morph:post-implementation
 description: Orquestra o fluxo completo pós-implementação: detecção de stack,
   scans automáticos (C#/Next.js), testes, validate-feature, smoke test via
   Playwright (obrigatório se dev server ativo), checklist de code review por
@@ -49,20 +49,20 @@ Execute os scans automáticos conforme o stack detectado.
 ### Se DOTNET ou FULLSTACK:
 
 ```bash
-node .claude/skills/code-review/scripts/scan-csharp.mjs --diff
+node .claude/skills/morph:code-review/scripts/scan-csharp.mjs --diff
 ```
 
 ### Se NEXTJS ou FULLSTACK:
 
 ```bash
-node .claude/skills/code-review-nextjs/scripts/scan-nextjs.mjs --diff
+node .claude/skills/morph:code-review-nextjs/scripts/scan-nextjs.mjs --diff
 ```
 
 **🚫 BLOCK se qualquer finding CRITICAL encontrado.**
 
 Corrija todos os CRITICALs antes de continuar. Para revisar a lista completa de checks:
-- .NET: `/code-review`
-- Next.js: `/code-review-nextjs`
+- .NET: `/morph:code-review`
+- Next.js: `/morph:code-review-nextjs`
 
 ---
 
@@ -181,7 +181,7 @@ Não é possível prosseguir para criação de PR sem smoke test ou confirmaçã
 
 ## Step 6 — Code Review Checklist (CRITICAL + HIGH)
 
-> Antes de revisar, leia: `.claude/skills/code-review/references/review-guidelines.md` — aplique confidence ≥ 75, ignore violações pré-existentes, inclua file:line em cada finding.
+> Antes de revisar, leia: `.claude/skills/morph:code-review/references/review-guidelines.md` — aplique confidence ≥ 75, ignore violações pré-existentes, inclua file:line em cada finding.
 
 Revise os itens mais importantes por stack. Para review completo, use os skills dedicados.
 
@@ -191,14 +191,14 @@ Dispatch dois subagents em paralelo (Task tool):
 
 **Subagent 1 — Backend Review:**
 > Revisor .NET focado. Escopo: APENAS arquivos .cs alterados (git diff main...HEAD).
-> Run: `node .claude/skills/code-review/scripts/scan-csharp.mjs --diff`
+> Run: `node .claude/skills/morph:code-review/scripts/scan-csharp.mjs --diff`
 > Depois revisar manualmente itens CRITICAL+HIGH do checklist .NET.
 > Aplicar review-guidelines.md: confidence ≥ 75, skip pré-existentes.
 > Output: findings com file:line, ou "✅ Sem CRITICAL/HIGH em backend alterado."
 
 **Subagent 2 — Frontend Review:**
 > Revisor Next.js focado. Escopo: APENAS arquivos .tsx/.ts alterados (git diff main...HEAD).
-> Run: `node .claude/skills/code-review-nextjs/scripts/scan-nextjs.mjs --diff`
+> Run: `node .claude/skills/morph:code-review-nextjs/scripts/scan-nextjs.mjs --diff`
 > Depois revisar manualmente itens CRITICAL+HIGH do checklist Next.js.
 > Aplicar review-guidelines.md: confidence ≥ 75, skip pré-existentes.
 > Output: findings com file:line, ou "✅ Sem CRITICAL/HIGH em frontend alterado."
@@ -222,14 +222,14 @@ Aguardar ambos. **🚫 BLOCK se algum retornar CRITICAL não resolvido.**
 [ ] DTOs com nomes descritivos + tipos corretos
 ```
 
-> Para lista completa: `/code-review`
+> Para lista completa: `/morph:code-review`
 
 ### Se NEXTJS:
 
 **Itens CRITICAL e HIGH — Next.js:**
 
 ```
-[ ] node .claude/skills/code-review-nextjs/scripts/scan-nextjs.mjs --diff → 0 CRITICAL
+[ ] node .claude/skills/morph:code-review-nextjs/scripts/scan-nextjs.mjs --diff → 0 CRITICAL
 [ ] File names em kebab-case (user-card.tsx, não UserCard.tsx)
 [ ] 'use client' apenas em componentes com hooks/event handlers
 [ ] Sem useEffect para data fetching → Server Component ou useQuery
@@ -241,7 +241,7 @@ Aguardar ambos. **🚫 BLOCK se algum retornar CRITICAL não resolvido.**
 [ ] Sem any type annotation
 ```
 
-> Para lista completa: `/code-review-nextjs`
+> Para lista completa: `/morph:code-review-nextjs`
 
 **🚫 BLOCK se qualquer item CRITICAL não estiver resolvido.**
 
@@ -259,7 +259,52 @@ npx morph-spec generate recap $ARGUMENTS
 
 ---
 
-## Step 8 — PR Suggestion
+## Step 8 — Finish Worktree
+
+Implementation is complete. If the feature was developed in a morph worktree, finalize it now.
+
+**Check if a worktree exists:**
+```bash
+git worktree list | grep morph/
+```
+
+**If a `morph/{feature}` worktree exists:**
+
+Invoke the finishing-a-development-branch skill:
+```
+Skill(superpowers:finishing-a-development-branch)
+```
+
+This skill will:
+1. Verify tests pass
+2. Present 4 options:
+   - **Merge locally** → merge into base branch + delete worktree
+   - **Push and create PR** → push branch + create GitHub PR (keeps worktree)
+   - **Keep as-is** → no action (worktree preserved for later)
+   - **Discard** → delete branch + worktree (requires typed confirmation)
+3. Clean up worktree for options 1 and 4
+
+**If NOT in a worktree** (legacy mode): skip this step and proceed to Step 9.
+
+> **Note:** If the `superpowers` plugin is not installed, create the PR manually:
+> `gh pr create --title "feat({feature}): <description>" --body "..."`
+
+---
+
+## Step 9 — Pre-PR Compliance Checklist
+
+Antes de criar o PR, invoque o checklist de compliance:
+
+```
+Skill(morph:checklist)
+```
+
+Este skill verifica: segurança, SEO, performance, acessibilidade e conformidade LGPD.
+**🚫 BLOCK se qualquer item CRITICAL não estiver resolvido.**
+
+---
+
+## Step 10 — PR Suggestion
 
 Quando todos os steps passarem, sugira o PR:
 
@@ -307,6 +352,8 @@ EOF
 | Step 5 | Dev server ativo + smoke test com falha |
 | Step 5 | Dev server não detectado sem confirmação explícita do usuário |
 | Step 6 | Qualquer item CRITICAL não resolvido no checklist manual |
+| Step 8 | Tests failing in worktree before merge/PR |
+| Step 9 | Item CRITICAL no `morph:checklist` não resolvido |
 
 **Todos os BLOCKs devem ser resolvidos antes de criar o PR.**
 

package/framework/skills/level-0-meta/simulation-checklist/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: simulation-checklist
+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

package/framework/skills/level-0-meta/terminal-title/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: terminal-title
+name: morph:terminal-title
 description: Manually set the terminal window title for the current task. Use when you need to override the automatic title set by the hook, or to set a specific descriptive title for the current work context.
 argument-hint: "[title]"
 user-invocable: true

package/framework/skills/level-0-meta/tool-usage-guide/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: tool-usage-guide
+name: morph:tool-usage-guide
 description: Decision flowchart and per-phase reference for selecting the right Claude Code tool (Read, Grep, Glob, Bash, Task) or MCP tool in MORPH-SPEC workflows. Use when unsure which tool to use for a given action, when choosing between native tools and MCPs, or when deciding whether to use a subagent vs direct tools.
 user-invocable: true
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep

package/framework/skills/level-0-meta/tool-usage-guide/references/tools-per-phase.md

@@ -17,7 +17,7 @@
 | Detect project stack | **Read** `.morph/framework/agents.json` → match keywords → **Bash** `npx morph-spec state add-agent` | agents.json is the source of truth |
 | Research external requirement | **WebSearch** | Current information needed |
 | Render proposal template | **Bash** `npx morph-spec template render docs/proposal ...` | CLI command |
-| Update state | **Bash** `npx morph-spec state mark-output ...` | CLI command |
+| Update state | **Bash** `npx morph-spec state mark-output {feature} proposal` | CLI command |
 
 **MCPs used:** None typically. GitHub MCP if feature comes from an issue.
 
@@ -70,7 +70,7 @@
 | Search for design references | **WebSearch** + **WebFetch** | External inspiration |
 | Render UI templates | **Bash** `npx morph-spec template render docs/ui-mockups ...` | CLI command |
 | Generate design system from CSS | **Bash** `npx morph-spec generate design-system --scan` | CLI command |
-| Update state | **Bash** `npx morph-spec state mark-output ...` | 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).
 
@@ -104,7 +104,7 @@
 | Render spec template | **Bash** `npx morph-spec template render docs/spec ...` | CLI command |
 | Render decisions template | **Bash** `npx morph-spec template render docs/decisions ...` | CLI command |
 | Create schema-analysis.md | **Write** to output directory | Document findings |
-| Update state | **Bash** `npx morph-spec state mark-output ...` | CLI command |
+| Update state | **Bash** `npx morph-spec state mark-output {feature} schemaAnalysis && npx morph-spec state mark-output {feature} spec && npx morph-spec state mark-output {feature} contracts && npx morph-spec state mark-output {feature} decisions` | CLI command |
 
 **MCPs used:** Supabase (schema analysis), Context7 (library research), GitHub (code search).
 
@@ -133,7 +133,7 @@
 | Research edge case behavior | **WebSearch** | External knowledge for edge cases |
 | Update spec with clarifications | **Edit** spec.md | Preserve existing content, add sections |
 | Create clarifications.md | **Bash** `npx morph-spec template render docs/clarifications ...` | Use template |
-| Update state | **Bash** `npx morph-spec state mark-output ... clarifications` | CLI command |
+| Update state | **Bash** `npx morph-spec state mark-output {feature} clarifications` | CLI command |
 
 **MCPs used:** Context7 (validate feasibility), GitHub (known issues).
 
@@ -159,6 +159,7 @@
 | Create GitHub issues from tasks | **GitHub MCP** `create_issue()` | Sync tasks to project management |
 | **Fallback:** Create issues via CLI | **Bash** `gh issue create ...` | When no GitHub MCP |
 | Render tasks template | **Bash** `npx morph-spec template render docs/tasks ...` | CLI command |
+| Mark tasks output | **Bash** `npx morph-spec state mark-output {feature} tasks` | CLI command |
 | Update state with task count | **Bash** `npx morph-spec state set ... tasks.total N` | CLI command |
 
 **MCPs used:** Context7 (complexity estimation), GitHub (issue creation).
@@ -195,7 +196,7 @@
 | Smoke test feature no browser | **Playwright MCP** `browser_navigate()` + `browser_snapshot()` | Manual testing |
 | Verificar erros de console | **Playwright MCP** `browser_console_messages()` | Browser DevTools |
 | Screenshot para recap.md | **Playwright MCP** `browser_take_screenshot()` | Manual screenshot |
-| Update state | **Bash** `npx morph-spec state set ...` | CLI command |
+| Mark recap output | **Bash** `npx morph-spec state mark-output {feature} recap` | CLI command |
 
 **MCPs used:** Supabase (migrations, RLS), Context7 (API lookup), GitHub (PRs), Playwright (smoke test, verification).
 

package/framework/skills/level-0-meta/verification-before-completion/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: verification-before-completion
+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?]"