Add Husky, Prettier, ESLint, and Vitest hooks

.claude/commands/brainstorm.md

@@ -1,7 +1,7 @@
 ---
 name: workflows:brainstorm
 description: Explore requirements and approaches through collaborative dialogue before planning implementation
-argument-hint: "[feature idea or problem to explore]"
+argument-hint: '[feature idea or problem to explore]'
 ---
 
 # Brainstorm a Feature or Improvement

.claude/commands/compound.md

@@ -1,7 +1,7 @@
 ---
 name: workflows:compound
 description: Document a recently solved problem to compound your team's knowledge
-argument-hint: "[optional: brief context about the fix]"
+argument-hint: '[optional: brief context about the fix]'
 ---
 
 # /compound
@@ -36,33 +36,38 @@ Phase 1 subagents return TEXT DATA to the orchestrator. They must NOT use Write,
 Launch these subagents IN PARALLEL. Each returns text data to the orchestrator.
 
 #### 1. **Context Analyzer**
-   - Extracts conversation history
-   - Identifies problem type, component, symptoms
-   - Validates against schema
-   - Returns: YAML frontmatter skeleton
+
+- Extracts conversation history
+- Identifies problem type, component, symptoms
+- Validates against schema
+- Returns: YAML frontmatter skeleton
 
 #### 2. **Solution Extractor**
-   - Analyzes all investigation steps
-   - Identifies root cause
-   - Extracts working solution with code examples
-   - Returns: Solution content block
+
+- Analyzes all investigation steps
+- Identifies root cause
+- Extracts working solution with code examples
+- Returns: Solution content block
 
 #### 3. **Related Docs Finder**
-   - Searches `docs/solutions/` for related documentation
-   - Identifies cross-references and links
-   - Returns: Links and relationships
+
+- Searches `docs/solutions/` for related documentation
+- Identifies cross-references and links
+- Returns: Links and relationships
 
 #### 4. **Prevention Strategist**
-   - Develops prevention strategies
-   - Creates best practices guidance
-   - Generates test cases if applicable
-   - Returns: Prevention/testing content
+
+- Develops prevention strategies
+- Creates best practices guidance
+- Generates test cases if applicable
+- Returns: Prevention/testing content
 
 #### 5. **Category Classifier**
-   - Determines optimal `docs/solutions/` category
-   - Validates category against schema
-   - Suggests filename based on slug
-   - Returns: Final path and filename
+
+- Determines optimal `docs/solutions/` category
+- Validates category against schema
+- Suggests filename based on slug
+- Returns: Final path and filename
 
 </parallel_tasks>
 
@@ -124,12 +129,13 @@ This creates a compounding knowledge system:
 
 <auto_invoke>
 <trigger_phrases>
+
 - "that worked"
 - "it's fixed"
 - "working now"
 - "problem solved"
-</trigger_phrases>
-</auto_invoke>
+  </trigger_phrases>
+  </auto_invoke>
 
 ## Routes To
 

.claude/commands/plan.md

@@ -1,7 +1,7 @@
 ---
 name: workflows:plan
 description: Transform feature descriptions into well-structured project plans following conventions
-argument-hint: "[feature description, bug report, or improvement idea]"
+argument-hint: '[feature description, bug report, or improvement idea]'
 ---
 
 # Create a plan for a new feature or bug fix

.claude/commands/review.md

@@ -1,7 +1,7 @@
 ---
 name: workflows:review
 description: Perform exhaustive code reviews using multi-agent analysis
-argument-hint: "[PR number, GitHub URL, branch name, or latest]"
+argument-hint: '[PR number, GitHub URL, branch name, or latest]'
 ---
 
 # Review Command
@@ -42,7 +42,7 @@ The following paths are pipeline artifacts and must never be flagged for deletio
 
 - `docs/plans/*.md` — Plan files created by `/workflows:plan`
 - `docs/solutions/*.md` — Solution documents created during the pipeline
-</protected_artifacts>
+  </protected_artifacts>
 
 #### Load Review Agents
 
@@ -59,6 +59,7 @@ Task {agent-name}(PR content + review context from settings body)
 ```
 
 Additionally, always run this regardless of settings:
+
 - Task learnings-researcher(PR content) - Search docs/solutions/ for past issues related to this PR's modules and patterns
 
 </parallel_tasks>
@@ -108,6 +109,7 @@ Use the file-todos skill to create todo files for ALL findings immediately.
 - Follow naming convention: `{issue_id}-pending-{priority}-{description}.md`
 
 **Examples:**
+
 ```
 001-pending-p1-path-traversal-vulnerability.md
 002-pending-p1-api-response-validation.md
@@ -126,15 +128,18 @@ After creating all todo files, present comprehensive summary:
 **Branch:** [branch-name]
 
 ### Findings Summary:
+
 - **Total Findings:** [X]
 - **CRITICAL (P1):** [count] - BLOCKS MERGE
 - **IMPORTANT (P2):** [count] - Should Fix
 - **NICE-TO-HAVE (P3):** [count] - Enhancements
 
 ### Created Todo Files:
+
 [list all created todo files]
 
 ### Next Steps:
+
 1. Address P1 Findings (CRITICAL - must be fixed before merge)
 2. Triage All Todos: `ls todos/*-pending-*.md`
 ```

.claude/commands/work.md

@@ -1,7 +1,7 @@
 ---
 name: workflows:work
 description: Execute work plans efficiently while maintaining quality and finishing features
-argument-hint: "[plan file, specification, or todo file path]"
+argument-hint: '[plan file, specification, or todo file path]'
 ---
 
 # Work Plan Execution Command
@@ -21,7 +21,6 @@ This command takes a work document (plan, specification, or todo file) and execu
 ### Phase 1: Quick Start
 
 1. **Read Plan and Clarify**
-
    - Read the work document completely
    - Review any references or links provided in the plan
    - If anything is unclear or ambiguous, ask clarifying questions now
@@ -50,10 +49,12 @@ This command takes a work document (plan, specification, or todo file) and execu
    **If on the default branch**, choose how to proceed:
 
    **Option A: Create a new branch**
+
    ```bash
    git pull origin [default_branch]
    git checkout -b feature-branch-name
    ```
+
    Use a meaningful name based on the work (e.g., `feat/user-authentication`, `fix/email-validation`).
 
    **Option B: Continue on the default branch**
@@ -93,16 +94,17 @@ This command takes a work document (plan, specification, or todo file) and execu
 
    After completing each task, evaluate whether to create an incremental commit:
 
-   | Commit when... | Don't commit when... |
-   |----------------|---------------------|
-   | Logical unit complete (model, service, component) | Small part of a larger unit |
-   | Tests pass + meaningful progress | Tests failing |
-   | About to switch contexts (backend → frontend) | Purely scaffolding with no behavior |
-   | About to attempt risky/uncertain changes | Would need a "WIP" commit message |
+   | Commit when...                                    | Don't commit when...                |
+   | ------------------------------------------------- | ----------------------------------- |
+   | Logical unit complete (model, service, component) | Small part of a larger unit         |
+   | Tests pass + meaningful progress                  | Tests failing                       |
+   | About to switch contexts (backend → frontend)     | Purely scaffolding with no behavior |
+   | About to attempt risky/uncertain changes          | Would need a "WIP" commit message   |
 
    **Heuristic:** "Can I write a commit message that describes a complete, valuable change? If yes, commit. If the message would be 'WIP' or 'partial X', wait."
 
    **Commit workflow:**
+
    ```bash
    # 1. Verify tests pass (use project's test command)
    # 2. Stage only files related to this logical unit (not `git add .`)
@@ -112,15 +114,13 @@ This command takes a work document (plan, specification, or todo file) and execu
    ```
 
 3. **Follow Existing Patterns**
-
    - The plan should reference similar code - read those files first
    - Match naming conventions exactly
    - Reuse existing components where possible
    - Follow project coding standards (see CLAUDE.md)
    - When in doubt, grep for similar implementations
 
 4. **Test Continuously**
-
    - Run relevant tests after each significant change
    - Don't wait until the end to test
    - Fix failures immediately
@@ -197,6 +197,7 @@ This command takes a work document (plan, specification, or todo file) and execu
 3. **Update Plan Status**
 
    If the input document has YAML frontmatter with a `status` field, update it to `completed`:
+
    ```
    status: active  →  status: completed
    ```

.claude/skills/compound-docs/SKILL.md

@@ -50,7 +50,7 @@ This skill captures problem solutions immediately after confirmation, creating s
 - Simple typos
 - Obvious syntax errors
 - Trivial fixes immediately corrected
-</step>
+  </step>
 
 <step number="2" required="true" depends_on="1">
 ### Step 2: Gather Context
@@ -94,7 +94,7 @@ Format: `[sanitized-symptom]-[module]-[YYYYMMDD].md`
 - Replace spaces with hyphens
 - Remove special characters except hyphens
 - Truncate to reasonable length (< 80 chars)
-</step>
+  </step>
 
 <step number="5" required="true" depends_on="4" blocking="true">
 ### Step 5: Validate YAML Schema

.claude/skills/compound-docs/assets/critical-pattern-template.md

@@ -7,11 +7,13 @@ Use this template when adding a pattern to `docs/solutions/patterns/critical-pat
 ## N. [Pattern Name] (ALWAYS REQUIRED)
 
 ### WRONG ([Will cause X error])
+
 ```[language]
 [code showing wrong approach]
 ```
 
 ### CORRECT
+
 ```[language]
 [code showing correct approach]
 ```
@@ -25,6 +27,7 @@ Use this template when adding a pattern to `docs/solutions/patterns/critical-pat
 ---
 
 **Instructions:**
+
 1. Replace N with the next pattern number
 2. Replace [Pattern Name] with descriptive title
 3. Fill in WRONG example with code that causes the problem

.claude/skills/compound-docs/assets/resolution-template.md

@@ -1,37 +1,48 @@
 ---
 module: [Module name or "System" for system-wide]
 date: [YYYY-MM-DD]
-problem_type: [build_error|test_failure|runtime_error|performance_issue|database_issue|security_issue|ui_bug|integration_issue|logic_error]
+problem_type:
+  [
+    build_error|test_failure|runtime_error|performance_issue|database_issue|security_issue|ui_bug|integration_issue|logic_error,
+  ]
 component: [Technical component involved]
 symptoms:
   - [Observable symptom 1 - specific error message or behavior]
   - [Observable symptom 2 - what user actually saw/experienced]
 root_cause: [Fundamental cause of the problem]
-resolution_type: [code_fix|migration|config_change|test_fix|dependency_update|environment_setup]
+resolution_type:
+  [
+    code_fix|migration|config_change|test_fix|dependency_update|environment_setup,
+  ]
 severity: [critical|high|medium|low]
 tags: [keyword1, keyword2, keyword3]
 ---
 
 # Troubleshooting: [Clear Problem Title]
 
 ## Problem
+
 [1-2 sentence clear description of the issue and what the user experienced]
 
 ## Environment
+
 - Module: [Name or "System-wide"]
 - Affected Component: [e.g., "Rendering pipeline", "Auth service"]
 - Date: [YYYY-MM-DD when this was solved]
 
 ## Symptoms
+
 - [Observable symptom 1 - what the user saw/experienced]
 - [Observable symptom 2 - error messages, visual issues, unexpected behavior]
 
 ## What Didn't Work
 
 **Attempted Solution 1:** [Description of what was tried]
+
 - **Why it failed:** [Technical reason this didn't solve the problem]
 
 **Attempted Solution 2:** [Description of second attempt]
+
 - **Why it failed:** [Technical reason]
 
 [If nothing else was attempted first, write:]
@@ -42,6 +53,7 @@ tags: [keyword1, keyword2, keyword3]
 [The actual fix that worked - provide specific details]
 
 **Code changes** (if applicable):
+
 ```
 # Before (broken):
 [Show the problematic code]
@@ -53,20 +65,23 @@ tags: [keyword1, keyword2, keyword3]
 ## Why This Works
 
 [Technical explanation of:]
+
 1. What was the ROOT CAUSE of the problem?
 2. Why does the solution address this root cause?
 3. What was the underlying issue?
 
 ## Prevention
 
 [How to avoid this problem in future development:]
+
 - [Specific coding practice, check, or pattern to follow]
 - [What to watch out for]
 - [How to catch this early]
 
 ## Related Issues
 
 [If any similar problems exist in docs/solutions/, link to them:]
+
 - See also: [another-related-issue.md](../category/another-related-issue.md)
 
 [If no related issues, write:]

.claude/skills/compound-docs/references/yaml-schema.md

@@ -34,9 +34,9 @@ date: 2026-02-15
 problem_type: performance_issue
 component: rendering_pipeline
 symptoms:
-  - "Frame drops below 30fps during particle effects"
-  - "GPU memory spikes during scene transitions"
-root_cause: "Unoptimized particle batch rendering"
+  - 'Frame drops below 30fps during particle effects'
+  - 'GPU memory spikes during scene transitions'
+root_cause: 'Unoptimized particle batch rendering'
 resolution_type: code_fix
 severity: high
 tags: [performance, rendering, particles]