@polymorphism-tech/morph-spec 4.5.0 → 4.7.0

package/CLAUDE.md

@@ -1,56 +1,77 @@
-# MORPH-SPEC - Claude Code Instructions
-
-> by Polymorphism Tech
-
-Spec-driven development system for multi-stack projects (.NET/Blazor/Next.js/Azure).
-
----
-
-## CRITICAL RULES
-
-### NEVER:
-- Skip to code without a specification
-- Implement without design approval
-- Ignore standards in `.morph/framework/standards/`
-- Create infrastructure manually
-- Generate code without defined contracts
-
-### ALWAYS:
-- Follow the 5 mandatory phases
-- Generate outputs in `.morph/features/{feature}/`
-- Document decisions in `decisions.md`
-- Checkpoint every 3 implemented tasks
-- Use Infrastructure as Code
-
----
-
-## ENTRY POINTS
-
-| Command | Purpose |
-|---------|---------|
-| `/morph-proposal {feature}` | Full spec pipeline (phases 1–4, pauses for approval) |
-| `/morph-apply {feature}` | Implement feature (phase 5) |
-| `/morph-status` | Feature dashboard |
-
-> All agents, workflows, phases, and templates are described in the skills loaded at session start.
-
----
-
-## PROJECT CONTEXT
-
-@.morph/context/README.md
-
----
-
-## KEY PATHS
-
-| Path | Contents |
-|------|---------|
-| `.morph/config/config.json` | Project configuration |
-| `.morph/framework/agents.json` | 37 agent definitions |
-| `.morph/framework/standards/` | Coding and architecture standards |
-| `.morph/framework/skills/` | Phase workflows and domain specialists |
-
----
-
-*MORPH-SPEC v4.4.0 by Polymorphism Tech*
+# MORPH-SPEC Runtime Instructions
+
+> by Polymorphism Tech — Spec-driven development for .NET/Blazor/Next.js/Azure
+
+---
+
+## Project Context
+
+@.morph/context/README.md
+
+---
+
+## Critical Rules
+
+**NEVER:**
+- Skip to code without a specification
+- Implement without design approval
+- Ignore standards in `.morph/framework/standards/`
+- Create infrastructure manually
+- Generate code without defined contracts
+
+**ALWAYS:**
+- Follow the mandatory phases
+- Generate outputs in `.morph/features/{feature}/`
+- Document decisions in `decisions.md`
+- Checkpoint every 3 implemented tasks
+- Use Infrastructure as Code
+
+---
+
+## Quick Reference
+
+| Command | Purpose |
+|---------|---------|
+| `/morph-proposal {feature}` | Full spec pipeline (phases 1–4, pauses for approval) |
+| `/morph-apply {feature}` | Implement feature (phase 5) |
+| `/morph-status` | Feature status dashboard |
+| `/morph-preflight` | Pre-implementation validation |
+
+---
+
+## State & Outputs
+
+| Path | Notes |
+|------|-------|
+| `.morph/state.json` | **READ-ONLY** — use `morph-spec` CLI to update |
+| `.morph/features/{feature}/{phase}/` | Feature outputs organized by phase |
+| `.morph/framework/` | **READ-ONLY** — framework files managed by morph-spec |
+| `.morph/config/config.json` | Project configuration (editable) |
+
+---
+
+## Phase Sequence
+
+```
+proposal → setup → [uiux] → design → clarify → tasks → implement → [sync]
+```
+
+Use `morph-spec state show {feature}` to see current phase and pending approval gates.
+
+---
+
+## Agents
+
+Tier-1 and tier-2 MORPH agents are available as native subagents in `.claude/agents/`.
+They can be invoked directly by Claude Code during multi-agent workflows.
+
+---
+
+## Context Window Tip
+
+When using 3+ MCPs, add `"experimental": { "mcpCliMode": true }` to `.claude/settings.json`.
+MCP tools load on-demand instead of all at startup — keeps context clean for actual work.
+
+---
+
+*MORPH-SPEC v4.5.0 by Polymorphism Tech*