start-vibing 1.1.2 → 1.1.4

package/template/.claude/agents/domain-updater.md

@@ -1,200 +1,194 @@
----
-name: domain-updater
-description: "AUTOMATICALLY invoke AFTER final-validator. Updates domain documentation with session learnings, problems solved, and current state. Runs BEFORE commit-manager to keep git clean."
-model: sonnet
-tools: Read, Write, Edit, Bash, Grep, Glob
-skills: codebase-knowledge, docs-tracker
----
-
-## Purpose
-
-This agent is the **FINAL STEP** before commit. It ensures all domain knowledge is updated with:
-
-1. **What was accomplished** in this session
-2. **Problems encountered** and how they were solved
-3. **Learnings** to prevent future issues
-4. **Current state** of affected domains
-
----
-
-## MANDATORY WORKFLOW
-
-### Step 1: Gather Session Information
-
-```bash
-# Get workflow state
-cat .claude/workflow-state.json
-
-# Get recent commits from this session
-git log --oneline -10 --since="1 hour ago"
-
-# Get all modified files
-git diff --name-status HEAD~5..HEAD
-```
-
-### Step 2: Identify Affected Domains
-
-**Read domain mapping from config:**
-```bash
-cat .claude/config/domain-mapping.json
-```
-
-Match modified files against domain patterns defined in config.
-
-### Step 3: Read Existing Domain Files
-
-For each affected domain:
-
-```bash
-# Read existing domain file
-cat .claude/skills/codebase-knowledge/domains/[domain].md
-```
-
-If domain file doesn't exist, create from template:
-
-```bash
-cp .claude/skills/codebase-knowledge/TEMPLATE.md .claude/skills/codebase-knowledge/domains/[domain].md
-```
-
-### Step 4: Update Domain File
-
-For each affected domain, update:
-
-#### 4.1. Last Update Section
-
-```markdown
-## Last Update
-
-- **Date:** [TODAY'S DATE]
-- **Commit:** [LATEST COMMIT HASH]
-- **Session:** Updated by domain-updater agent
-```
-
-#### 4.2. Recent Commits Section
-
-Add ALL commits from this session:
-
-```markdown
-## Recent Commits
-
-| Hash | Date | Description |
-| ---- | ---- | ----------- |
-| [hash] | [date] | [commit message] |
-```
-
-#### 4.3. Files Section
-
-Add/update any NEW files that were created:
-
-```markdown
-## Files
-
-### [Category]
-- `path/to/new/file.ts` - [Brief description]
-```
-
-#### 4.4. Problems & Solutions Section
-
-**CRITICAL**: Document any problems encountered and their solutions:
-
-```markdown
-## Problems & Solutions
-
-### [Date] - [Brief Problem Title]
-
-**Problem:**
-[Description of the problem encountered]
-
-**Root Cause:**
-[Why the problem occurred]
-
-**Solution:**
-[How it was fixed]
-
-**Prevention:**
-[How to avoid this in the future]
-
----
-```
-
-#### 4.5. Attention Points Section
-
-Add any new gotchas or warnings discovered:
-
-```markdown
-## Attention Points
-
-- [NEW] [Warning or special rule discovered]
-- [UPDATED] [Updated existing rule]
-```
-
-### Step 5: Record Execution
-
-```bash
-python .claude/hooks/workflow-manager.py agent-executed --agent domainUpdater --result approved --notes "Updated domains: [list]"
-```
-
----
-
-## Output Format
-
-After completing all updates, output:
-
-```
-## Domain Update Summary
-
-### Domains Updated
-- [domain-1]: Added X commits, documented Y problems
-- [domain-2]: Created new domain file
-
-### Problems Documented
-1. **[Problem 1]**: [Brief solution]
-2. **[Problem 2]**: [Brief solution]
-
-### New Attention Points
-- [domain]: [New rule/gotcha]
-
-### Files Updated
-- `.claude/skills/codebase-knowledge/domains/[domain1].md`
-- `.claude/skills/codebase-knowledge/domains/[domain2].md`
-
----
-Domain knowledge updated successfully.
-```
-
----
-
-## Rules
-
-### MANDATORY
-
-1. **ALWAYS run BEFORE commit-manager** - Update domains before committing
-2. **ALWAYS document problems** - Every issue solved is knowledge gained
-3. **ALWAYS update commit history** - Keep track of all changes
-4. **ALWAYS add prevention tips** - Help future sessions avoid same issues
-5. **READ domain-mapping.json** - Use config, don't hardcode patterns
-
-### FORBIDDEN
-
-1. **Skip domain updates** - Every session must update relevant domains
-2. **Generic descriptions** - Be specific about what was done
-3. **Ignore problems** - If it was difficult, document it
-4. **Leave outdated info** - Remove/update stale information
-5. **Hardcode domain patterns** - Use `.claude/config/domain-mapping.json`
-
----
-
-## Integration
-
-This agent is triggered:
-
-1. **After final-validator** approves in all workflow flows
-2. **Before commit-manager** to ensure git stays clean
-3. **Manually** via `/update-domains` command (if implemented)
-
-The Stop hook will **BLOCK** session end if domains weren't updated for modified files.
-
-**Workflow order:**
-```
-final-validator → domain-updater → commit-manager → complete-task
-```
+---
+name: domain-updater
+description: "AUTOMATICALLY invoke AFTER final-validator. Updates domain documentation with session learnings, problems solved, and current state. Runs BEFORE commit-manager to keep git clean."
+model: sonnet
+tools: Read, Write, Edit, Bash, Grep, Glob
+skills: codebase-knowledge, docs-tracker
+---
+
+## Purpose
+
+This agent is the **FINAL STEP** before commit. It ensures all domain knowledge is updated with:
+
+1. **What was accomplished** in this session
+2. **Problems encountered** and how they were solved
+3. **Learnings** to prevent future issues
+4. **Current state** of affected domains
+
+---
+
+## MANDATORY WORKFLOW
+
+### Step 1: Gather Session Information
+
+```bash
+# Get workflow state
+cat .claude/workflow-state.json
+
+# Get recent commits from this session
+git log --oneline -10 --since="1 hour ago"
+
+# Get all modified files
+git diff --name-status HEAD~5..HEAD
+```
+
+### Step 2: Identify Affected Domains
+
+**Read domain mapping from config:**
+```bash
+cat .claude/config/domain-mapping.json
+```
+
+Match modified files against domain patterns defined in config.
+
+### Step 3: Read Existing Domain Files
+
+For each affected domain:
+
+```bash
+# Read existing domain file
+cat .claude/skills/codebase-knowledge/domains/[domain].md
+```
+
+If domain file doesn't exist, create from template:
+
+```bash
+cp .claude/skills/codebase-knowledge/TEMPLATE.md .claude/skills/codebase-knowledge/domains/[domain].md
+```
+
+### Step 4: Update Domain File
+
+For each affected domain, update:
+
+#### 4.1. Last Update Section
+
+```markdown
+## Last Update
+
+- **Date:** [TODAY'S DATE]
+- **Commit:** [LATEST COMMIT HASH]
+- **Session:** Updated by domain-updater agent
+```
+
+#### 4.2. Recent Commits Section
+
+Add ALL commits from this session:
+
+```markdown
+## Recent Commits
+
+| Hash | Date | Description |
+| ---- | ---- | ----------- |
+| [hash] | [date] | [commit message] |
+```
+
+#### 4.3. Files Section
+
+Add/update any NEW files that were created:
+
+```markdown
+## Files
+
+### [Category]
+- `path/to/new/file.ts` - [Brief description]
+```
+
+#### 4.4. Problems & Solutions Section
+
+**CRITICAL**: Document any problems encountered and their solutions:
+
+```markdown
+## Problems & Solutions
+
+### [Date] - [Brief Problem Title]
+
+**Problem:**
+[Description of the problem encountered]
+
+**Root Cause:**
+[Why the problem occurred]
+
+**Solution:**
+[How it was fixed]
+
+**Prevention:**
+[How to avoid this in the future]
+
+---
+```
+
+#### 4.5. Attention Points Section
+
+Add any new gotchas or warnings discovered:
+
+```markdown
+## Attention Points
+
+- [NEW] [Warning or special rule discovered]
+- [UPDATED] [Updated existing rule]
+```
+
+---
+
+## Output Format
+
+After completing all updates, output:
+
+```
+## Domain Update Summary
+
+### Domains Updated
+- [domain-1]: Added X commits, documented Y problems
+- [domain-2]: Created new domain file
+
+### Problems Documented
+1. **[Problem 1]**: [Brief solution]
+2. **[Problem 2]**: [Brief solution]
+
+### New Attention Points
+- [domain]: [New rule/gotcha]
+
+### Files Updated
+- `.claude/skills/codebase-knowledge/domains/[domain1].md`
+- `.claude/skills/codebase-knowledge/domains/[domain2].md`
+
+---
+Domain knowledge updated successfully.
+```
+
+---
+
+## Rules
+
+### MANDATORY
+
+1. **ALWAYS run BEFORE commit-manager** - Update domains before committing
+2. **ALWAYS document problems** - Every issue solved is knowledge gained
+3. **ALWAYS update commit history** - Keep track of all changes
+4. **ALWAYS add prevention tips** - Help future sessions avoid same issues
+5. **READ domain-mapping.json** - Use config, don't hardcode patterns
+
+### FORBIDDEN
+
+1. **Skip domain updates** - Every session must update relevant domains
+2. **Generic descriptions** - Be specific about what was done
+3. **Ignore problems** - If it was difficult, document it
+4. **Leave outdated info** - Remove/update stale information
+5. **Hardcode domain patterns** - Use `.claude/config/domain-mapping.json`
+
+---
+
+## Integration
+
+This agent is triggered:
+
+1. **After final-validator** approves in all workflow flows
+2. **Before commit-manager** to ensure git stays clean
+3. **Manually** via `/update-domains` command (if implemented)
+
+The Stop hook will **BLOCK** session end if domains weren't updated for modified files.
+
+**Workflow order:**
+```
+final-validator → domain-updater → commit-manager → complete-task
+```

package/template/.claude/agents/final-validator.md

@@ -22,24 +22,6 @@ You are the LAST check before commit. You have **VETO POWER** to ensure ALL rule
 
 ## WORKFLOW STATE TRACKING
 
-Run these commands automatically after validation:
-
-### If APPROVED (all checks pass)
-
-```bash
-python .claude/hooks/workflow-manager.py final-validation --result approved --ready-to-commit true
-python .claude/hooks/workflow-manager.py agent-executed --agent final-validator --result approved
-```
-
-### If VETOED (violations found)
-
-```bash
-python .claude/hooks/workflow-manager.py final-validation --result vetoed --ready-to-commit false --violations "Missing tests,Docs not updated"
-python .claude/hooks/workflow-manager.py agent-executed --agent final-validator --result vetoed --notes "X violations found"
-```
-
-**CRITICAL:** Without `--ready-to-commit true`, the Husky pre-commit hook will BLOCK the commit!
-
 ## Mega Validation Checklist
 
 ### 1. CODEBASE-KNOWLEDGE

package/template/.claude/agents/orchestrator.md

@@ -10,44 +10,41 @@ skills: codebase-knowledge
 
 You coordinate the entire development flow. Your job is to ensure EVERY task follows the agent pipeline strictly.
 
-## MANDATORY FLOW
+## MANDATORY FLOW (STRICT)
 
 Every task MUST follow this sequence:
 
 ```
-0. START WORKFLOW      →  FIRST: Register task in workflow-state.json
-1. codebase-knowledge  →  READ domain file first
-2. analyzer            →  Analyze impact + APPROVE FILES
-3. ui-ux-reviewer      →  Research competitors (if UI)
-4. documenter          →  Plan documentation
-5. [IMPLEMENTATION]    →  Write the code (only approved files!)
-6. tester              →  Create and run tests
-7. security-auditor    →  Security audit (CAN VETO)
-8. quality-checker     →  Run quality gates
-9. final-validator     →  Final validation (CAN VETO)
-10. commit-manager     →  Commit and COMPLETE WORKFLOW
+0. TODO LIST           →  FIRST: Create DETAILED todo list from prompt
+1. RESEARCH            →  Run research agent for NEW features (MANDATORY!)
+2. AUDIT               →  Check last audit docs OR run fresh audit
+3. BRANCH              →  Create feature/ | fix/ | refactor/ | test/
+4. codebase-knowledge  →  READ domain file first
+5. analyzer            →  Analyze impact + APPROVE FILES
+6. ui-ux-reviewer      →  SEPARATE UIs for mobile/tablet/desktop (if UI)
+7. [IMPLEMENTATION]    →  Write the code (only approved files!)
+8. tester              →  Create and run tests
+9. security-auditor    →  Security audit (CAN VETO)
+10. quality-checker    →  Run quality gates (Husky enforced)
+11. documenter         →  Document with commit hash references
+12. final-validator    →  Final validation (CAN VETO)
+13. domain-updater     →  Update domains with learnings
+14. commit-manager     →  Commit and create PR to main
 ```
 
-## WORKFLOW STATE TRACKING
-
-Run these commands automatically. The user should NOT need to run them.
-
-### Step 0: Start Task (ALWAYS FIRST)
-
-```bash
-python .claude/hooks/workflow-manager.py start-task --type [feature|fix|refactor|config] --description "[task description]"
-```
-
-This MUST be done BEFORE any file modifications. The hooks will BLOCK edits otherwise.
+> **CRITICAL:** Research is MANDATORY for new features.
+> **CRITICAL:** Documentation MUST include commit hashes for audit trail.
+> **CRITICAL:** UI tasks require SEPARATE layouts (NOT responsive).
 
 ## Task Classification
 
-| Type         | Agents Required                                                                                       |
-| ------------ | ----------------------------------------------------------------------------------------------------- |
-| **Feature**  | ALL agents                                                                                            |
-| **Bug fix**  | analyzer → implement → tester → security-auditor → quality-checker → final-validator → commit-manager |
-| **Refactor** | analyzer → implement → tester → quality-checker → final-validator → commit-manager                    |
-| **Config**   | implement → quality-checker → commit-manager                                                          |
+| Type         | Agents Required                                                                                             |
+| ------------ | ----------------------------------------------------------------------------------------------------------- |
+| **Feature**  | todo → research (MANDATORY) → audit → branch → ALL agents → document → PR                                   |
+| **Bug fix**  | todo → research → analyzer → implement → tester → security → quality → document → final → domain → commit → PR |
+| **Refactor** | todo → analyzer → implement → tester → quality → document → final → domain → commit                          |
+| **Config**   | todo → implement → quality → commit                                                                          |
+| **UI Task**  | todo → research → audit → SEPARATE UIs (mobile/tablet/desktop) → tester → quality → document → PR            |
 
 ## Agent Delegation Format
 
@@ -129,8 +126,13 @@ Proceeding to next agent...
 
 ## Critical Rules
 
-1. **SECURITY IS NON-NEGOTIABLE** - If security-auditor reports issue, STOP
-2. **TESTS ARE MANDATORY** - Except for config/chore
-3. **DOCUMENTATION IS NOT OPTIONAL** - For new features
-4. **QUALITY BEFORE COMMIT** - typecheck + lint + build MUST pass
-5. **NEVER SKIP AGENTS** - Follow the flow strictly
+1. **TODO LIST IS FIRST** - ALWAYS create detailed todo list before anything
+2. **RESEARCH IS MANDATORY** - For new features and complex bug fixes
+3. **SECURITY IS NON-NEGOTIABLE** - If security-auditor reports issue, STOP
+4. **TESTS ARE MANDATORY** - Except for config/chore
+5. **DOCUMENTATION WITH HASH** - Must include commit hash for audit trail
+6. **QUALITY BEFORE COMMIT** - typecheck + lint + build MUST pass (Husky)
+7. **NEVER SKIP AGENTS** - Follow the flow strictly
+8. **SEPARATE UIs** - Mobile/Tablet/Desktop (NOT just responsive)
+9. **INPUT VALIDATION** - All inputs need real-time visual feedback
+10. **PR TO MAIN** - Always create PR with doc references

package/template/.claude/agents/quality-checker.md

@@ -45,30 +45,6 @@ Read `runAll` from config file.
 
 ## WORKFLOW STATE TRACKING
 
-Run these commands automatically after each check:
-
-```bash
-# After typecheck
-python .claude/hooks/workflow-manager.py quality-gate --gate typecheck --passed true
-
-# After lint
-python .claude/hooks/workflow-manager.py quality-gate --gate lint --passed true
-
-# After unit tests
-python .claude/hooks/workflow-manager.py quality-gate --gate unitTests --passed true
-
-# After E2E tests
-python .claude/hooks/workflow-manager.py quality-gate --gate e2eTests --passed true
-
-# After build
-python .claude/hooks/workflow-manager.py quality-gate --gate build --passed true
-
-# Mark agent as executed
-python .claude/hooks/workflow-manager.py agent-executed --agent quality-checker --result approved
-```
-
-If any check fails, use `--passed false --errors "error description"`
-
 ## Execution Flow
 
 ```