start-vibing 2.0.11 → 2.0.13

package/template/CLAUDE.md

@@ -1,117 +1,117 @@
-# Development Rules
-
-> **THESE RULES ARE MANDATORY. NO EXCEPTIONS.**
-
----
-
-## Workflow (STRICT FLOW)
-
-```
-0. INIT TASK      →  Run commit-manager to REGISTER task start
-1. TODO LIST      →  ALWAYS create detailed todo list from prompt
-2. RESEARCH       →  Run research agent for NEW features (MANDATORY)
-3. AUDIT          →  Check docs from last audit OR run fresh audit
-4. CREATE BRANCH  →  feature/ | fix/ | refactor/ | test/
-5. IMPLEMENT      →  Follow project rules + analyzer approval
-6. DOCUMENT       →  Document ALL modified files (MANDATORY)
-7. QUALITY GATES  →  Run typecheck && lint && test (Husky enforced)
-8. FINISH         →  commit-manager creates PR with task summary
-```
-
-> **CRITICAL:** Research agent is MANDATORY for any new feature or complex bug fix.
-> **CRITICAL:** All documentation must reference commit hashes for audit trail.
-> **CRITICAL:** Stop hook BLOCKS task completion if files not documented.
-> **FALLBACK:** If Task tool fails to invoke an agent, READ the agent file directly from `.claude/agents/[agent-name].md` and follow its instructions manually.
-
----
-
-## MCP Servers (MANDATORY)
-
-Configure these in `.mcp.json` at project root:
-
-| Server                | Purpose                            | When to Use                          |
-| --------------------- | ---------------------------------- | ------------------------------------ |
-| `context7`            | Up-to-date library documentation   | Before implementing with ANY library |
-| `sequential-thinking` | Complex problem-solving            | Multi-step tasks, planning           |
-| `memory`              | Persistent knowledge graph         | Store/recall project patterns        |
-| `playwright`          | Browser automation and E2E testing | UI testing, page verification        |
-| `nextjs-devtools`     | Next.js specific development tools | Next.js projects only                |
-| `mongodb`             | MongoDB database operations        | Database queries, schema inspection  |
-
-### Usage Rules
-
-- **ALWAYS** use `context7` before implementing features with external libraries
-- **ALWAYS** use `playwright` for E2E tests instead of manual browser testing
-- **ALWAYS** check `memory` for existing patterns before creating new ones
-- **NEVER** hardcode library APIs - query `context7` for current docs
-
----
-
-## Agent System
-
-This project uses 11 specialized AI agents:
-
-| Agent            | Purpose                       | Priority |
-| ---------------- | ----------------------------- | -------- |
-| orchestrator     | Coordinates entire workflow   | 1        |
-| analyzer         | Analyzes change impact        | 2        |
-| research         | Researches best practices     | 3        |
-| documenter       | Creates/updates documentation | 3        |
-| tester           | Creates unit and E2E tests    | 4        |
-| security-auditor | Audits security (VETO POWER)  | 5        |
-| ui-ux-reviewer   | Reviews UI/UX patterns        | 6        |
-| quality-checker  | Runs quality gates            | 7        |
-| final-validator  | Final validation (VETO POWER) | 8        |
-| domain-updater   | Updates domain knowledge      | 9        |
-| commit-manager   | Manages commits (FINAL step)  | 10       |
-
----
-
-## Stop Hook Enforcement
-
-The Stop hook runs when Claude is about to finish and BLOCKS if:
-
-| Violation                          | Action Required                 |
-| ---------------------------------- | ------------------------------- |
-| On main branch with source changes | Create feature/fix branch first |
-| Source files not documented        | Run documenter agent            |
-| Documenter not executed            | Invoke documenter via Task tool |
-
----
-
-## Configuration
-
-Edit these files in `.claude/config/` for your project:
-
-| File                  | Purpose                    |
-| --------------------- | -------------------------- |
-| `project-config.json` | Stack, structure, commands |
-| `quality-gates.json`  | Quality check commands     |
-| `testing-config.json` | Test framework config      |
-| `security-rules.json` | Security audit rules       |
-| `domain-mapping.json` | File patterns to domains   |
-
----
-
-## Critical Rules
-
-1. **ALWAYS use MCP servers** - Context7 for docs, Playwright for E2E
-2. **ALWAYS start with todo list** - Track progress with TodoWrite tool
-3. **NEVER skip agents** - Stop hook blocks incomplete workflows
-4. **ALWAYS use conventional commits** - feat:, fix:, refactor:, docs:
-5. **NEVER commit to main** - Create feature/fix branches
-
----
-
-## Documentation
-
-- [Agent System](.claude/CLAUDE.md) - Full agent documentation
-- [Skills](.claude/skills/) - Available skills and templates
-- [Hooks](.claude/hooks/) - Workflow enforcement hooks
-
----
-
-## Setup by start-vibing
-
-This project was set up with `npx start-vibing`.
-For updates: `npx start-vibing --force`
+# Development Rules
+
+> **THESE RULES ARE MANDATORY. NO EXCEPTIONS.**
+
+---
+
+## Workflow (STRICT FLOW)
+
+```
+0. INIT TASK      →  Run commit-manager to REGISTER task start
+1. TODO LIST      →  ALWAYS create detailed todo list from prompt
+2. RESEARCH       →  Run research agent for NEW features (MANDATORY)
+3. AUDIT          →  Check docs from last audit OR run fresh audit
+4. CREATE BRANCH  →  feature/ | fix/ | refactor/ | test/
+5. IMPLEMENT      →  Follow project rules + analyzer approval
+6. DOCUMENT       →  Document ALL modified files (MANDATORY)
+7. QUALITY GATES  →  Run typecheck && lint && test (Husky enforced)
+8. FINISH         →  commit-manager creates PR with task summary
+```
+
+> **CRITICAL:** Research agent is MANDATORY for any new feature or complex bug fix.
+> **CRITICAL:** All documentation must reference commit hashes for audit trail.
+> **CRITICAL:** Stop hook BLOCKS task completion if files not documented.
+> **FALLBACK:** If Task tool fails to invoke an agent, READ the agent file directly from `.claude/agents/[agent-name].md` and follow its instructions manually.
+
+---
+
+## MCP Servers (MANDATORY)
+
+Configure these in `.mcp.json` at project root:
+
+| Server                | Purpose                            | When to Use                          |
+| --------------------- | ---------------------------------- | ------------------------------------ |
+| `context7`            | Up-to-date library documentation   | Before implementing with ANY library |
+| `sequential-thinking` | Complex problem-solving            | Multi-step tasks, planning           |
+| `memory`              | Persistent knowledge graph         | Store/recall project patterns        |
+| `playwright`          | Browser automation and E2E testing | UI testing, page verification        |
+| `nextjs-devtools`     | Next.js specific development tools | Next.js projects only                |
+| `mongodb`             | MongoDB database operations        | Database queries, schema inspection  |
+
+### Usage Rules
+
+- **ALWAYS** use `context7` before implementing features with external libraries
+- **ALWAYS** use `playwright` for E2E tests instead of manual browser testing
+- **ALWAYS** check `memory` for existing patterns before creating new ones
+- **NEVER** hardcode library APIs - query `context7` for current docs
+
+---
+
+## Agent System
+
+This project uses 11 specialized AI agents:
+
+| Agent            | Purpose                       | Priority |
+| ---------------- | ----------------------------- | -------- |
+| orchestrator     | Coordinates entire workflow   | 1        |
+| analyzer         | Analyzes change impact        | 2        |
+| research         | Researches best practices     | 3        |
+| documenter       | Creates/updates documentation | 3        |
+| tester           | Creates unit and E2E tests    | 4        |
+| security-auditor | Audits security (VETO POWER)  | 5        |
+| ui-ux-reviewer   | Reviews UI/UX patterns        | 6        |
+| quality-checker  | Runs quality gates            | 7        |
+| final-validator  | Final validation (VETO POWER) | 8        |
+| domain-updater   | Updates domain knowledge      | 9        |
+| commit-manager   | Manages commits (FINAL step)  | 10       |
+
+---
+
+## Stop Hook Enforcement
+
+The Stop hook runs when Claude is about to finish and BLOCKS if:
+
+| Violation                          | Action Required                 |
+| ---------------------------------- | ------------------------------- |
+| On main branch with source changes | Create feature/fix branch first |
+| Source files not documented        | Run documenter agent            |
+| Documenter not executed            | Invoke documenter via Task tool |
+
+---
+
+## Configuration
+
+Edit these files in `.claude/config/` for your project:
+
+| File                  | Purpose                    |
+| --------------------- | -------------------------- |
+| `project-config.json` | Stack, structure, commands |
+| `quality-gates.json`  | Quality check commands     |
+| `testing-config.json` | Test framework config      |
+| `security-rules.json` | Security audit rules       |
+| `domain-mapping.json` | File patterns to domains   |
+
+---
+
+## Critical Rules
+
+1. **ALWAYS use MCP servers** - Context7 for docs, Playwright for E2E
+2. **ALWAYS start with todo list** - Track progress with TodoWrite tool
+3. **NEVER skip agents** - Stop hook blocks incomplete workflows
+4. **ALWAYS use conventional commits** - feat:, fix:, refactor:, docs:
+5. **NEVER commit to main** - Create feature/fix branches
+
+---
+
+## Documentation
+
+- [Agent System](.claude/CLAUDE.md) - Full agent documentation
+- [Skills](.claude/skills/) - Available skills and templates
+- [Hooks](.claude/hooks/) - Workflow enforcement hooks
+
+---
+
+## Setup by start-vibing
+
+This project was set up with `npx start-vibing`.
+For updates: `npx start-vibing --force`