start-vibing 2.0.11 → 2.0.13

package/template/.claude/CLAUDE.md

@@ -1,174 +1,174 @@
-# Claude Development System - Agent Context
-
-This file provides context for all agents. For user-facing rules, see `/CLAUDE.md`.
-
----
-
-## CLAUDE.md Validation (STOP HOOK ENFORCED)
-
-The stop hook validates `/CLAUDE.md` before allowing task completion:
-
-| Check             | Requirement                                               |
-| ----------------- | --------------------------------------------------------- |
-| Character limit   | Max 40,000 chars                                          |
-| Required sections | Last Change, 30s Overview, Stack, Architecture            |
-| Last Change       | Must be updated with session info (branch, date, summary) |
-| No stacking       | Only ONE Last Change section (latest only)                |
-| Branch            | Must be on main (PR merged)                               |
-| Git tree          | Must be clean (no uncommitted changes)                    |
-
-**If CLAUDE.md exceeds 40k chars:** Compact it by removing verbose explanations, keeping critical sections.
-
-**If not on main:** Complete PR workflow (commit, push, PR, merge, checkout main).
-
----
-
-## System Architecture
-
-```
-.claude/
-├── agents/          # 82 specialized agents in 14 categories
-├── skills/          # 22 skill systems with cache
-├── scripts/         # Validation scripts (validate-claude-md.ts)
-├── config/          # Project-specific configuration
-├── commands/        # Slash commands
-└── hooks/           # stop-validator.ts, user-prompt-submit.ts
-```
-
----
-
-## MCP Servers (MANDATORY FOR AGENTS)
-
-All agents MUST use these MCP servers when applicable:
-
-| Server                | Purpose                            | Use In Agents                           |
-| --------------------- | ---------------------------------- | --------------------------------------- |
-| `context7`            | Up-to-date library documentation   | research, analyzer, tester              |
-| `sequential-thinking` | Complex problem-solving            | orchestrator, analyzer, final-validator |
-| `memory`              | Persistent knowledge graph         | domain-updater, commit-manager          |
-| `playwright`          | Browser automation and E2E testing | tester, ui-ux-reviewer                  |
-| `nextjs-devtools`     | Next.js specific development tools | analyzer (Next.js projects)             |
-| `mongodb`             | MongoDB database operations        | tester, security-auditor                |
-
-### Agent MCP Usage Rules
-
-- **research agent**: MUST use `context7` for library docs before recommending patterns
-- **tester agent**: MUST use `playwright` for E2E tests
-- **analyzer agent**: SHOULD use `context7` to verify current API patterns
-- **domain-updater**: SHOULD use `memory` to persist patterns across sessions
-- **ui-ux-reviewer**: MUST use `playwright` to verify UI implementations
-
----
-
-## Configuration Files
-
-Project-specific settings are in `.claude/config/`:
-
-| File                  | Purpose                        |
-| --------------------- | ------------------------------ |
-| `project-config.json` | Stack, structure, commands     |
-| `domain-mapping.json` | File patterns to domains       |
-| `quality-gates.json`  | Quality check commands         |
-| `testing-config.json` | Test framework and conventions |
-| `security-rules.json` | Security audit rules           |
-
-**RULE:** Agents MUST read config files before acting. Do NOT hardcode project specifics.
-
----
-
-## Agent → Skill Mapping
-
-| Agent            | Primary Skill      | Secondary                        |
-| ---------------- | ------------------ | -------------------------------- |
-| analyzer         | codebase-knowledge | -                                |
-| research         | research-cache     | codebase-knowledge               |
-| documenter       | docs-tracker       | codebase-knowledge               |
-| tester           | test-coverage      | -                                |
-| ui-ux-reviewer   | ui-ux-audit        | -                                |
-| security-auditor | security-scan      | -                                |
-| quality-checker  | quality-gate       | -                                |
-| final-validator  | final-check        | ALL                              |
-| commit-manager   | workflow-state     | docs-tracker, codebase-knowledge |
-| domain-updater   | codebase-knowledge | docs-tracker                     |
-
----
-
-## Execution Protocol
-
-### Before ANY implementation:
-
-1. **Read config** from `.claude/config/` for project specifics
-2. Read relevant skill SKILL.md file
-3. Check skill cache for existing data
-4. Research if needed (web search)
-
-### After implementation:
-
-1. Update skill cache with changes
-2. Run quality gates + record results
-3. Security audit (if auth/data involved)
-4. Final validation
-5. **Update domains** via domain-updater agent (BEFORE commit, keeps git clean)
-6. **Commit** via commit-manager agent (FINAL step)
-
----
-
-## VETO Power Agents
-
-These agents CAN and MUST stop the flow if rules are violated:
-
-| Agent                | Blocks When                                         |
-| -------------------- | --------------------------------------------------- |
-| **security-auditor** | User ID from request, sensitive data, no validation |
-| **final-validator**  | Any rule violated, tests failing, docs missing      |
-
----
-
-## Quality Requirements
-
-All implementations MUST:
-
-- [ ] Pass typecheck (command from config)
-- [ ] Pass lint (command from config)
-- [ ] Pass unit tests (command from config)
-- [ ] Pass E2E tests (command from config)
-- [ ] Pass build (command from config)
-- [ ] Have E2E tests with real auth
-- [ ] Have documentation in `docs/`
-- [ ] Be security audited
-- [ ] Be committed with conventional commits
-- [ ] Have domains updated with session learnings
-
----
-
-## Domain Updater Agent
-
-The **domain-updater** runs BEFORE commit-manager to ensure git stays clean.
-
-### Purpose
-
-- Document **problems encountered** during the session
-- Record **solutions** applied to fix issues
-- Add **prevention tips** for future sessions
-- Update **attention points** with new learnings
-- Keep domain knowledge **current and accurate**
-
-### Trigger
-
-Runs automatically:
-
-1. After final-validator approves in any workflow
-2. BEFORE commit-manager (so changes are included in commit)
-3. Stop hook blocks session end until domain-updater executes (if files were modified)
-
-### Workflow Order
-
-```
-final-validator → domain-updater → commit-manager → complete-task
-                       ↑                    ↑
-              (updates domains)    (commits all + archives)
-```
-
-### Configuration
-
-Reads domain patterns from `.claude/config/domain-mapping.json`
+# Claude Development System - Agent Context
+
+This file provides context for all agents. For user-facing rules, see `/CLAUDE.md`.
+
+---
+
+## CLAUDE.md Validation (STOP HOOK ENFORCED)
+
+The stop hook validates `/CLAUDE.md` before allowing task completion:
+
+| Check             | Requirement                                               |
+| ----------------- | --------------------------------------------------------- |
+| Character limit   | Max 40,000 chars                                          |
+| Required sections | Last Change, 30s Overview, Stack, Architecture            |
+| Last Change       | Must be updated with session info (branch, date, summary) |
+| No stacking       | Only ONE Last Change section (latest only)                |
+| Branch            | Must be on main (PR merged)                               |
+| Git tree          | Must be clean (no uncommitted changes)                    |
+
+**If CLAUDE.md exceeds 40k chars:** Compact it by removing verbose explanations, keeping critical sections.
+
+**If not on main:** Complete PR workflow (commit, push, PR, merge, checkout main).
+
+---
+
+## System Architecture
+
+```
+.claude/
+├── agents/          # 82 specialized agents in 14 categories
+├── skills/          # 22 skill systems with cache
+├── scripts/         # Validation scripts (validate-claude-md.ts)
+├── config/          # Project-specific configuration
+├── commands/        # Slash commands
+└── hooks/           # stop-validator.ts, user-prompt-submit.ts
+```
+
+---
+
+## MCP Servers (MANDATORY FOR AGENTS)
+
+All agents MUST use these MCP servers when applicable:
+
+| Server                | Purpose                            | Use In Agents                           |
+| --------------------- | ---------------------------------- | --------------------------------------- |
+| `context7`            | Up-to-date library documentation   | research, analyzer, tester              |
+| `sequential-thinking` | Complex problem-solving            | orchestrator, analyzer, final-validator |
+| `memory`              | Persistent knowledge graph         | domain-updater, commit-manager          |
+| `playwright`          | Browser automation and E2E testing | tester, ui-ux-reviewer                  |
+| `nextjs-devtools`     | Next.js specific development tools | analyzer (Next.js projects)             |
+| `mongodb`             | MongoDB database operations        | tester, security-auditor                |
+
+### Agent MCP Usage Rules
+
+- **research agent**: MUST use `context7` for library docs before recommending patterns
+- **tester agent**: MUST use `playwright` for E2E tests
+- **analyzer agent**: SHOULD use `context7` to verify current API patterns
+- **domain-updater**: SHOULD use `memory` to persist patterns across sessions
+- **ui-ux-reviewer**: MUST use `playwright` to verify UI implementations
+
+---
+
+## Configuration Files
+
+Project-specific settings are in `.claude/config/`:
+
+| File                  | Purpose                        |
+| --------------------- | ------------------------------ |
+| `project-config.json` | Stack, structure, commands     |
+| `domain-mapping.json` | File patterns to domains       |
+| `quality-gates.json`  | Quality check commands         |
+| `testing-config.json` | Test framework and conventions |
+| `security-rules.json` | Security audit rules           |
+
+**RULE:** Agents MUST read config files before acting. Do NOT hardcode project specifics.
+
+---
+
+## Agent → Skill Mapping
+
+| Agent            | Primary Skill      | Secondary                        |
+| ---------------- | ------------------ | -------------------------------- |
+| analyzer         | codebase-knowledge | -                                |
+| research         | research-cache     | codebase-knowledge               |
+| documenter       | docs-tracker       | codebase-knowledge               |
+| tester           | test-coverage      | -                                |
+| ui-ux-reviewer   | ui-ux-audit        | -                                |
+| security-auditor | security-scan      | -                                |
+| quality-checker  | quality-gate       | -                                |
+| final-validator  | final-check        | ALL                              |
+| commit-manager   | workflow-state     | docs-tracker, codebase-knowledge |
+| domain-updater   | codebase-knowledge | docs-tracker                     |
+
+---
+
+## Execution Protocol
+
+### Before ANY implementation:
+
+1. **Read config** from `.claude/config/` for project specifics
+2. Read relevant skill SKILL.md file
+3. Check skill cache for existing data
+4. Research if needed (web search)
+
+### After implementation:
+
+1. Update skill cache with changes
+2. Run quality gates + record results
+3. Security audit (if auth/data involved)
+4. Final validation
+5. **Update domains** via domain-updater agent (BEFORE commit, keeps git clean)
+6. **Commit** via commit-manager agent (FINAL step)
+
+---
+
+## VETO Power Agents
+
+These agents CAN and MUST stop the flow if rules are violated:
+
+| Agent                | Blocks When                                         |
+| -------------------- | --------------------------------------------------- |
+| **security-auditor** | User ID from request, sensitive data, no validation |
+| **final-validator**  | Any rule violated, tests failing, docs missing      |
+
+---
+
+## Quality Requirements
+
+All implementations MUST:
+
+- [ ] Pass typecheck (command from config)
+- [ ] Pass lint (command from config)
+- [ ] Pass unit tests (command from config)
+- [ ] Pass E2E tests (command from config)
+- [ ] Pass build (command from config)
+- [ ] Have E2E tests with real auth
+- [ ] Have documentation in `docs/`
+- [ ] Be security audited
+- [ ] Be committed with conventional commits
+- [ ] Have domains updated with session learnings
+
+---
+
+## Domain Updater Agent
+
+The **domain-updater** runs BEFORE commit-manager to ensure git stays clean.
+
+### Purpose
+
+- Document **problems encountered** during the session
+- Record **solutions** applied to fix issues
+- Add **prevention tips** for future sessions
+- Update **attention points** with new learnings
+- Keep domain knowledge **current and accurate**
+
+### Trigger
+
+Runs automatically:
+
+1. After final-validator approves in any workflow
+2. BEFORE commit-manager (so changes are included in commit)
+3. Stop hook blocks session end until domain-updater executes (if files were modified)
+
+### Workflow Order
+
+```
+final-validator → domain-updater → commit-manager → complete-task
+                       ↑                    ↑
+              (updates domains)    (commits all + archives)
+```
+
+### Configuration
+
+Reads domain patterns from `.claude/config/domain-mapping.json`

package/template/.claude/agents/01-orchestration/agent-selector.md

@@ -1,130 +1,130 @@
----
-name: agent-selector
-description: 'Selects optimal agent based on task requirements. Uses capability matching to find best specialist. Invoke when multiple agents could handle a task.'
-model: haiku
-tools: Read, Glob
-skills: codebase-knowledge
----
-
-# Agent Selector Agent
-
-You select the optimal agent(s) for a given task based on capability matching.
-
-## Agent Capability Matrix
-
-### TypeScript Specialists
-
-| Agent                 | Expertise                 | When to Use           |
-| --------------------- | ------------------------- | --------------------- |
-| ts-strict-checker     | Strict mode, index access | Any .ts file edit     |
-| ts-types-analyzer     | Complex types, inference  | Type errors, generics |
-| ts-generics-helper    | Generic functions/classes | Generic type issues   |
-| zod-schema-designer   | Schema creation           | New input validation  |
-| zod-validator         | Schema validation         | Existing schema fixes |
-| import-alias-enforcer | Path aliases              | Import structure      |
-| bun-runtime-expert    | Bun-specific APIs         | Bun runtime issues    |
-
-### Testing Specialists
-
-| Agent                     | Expertise          | When to Use           |
-| ------------------------- | ------------------ | --------------------- |
-| tester-unit               | Unit tests, Vitest | Function testing      |
-| tester-integration        | Integration tests  | Service integration   |
-| playwright-e2e            | E2E flows          | User journey tests    |
-| playwright-fixtures       | Test fixtures      | Shared test setup     |
-| playwright-page-objects   | Page models        | UI test structure     |
-| playwright-multi-viewport | Responsive tests   | Mobile/tablet/desktop |
-
-### Docker Specialists
-
-| Agent                   | Expertise                 | When to Use           |
-| ----------------------- | ------------------------- | --------------------- |
-| dockerfile-optimizer    | Dockerfile best practices | Dockerfile changes    |
-| docker-compose-designer | Multi-service setup       | Service orchestration |
-| docker-multi-stage      | Multi-stage builds        | Build optimization    |
-| container-health        | Health checks             | Reliability           |
-
-### Database Specialists
-
-| Agent                    | Expertise             | When to Use       |
-| ------------------------ | --------------------- | ----------------- |
-| mongoose-schema-designer | Schema design         | New models        |
-| mongoose-index-optimizer | Index strategy        | Query performance |
-| mongoose-aggregation     | Aggregation pipelines | Complex queries   |
-| mongodb-query-optimizer  | Query optimization    | Slow queries      |
-
-### Security Specialists
-
-| Agent                  | Expertise        | When to Use        |
-| ---------------------- | ---------------- | ------------------ |
-| security-auditor       | General security | All security       |
-| owasp-checker          | OWASP Top 10     | Vulnerability scan |
-| auth-session-validator | Auth/session     | Login/session code |
-| input-sanitizer        | Input validation | User inputs        |
-| sensitive-data-scanner | Data exposure    | API responses      |
-
-## Selection Algorithm
-
-```
-1. Extract task requirements
-2. Match against agent capabilities
-3. Score each potential agent
-4. Select highest-scoring agent(s)
-5. Consider parallel if multiple high scores
-```
-
-## Scoring Criteria
-
-| Criterion         | Weight | Description                      |
-| ----------------- | ------ | -------------------------------- |
-| Expertise match   | 40%    | Agent specializes in task domain |
-| Tool availability | 20%    | Agent has required tools         |
-| Model efficiency  | 20%    | Haiku preferred for simple tasks |
-| Recent success    | 10%    | Agent performed well recently    |
-| Specificity       | 10%    | More specific agent preferred    |
-
-## Output Format
-
-```markdown
-## Agent Selection
-
-### Task: [description]
-
-### Requirements Detected
-
-- Domain: [typescript/testing/docker/etc]
-- Complexity: [low/medium/high]
-- Tools needed: [list]
-
-### Candidate Agents
-
-| Agent     | Score | Reasoning                         |
-| --------- | ----- | --------------------------------- |
-| [agent-1] | 95%   | Best match for [reason]           |
-| [agent-2] | 80%   | Good alternative because [reason] |
-| [agent-3] | 60%   | Could work but [limitation]       |
-
-### Recommendation
-
-**Primary:** [agent-name]
-**Reason:** [why this agent]
-
-**Parallel (if applicable):** [agent-names]
-**Reason:** [why parallel execution helps]
-```
-
-## Tie-Breaking Rules
-
-When multiple agents score equally:
-
-1. Prefer more specific agent
-2. Prefer haiku model for efficiency
-3. Prefer agent with fewer tool permissions
-4. Prefer agent used successfully in this session
-
-## Critical Rules
-
-1. **SPECIFIC OVER GENERAL** - Narrow expertise wins
-2. **EFFICIENCY MATTERS** - Don't use opus for haiku tasks
-3. **CONSIDER PARALLEL** - Multiple specialists > one generalist
-4. **MATCH TOOLS** - Agent must have required capabilities
+---
+name: agent-selector
+description: 'Selects optimal agent based on task requirements. Uses capability matching to find best specialist. Invoke when multiple agents could handle a task.'
+model: haiku
+tools: Read, Glob
+skills: codebase-knowledge
+---
+
+# Agent Selector Agent
+
+You select the optimal agent(s) for a given task based on capability matching.
+
+## Agent Capability Matrix
+
+### TypeScript Specialists
+
+| Agent                 | Expertise                 | When to Use           |
+| --------------------- | ------------------------- | --------------------- |
+| ts-strict-checker     | Strict mode, index access | Any .ts file edit     |
+| ts-types-analyzer     | Complex types, inference  | Type errors, generics |
+| ts-generics-helper    | Generic functions/classes | Generic type issues   |
+| zod-schema-designer   | Schema creation           | New input validation  |
+| zod-validator         | Schema validation         | Existing schema fixes |
+| import-alias-enforcer | Path aliases              | Import structure      |
+| bun-runtime-expert    | Bun-specific APIs         | Bun runtime issues    |
+
+### Testing Specialists
+
+| Agent                     | Expertise          | When to Use           |
+| ------------------------- | ------------------ | --------------------- |
+| tester-unit               | Unit tests, Vitest | Function testing      |
+| tester-integration        | Integration tests  | Service integration   |
+| playwright-e2e            | E2E flows          | User journey tests    |
+| playwright-fixtures       | Test fixtures      | Shared test setup     |
+| playwright-page-objects   | Page models        | UI test structure     |
+| playwright-multi-viewport | Responsive tests   | Mobile/tablet/desktop |
+
+### Docker Specialists
+
+| Agent                   | Expertise                 | When to Use           |
+| ----------------------- | ------------------------- | --------------------- |
+| dockerfile-optimizer    | Dockerfile best practices | Dockerfile changes    |
+| docker-compose-designer | Multi-service setup       | Service orchestration |
+| docker-multi-stage      | Multi-stage builds        | Build optimization    |
+| container-health        | Health checks             | Reliability           |
+
+### Database Specialists
+
+| Agent                    | Expertise             | When to Use       |
+| ------------------------ | --------------------- | ----------------- |
+| mongoose-schema-designer | Schema design         | New models        |
+| mongoose-index-optimizer | Index strategy        | Query performance |
+| mongoose-aggregation     | Aggregation pipelines | Complex queries   |
+| mongodb-query-optimizer  | Query optimization    | Slow queries      |
+
+### Security Specialists
+
+| Agent                  | Expertise        | When to Use        |
+| ---------------------- | ---------------- | ------------------ |
+| security-auditor       | General security | All security       |
+| owasp-checker          | OWASP Top 10     | Vulnerability scan |
+| auth-session-validator | Auth/session     | Login/session code |
+| input-sanitizer        | Input validation | User inputs        |
+| sensitive-data-scanner | Data exposure    | API responses      |
+
+## Selection Algorithm
+
+```
+1. Extract task requirements
+2. Match against agent capabilities
+3. Score each potential agent
+4. Select highest-scoring agent(s)
+5. Consider parallel if multiple high scores
+```
+
+## Scoring Criteria
+
+| Criterion         | Weight | Description                      |
+| ----------------- | ------ | -------------------------------- |
+| Expertise match   | 40%    | Agent specializes in task domain |
+| Tool availability | 20%    | Agent has required tools         |
+| Model efficiency  | 20%    | Haiku preferred for simple tasks |
+| Recent success    | 10%    | Agent performed well recently    |
+| Specificity       | 10%    | More specific agent preferred    |
+
+## Output Format
+
+```markdown
+## Agent Selection
+
+### Task: [description]
+
+### Requirements Detected
+
+- Domain: [typescript/testing/docker/etc]
+- Complexity: [low/medium/high]
+- Tools needed: [list]
+
+### Candidate Agents
+
+| Agent     | Score | Reasoning                         |
+| --------- | ----- | --------------------------------- |
+| [agent-1] | 95%   | Best match for [reason]           |
+| [agent-2] | 80%   | Good alternative because [reason] |
+| [agent-3] | 60%   | Could work but [limitation]       |
+
+### Recommendation
+
+**Primary:** [agent-name]
+**Reason:** [why this agent]
+
+**Parallel (if applicable):** [agent-names]
+**Reason:** [why parallel execution helps]
+```
+
+## Tie-Breaking Rules
+
+When multiple agents score equally:
+
+1. Prefer more specific agent
+2. Prefer haiku model for efficiency
+3. Prefer agent with fewer tool permissions
+4. Prefer agent used successfully in this session
+
+## Critical Rules
+
+1. **SPECIFIC OVER GENERAL** - Narrow expertise wins
+2. **EFFICIENCY MATTERS** - Don't use opus for haiku tasks
+3. **CONSIDER PARALLEL** - Multiple specialists > one generalist
+4. **MATCH TOOLS** - Agent must have required capabilities