@polymorphism-tech/morph-spec 4.7.2 → 4.8.4

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

@@ -0,0 +1,216 @@
+---
+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
+  context as the project evolves.
+argument-hint: "[refresh]"
+user-invocable: true
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+# morph-init — LLM-Powered Project Initialization
+
+> Run once after `npm install -g @polymorphism-tech/morph-spec`.
+> Re-run as `/morph-init refresh` when your project evolves.
+
+---
+
+## Step 0 — Required Plugins
+
+Check for required Claude Code plugins: **superpowers** and **context7**.
+
+Read `~/.claude/plugins/installed_plugins.json` and check for:
+- `superpowers@claude-plugins-official`
+- `context7@claude-plugins-official`
+
+For each missing plugin, run:
+
+```bash
+morph-spec install-plugin superpowers
+morph-spec install-plugin context7
+```
+
+**If the command succeeds:** `✓ {plugin} installed. Restart Claude Code after /morph-init completes.`
+
+**If the command fails:** Show this and **STOP** — do not continue:
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  Plugin {plugin} requires manual installation:              │
+│                                                             │
+│  1. Claude Code → Settings (Cmd/Ctrl+,) → Extensions        │
+│  2. Browse → search "{plugin}" → Install                    │
+│  3. Restart Claude Code                                     │
+│  4. Re-run /morph-init                                      │
+└─────────────────────────────────────────────────────────────┘
+```
+
+Both `superpowers` and `context7` are required. Do not continue if either is missing.
+
+---
+
+## Step 1 — Infrastructure
+
+Check if `.morph/` exists in the current directory.
+
+**If MISSING:**
+```bash
+morph-spec setup-infra
+```
+Output confirms: `✓ MORPH-SPEC infrastructure installed.`
+
+**If EXISTS and argument is `refresh`:** Continue — will overwrite context and config.
+
+**If EXISTS and no argument:**
+Ask: *"MORPH already initialized. Refresh context and config? (y/n)"*
+If `n` → STOP.
+
+---
+
+## Step 2 — Analyze Project
+
+Gather evidence to build a stack map. Run these in parallel:
+
+| Tool | Pattern | Signal |
+|------|---------|--------|
+| `Glob` | `**/package.json` | Detect next, supabase, clerk, stripe in deps |
+| `Glob` | `**/*.csproj` | .NET projects at any depth |
+| `Glob` | `**/next.config.{js,ts,mjs}` | Next.js in any subdirectory |
+| `Glob` | `**/components.json` | shadcn/ui |
+| `Glob` | `**/docker-compose*.yml` | Container services |
+| `Glob` | `database/migrations/**` | Supabase local dev |
+| `Glob` | `supabase/**` | Supabase project config |
+| `Glob` | `**/*.razor` | Blazor |
+| `Read` | `.env.example` | Env vars reveal integrations |
+| `Read` | `README.md` | Existing project description |
+| `Grep` | `@supabase/supabase-js` | Supabase dep in any package.json |
+| `Grep` | `clerk\|auth0\|nextauth` | Auth provider |
+| `Grep` | `stripe\|asaas` | Payment provider |
+
+Read each found `package.json` for dependency names. Build an **evidence map**:
+
+```
+stack:         [nextjs, dotnet, ...]
+integrations:  [supabase, docker, clerk, ...]
+uiLibrary:     shadcn | fluent-ui | mudblazor | null
+monorepo:      true | false
+frontendPath:  src/frontend (if monorepo)
+backendPath:   src/backend (if monorepo)
+```
+
+---
+
+## Step 3 — Ask Targeted Questions
+
+**Rule: only ask what cannot be inferred with ≥90% confidence from files.**
+
+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 |
+
+Do **not** ask about technology already confirmed by file evidence.
+
+---
+
+## Step 4 — Generate `context/README.md`
+
+Write `.morph/context/README.md`:
+
+```markdown
+# [ProjectName] — Project Context
+
+## Overview
+[Answer from question 1]
+
+## Tech Stack
+| Layer      | Technology | Location |
+|------------|-----------|----------|
+[One row per detected layer — frontend, backend, database, UI library, auth, payments]
+
+## Architecture
+[monorepo / single-stack / etc — describe layers and responsibilities]
+
+## Key Integrations
+[Per integration: service → purpose → detected via: evidence file/dep]
+
+## Agent Notes
+[Patterns from eslint/tsconfig/.editorconfig, important paths,
+ project-specific conventions for MORPH agents]
+```
+
+---
+
+## Step 5 — Update `config.json`
+
+Read `.morph/config/config.json` and merge into `project`:
+
+```json
+{
+  "framework": "global",
+  "frameworkVersion": "[current version]",
+  "project": {
+    "name": "[ProjectName]",
+    "description": "[answer from question 1]",
+    "stack": "[stacks joined with +, e.g. nextjs+dotnet]",
+    "architecture": "[monorepo | single-stack | detected pattern]",
+    "uiLibrary": "[detected or null]",
+    "integrations": ["supabase", "docker", "clerk"],
+    "frontendPath": "[path if monorepo, else omit]",
+    "backendPath": "[path if monorepo, else omit]"
+  }
+}
+```
+
+---
+
+## Step 6 — Configure MCPs
+
+For each detected integration with an available MCP:
+
+**Supabase detected:**
+> *"Configure Supabase MCP now? I'll need `SUPABASE_URL` and `SERVICE_ROLE_KEY`."*
+- YES → collect credentials → add to `.claude/settings.local.json` under `mcpServers`
+- NO → show snippet + `morph-spec mcp setup supabase`
+
+**GitHub:**
+> *"Configure GitHub MCP? I'll need a `GITHUB_PERSONAL_ACCESS_TOKEN`."*
+- YES/NO → same pattern
+
+Only offer Figma, Docker, Azure if explicitly detected in `.env.example`.
+
+---
+
+## Step 7 — 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.
+
+```
+✓ Plugins:       superpowers ✓   context7 ✓
+✓ Infrastructure: .morph/ structure, hooks, agents, rules, skills
+✓ Agents:        [N] total ([T1] orchestrators, [T2] domain leaders, [S] specialists)
+✓ context/README.md generated
+✓ config.json updated
+  Stack: [stack]  |  Architecture: [architecture]
+  Integrations:   [list]
+✓ MCPs: [configured list]
+
+[If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS = "1":]
+✓ Agent Teams: enabled
+
+[If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is NOT set:]
+⚠ Agent Teams not enabled. Multi-agent workflows require:
+  ~/.claude/settings.local.json → {"env": {"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"}}
+
+[If any plugin was newly installed:]
+○ Restart Claude Code to activate newly installed plugins.
+
+Next: /morph-proposal [feature-name]
+```

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

@@ -77,7 +77,7 @@ Gerar lista de telas para implementar na ordem correta:
 ### T001: Setup Design System
 - Criar/atualizar wwwroot/css/design-system.css
 - Adicionar todas as classes CSS listadas
-- Validar com `morph-spec validate-css`
+- Validar com `morph-spec validate`
 
 ### T002: {Nome da Tela 1}
 - Ler: {prototype-path}/{tela1}.html
@@ -92,7 +92,7 @@ Gerar lista de telas para implementar na ordem correta:
 
 ### TXXX: Validacao Final
 - Build completo
-- `morph-spec validate-css`
+- `morph-spec validate`
 - Testar responsividade
 ```
 
@@ -130,7 +130,7 @@ Para cada tela, seguir este fluxo:
 
 6. **Validar CSS**
    ```bash
-   morph-spec validate-css src/MyApp.Web
+   morph-spec validate src/MyApp.Web
    ```
 
 ---
@@ -217,4 +217,4 @@ Mapeamento HTML → Blazor:
 
 ---
 
-*MORPH-SPEC v2.2.0 by Polymorphism Tech*
+*MORPH-SPEC by Polymorphism Tech*

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

@@ -59,7 +59,7 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 | Read project context | **Read** `.morph/context/README.md` | Single known file |
 | Read config | **Read** `.morph/config.json` | Single known file |
 | Find existing features | **Glob** `.morph/features/*/0-proposal/proposal.md` | Pattern search |
-| Detect project stack | **Bash** `npx morph-spec detect-agents --json "..."` | CLI command |
+| 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 |
@@ -80,7 +80,7 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 | Action | Tool | Why |
 |--------|------|-----|
 | Verify feature state | **Bash** `npx morph-spec state get {feature}` | CLI command |
-| Detect agents + standards | **Bash** `npx morph-spec detect-agents --json "..."` | CLI command, returns JSON with standards |
+| Detect agents + standards | **Read** `.morph/framework/agents.json` → match keywords → **Bash** `npx morph-spec state add-agent {f} {id}` per match | No CLI command — read agents.json directly |
 | Read project context | **Read** `.morph/context/README.md` | Single file |
 | Read config | **Read** `.morph/config.json` | Single file |
 | Scan project structure | **Glob** `src/**/*.{ts,tsx,cs}` | Understand codebase layout |
@@ -90,9 +90,9 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 **MCPs used:** GitHub (optional — for repo metadata).
 
 **Anti-patterns:**
-- ❌ Task agent to detect project stack (detect-agents CLI does this)
+- ❌ Calling `detect-agents` CLI (it doesn't exist — read `.morph/framework/agents.json` directly)
+- ❌ Task agent to detect project stack (read agents.json and match keywords inline)
 - ❌ WebSearch for project info (it's local, use Read/Glob)
-- ❌ Manual parsing of agents.json (detect-agents handles it)
 
 ---
 

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

@@ -7,7 +7,7 @@ description: Phase-specific verification checklists and morph-spec validation co
 
 > Never claim work is complete without running verification. Evidence before assertions.
 >
-> **Script:** Run `node scripts/check-phase-outputs.mjs <feature> [phase]` to check required output files exist.
+> **Script:** Run `node .claude/skills/verification-before-completion/scripts/check-phase-outputs.mjs <feature> [phase]` to check required output files exist.
 
 ## When to Use