@stella-studio/ck 1.0.0

package/.claude/skills/fix/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: fix
+description: ALWAYS activate this skill before fixing ANY bug, error, test failure, CI/CD issue, type error, lint, log error, UI issue, code problem.
+version: 1.1.1
+---
+
+# Fixing
+
+Unified skill for fixing issues of any complexity with intelligent routing.
+
+## Arguments
+
+- `--auto` - Activate autonomous mode (**default**)
+- `--review` - Activate human-in-the-loop review mode
+- `--quick` - Activate quick mode
+- `--parallel` - Activate parallel mode: route to parallel `fullstack-developer` agents per issue
+
+## Workflow
+
+### Step 1: Mode Selection
+
+**First action:** If there is no "auto" keyword in the request, use `AskUserQuestion` to determine workflow mode:
+
+| Option | Recommend When | Behavior |
+|--------|----------------|----------|
+| **Autonomous** (default) | Simple/moderate issues | Auto-approve if score >= 9.5 & 0 critical |
+| **Human-in-the-loop Review** | Critical/production code | Pause for approval at each step |
+| **Quick** | Type errors, lint, trivial bugs | Fast debug → fix → review cycle |
+
+See `references/mode-selection.md` for AskUserQuestion format.
+
+### Step 2: Debug
+
+- Activate `debug` skill.
+- Guess all possible root causes.
+- Spawn multiple `Explore` subagents in parallel to verify each hypothesis.
+- Create report with all findings for the next step.
+
+### Step 3: Complexity Assessment & Fix Implementation
+
+Classify before routing. See `references/complexity-assessment.md`.
+
+| Level | Indicators | Workflow |
+|-------|------------|----------|
+| **Simple** | Single file, clear error, type/lint | `references/workflow-quick.md` |
+| **Moderate** | Multi-file, root cause unclear | `references/workflow-standard.md` |
+| **Complex** | System-wide, architecture impact | `references/workflow-deep.md` |
+| **Parallel** | 2+ independent issues OR `--parallel` flag | Parallel `fullstack-developer` agents |
+
+### Step 4: Fix Verification & Prevent Future Issues
+
+- Read and analyze all the implemented changes.
+- Spawn multiple `Explore` subagents to find possible related code for verification.
+- Make sure these fixes don't break other parts of the codebase.
+- Prevent future issues by adding comprehensive validation.
+
+### Step 5: Finalize (MANDATORY - never skip)
+
+1. Report summary: confidence score, changes, files
+2. `docs-manager` subagent → update `./docs` if changes warrant (NON-OPTIONAL)
+3. `TaskUpdate` → mark all Claude Tasks complete
+4. Ask user if they want to commit via `git-manager` subagent
+
+---
+
+## IMPORTANT: Skill/Subagent Activation Matrix
+
+See `references/skill-activation-matrix.md` for complete matrix.
+
+**Always activate:** `debug` (all workflows)
+**Conditional:** `problem-solving`, `sequential-thinking`, `brainstorm`, `context-engineering`
+**Subagents:** `debugger`, `researcher`, `planner`, `code-reviewer`, `tester`, `Bash`
+**Parallel:** Multiple `Explore` agents for scouting, `Bash` agents for verification
+
+## Output Format
+
+Unified step markers:
+```
+✓ Step 0: [Mode] selected - [Complexity] detected
+✓ Step 1: Root cause identified - [summary]
+✓ Step 2: Fix implemented - [N] files changed
+✓ Step 3: Tests [X/X passed]
+✓ Step 4: Review [score]/10 - [status]
+✓ Step 5: Complete - [action taken]
+```
+
+## References
+
+Load as needed:
+- `references/mode-selection.md` - AskUserQuestion format for mode
+- `references/complexity-assessment.md` - Classification criteria
+- `references/workflow-quick.md` - Quick: debug → fix → review
+- `references/workflow-standard.md` - Standard: full pipeline
+- `references/workflow-deep.md` - Deep: research + brainstorm + plan
+- `references/review-cycle.md` - Review logic (autonomous vs HITL)
+- `references/skill-activation-matrix.md` - When to activate each skill
+- `references/parallel-exploration.md` - Parallel Explore/Bash subagents patterns
+
+**Specialized Workflows:**
+- `references/workflow-ci.md` - GitHub Actions/CI failures
+- `references/workflow-logs.md` - Application log analysis
+- `references/workflow-test.md` - Test suite failures
+- `references/workflow-types.md` - TypeScript type errors
+- `references/workflow-ui.md` - Visual/UI issues (requires design skills)

package/.claude/skills/fix/references/complexity-assessment.md

@@ -0,0 +1,64 @@
+# Complexity Assessment
+
+Classify issue complexity before routing to workflow.
+
+## Classification Criteria
+
+### Simple (→ workflow-quick.md)
+
+**Indicators:**
+- Single file affected
+- Clear error message (type error, syntax, lint)
+- Keywords: `type`, `typescript`, `tsc`, `lint`, `eslint`, `syntax`
+- Obvious fix location
+- No investigation needed
+
+**Examples:**
+- "Fix type error in auth.ts"
+- "ESLint errors after upgrade"
+- "Syntax error in config file"
+
+### Moderate (→ workflow-standard.md)
+
+**Indicators:**
+- 2-5 files affected
+- Root cause unclear but localized
+- Needs debugging investigation
+- Keywords: `bug`, `broken`, `not working`, `fails sometimes`
+- Test failures with unclear cause
+
+**Examples:**
+- "Login sometimes fails"
+- "API returns wrong data"
+- "Component not rendering correctly"
+
+### Complex (→ workflow-deep.md)
+
+**Indicators:**
+- System-wide impact (5+ files)
+- Architecture decision needed
+- Research required for solution
+- Keywords: `architecture`, `refactor`, `system-wide`, `design issue`
+- Performance/security vulnerabilities
+- Multiple interacting components
+
+**Examples:**
+- "Memory leak in production"
+- "Database deadlocks under load"
+- "Security vulnerability in auth flow"
+
+### Parallel (→ multiple fullstack-developer agents)
+
+**Triggers:**
+- `--parallel` flag explicitly passed (activate parallel routing regardless of auto-classification)
+
+**Indicators:**
+- 2+ independent issues mentioned
+- Issues in different areas (frontend + backend, auth + payments)
+- No dependencies between issues
+- Keywords: list of issues, "and", "also", multiple error types
+
+**Examples:**
+- "Fix type errors AND update UI styling"
+- "Auth bug + payment integration issue"
+- "3 different test failures in unrelated modules"

package/.claude/skills/fix/references/mode-selection.md

@@ -0,0 +1,46 @@
+# Mode Selection
+
+Use `AskUserQuestion` at start of fixing workflow.
+
+## AskUserQuestion Format
+
+```json
+{
+  "questions": [{
+    "question": "How should I handle the fix workflow?",
+    "header": "Fix Mode",
+    "options": [
+      {
+        "label": "Autonomous (Recommended)",
+        "description": "Auto-approve if quality high, only ask when stuck"
+      },
+      {
+        "label": "Human-in-the-loop",
+        "description": "Pause for approval at each major step"
+      },
+      {
+        "label": "Quick fix",
+        "description": "Fast debug-fix-review cycle for simple issues"
+      }
+    ],
+    "multiSelect": false
+  }]
+}
+```
+
+## Mode Recommendations
+
+| Issue Type | Recommended Mode |
+|------------|------------------|
+| Type errors, lint errors | Quick |
+| Single file bugs | Quick or Autonomous |
+| Multi-file, unclear root cause | Autonomous |
+| Production/critical code | Human-in-the-loop |
+| System-wide/architecture | Human-in-the-loop |
+| Security vulnerabilities | Human-in-the-loop |
+
+## Skip Mode Selection When
+
+- Issue is clearly trivial (type error keyword detected) → default Quick
+- User explicitly specified mode in prompt
+- Previous context already established mode

package/.claude/skills/fix/references/parallel-exploration.md

@@ -0,0 +1,77 @@
+# Parallel Exploration
+
+Patterns for launching multiple subagents in parallel to scout codebase and verify implementation.
+
+## Parallel Exploration (Scouting)
+
+Launch multiple `Explore` subagents simultaneously when needing to find:
+- Related files across different areas
+- Similar implementations/patterns
+- Dependencies and usage
+
+**Pattern:**
+```
+Task(subagent_type="Explore", prompt="Find [X] in [area1]", description="Scout area1")
+Task(subagent_type="Explore", prompt="Find [Y] in [area2]", description="Scout area2")
+Task(subagent_type="Explore", prompt="Find [Z] in [area3]", description="Scout area3")
+```
+
+**Example - Multi-area scouting:**
+```
+// Launch in SINGLE message with multiple Task calls:
+Task("Explore", "Find auth-related files in src/", "Scout auth")
+Task("Explore", "Find API routes handling users", "Scout API")
+Task("Explore", "Find test files for auth module", "Scout tests")
+```
+
+## Parallel Verification (Bash)
+
+Launch multiple `Bash` subagents to verify implementation from different angles.
+
+**Pattern:**
+```
+Task(subagent_type="Bash", prompt="Run [command1]", description="Verify X")
+Task(subagent_type="Bash", prompt="Run [command2]", description="Verify Y")
+```
+
+**Example - Multi-verification:**
+```
+// Launch in SINGLE message:
+Task("Bash", "Run typecheck: bun run typecheck", "Verify types")
+Task("Bash", "Run lint: bun run lint", "Verify lint")
+Task("Bash", "Run build: bun run build", "Verify build")
+```
+
+## When to Use Parallel
+
+| Scenario | Parallel Strategy |
+|----------|-------------------|
+| Root cause unclear, multiple suspects | 2-3 Explore agents on different areas |
+| Multi-module fix | Explore each module in parallel |
+| After implementation | Bash agents for typecheck + lint + build |
+| Before commit | Bash agents for test + build + lint |
+
+## Combining Explore + Bash
+
+**Step 1:** Parallel Explore to scout
+**Step 2:** Sequential implementation
+**Step 3:** Parallel Bash to verify
+
+```
+// Scout phase - parallel
+Task("Explore", "Find payment handlers", "Scout payments")
+Task("Explore", "Find order processors", "Scout orders")
+
+// Wait for results, implement fix
+
+// Verify phase - parallel
+Task("Bash", "Run tests: bun test", "Run tests")
+Task("Bash", "Run typecheck", "Check types")
+Task("Bash", "Run build", "Verify build")
+```
+
+## Resource Limits
+
+- Max 3 parallel agents recommended (system resources)
+- Each subagent has 200K token context limit
+- Keep prompts concise to avoid context bloat

package/.claude/skills/fix/references/review-cycle.md

@@ -0,0 +1,77 @@
+# Review Cycle
+
+Mode-aware review handling for code-reviewer results.
+
+## Autonomous Mode
+
+```
+cycle = 0
+LOOP:
+  1. Run code-reviewer → score, critical_count, warnings, suggestions
+
+  2. IF score >= 9.5 AND critical_count == 0:
+     → Output: "✓ Review [score]/10 - Auto-approved"
+     → PROCEED to next step
+
+  3. ELSE IF critical_count > 0 AND cycle < 3:
+     → Output: "⚙ Auto-fixing [N] critical issues (cycle [cycle+1]/3)"
+     → Fix critical issues
+     → Re-run tests
+     → cycle++, GOTO LOOP
+
+  4. ELSE IF cycle >= 3:
+     → ESCALATE to user via AskUserQuestion
+     → Display findings
+     → Options: "Fix manually" / "Approve anyway" / "Abort"
+
+  5. ELSE (score < 9.5, no critical):
+     → Output: "✓ Review [score]/10 - Approved with [N] warnings"
+     → PROCEED (warnings logged, not blocking)
+```
+
+## Human-in-the-Loop Mode
+
+```
+ALWAYS:
+  1. Run code-reviewer → score, critical_count, warnings, suggestions
+
+  2. Display findings:
+     ┌─────────────────────────────────────┐
+     │ Review: [score]/10                  │
+     ├─────────────────────────────────────┤
+     │ Critical ([N]): [list]              │
+     │ Warnings ([N]): [list]              │
+     │ Suggestions ([N]): [list]           │
+     └─────────────────────────────────────┘
+
+  3. Use AskUserQuestion:
+     IF critical_count > 0:
+       - "Fix critical issues"
+       - "Fix all issues"
+       - "Approve anyway"
+       - "Abort"
+     ELSE:
+       - "Approve"
+       - "Fix warnings/suggestions"
+       - "Abort"
+
+  4. Handle response:
+     - Fix → implement, re-test, re-review (max 3 cycles)
+     - Approve → proceed
+     - Abort → stop workflow
+```
+
+## Quick Mode Review
+
+Uses same logic as Autonomous but:
+- Lower threshold: score >= 8.5 acceptable
+- Only 1 auto-fix cycle before escalate
+- Focus on: correctness, security, no regressions
+
+## Critical Issues (Always Block)
+
+- Security vulnerabilities (XSS, SQL injection, OWASP)
+- Performance bottlenecks (O(n²) when O(n) possible)
+- Architectural violations
+- Data loss risks
+- Breaking changes without migration

package/.claude/skills/fix/references/skill-activation-matrix.md

@@ -0,0 +1,65 @@
+# Skill Activation Matrix
+
+When to activate each skill during fixing workflows.
+
+## Always Activate
+
+| Skill | Reason |
+|-------|--------|
+| `debug` | Core to all fix workflows - find root cause first |
+
+## Conditional Activation
+
+| Skill | Activate When |
+|-------|---------------|
+| `problem-solving` | Stuck on approach, multiple failed attempts |
+| `sequential-thinking` | Complex logic chain, multi-step reasoning needed |
+| `brainstorm` | Multiple valid approaches, architecture decision |
+| `context-engineering` | Fixing AI/LLM/agent code, context window issues |
+| `ai-multimodal` | UI issues, screenshots provided, visual bugs |
+
+## Subagent Usage
+
+| Subagent | Activate When |
+|----------|---------------|
+| `debugger` | Root cause unclear, need deep investigation |
+| `Explore` (parallel) | Scout multiple areas simultaneously |
+| `Bash` (parallel) | Verify implementation (typecheck, lint, build) |
+| `researcher` | External docs needed, latest best practices |
+| `planner` | Complex fix needs breakdown, multiple phases |
+| `tester` | After implementation, verify fix works |
+| `code-reviewer` | After fix, verify quality and security |
+| `git-manager` | After approval, commit changes |
+| `docs-manager` | API/behavior changes need doc updates |
+| `project-manager` | Major fix impacts roadmap/plan status |
+
+## Parallel Patterns
+
+See `references/parallel-exploration.md` for detailed patterns.
+
+| When | Parallel Strategy |
+|------|-------------------|
+| Root cause unclear | 2-3 `Explore` agents on different areas |
+| Multi-module fix | `Explore` each module in parallel |
+| After implementation | `Bash` agents: typecheck + lint + build |
+| Before commit | `Bash` agents: test + build + lint |
+
+## Workflow → Skills Map
+
+| Workflow | Skills Activated |
+|----------|------------------|
+| Quick | `debug`, `code-reviewer`, parallel `Bash` verification |
+| Standard | Above + `problem-solving`, `sequential-thinking`, `tester`, parallel `Explore` |
+| Deep | All above + `brainstorming`, `context-engineering`, `researcher`, `planner` |
+| Parallel | Per-issue workflow + coordination via parallel agents |
+
+## Detection Triggers
+
+| Keyword/Pattern | Skill to Consider |
+|-----------------|-------------------|
+| "AI", "LLM", "agent", "context" | `context-engineering` |
+| "stuck", "tried everything" | `problem-solving` |
+| "complex", "multi-step" | `sequential-thinking` |
+| "which approach", "options" | `brainstorm` |
+| "latest docs", "best practice" | `researcher` subagent |
+| Screenshot attached | `ai-multimodal` |

package/.claude/skills/fix/references/workflow-ci.md

@@ -0,0 +1,28 @@
+# CI/CD Fix Workflow
+
+For GitHub Actions failures and CI/CD pipeline issues.
+
+## Prerequisites
+- `gh` CLI installed and authorized
+- GitHub Actions URL or run ID
+
+## Workflow
+
+1. **Fetch logs** with `debugger` agent:
+   ```bash
+   gh run view <run-id> --log-failed
+   gh run view <run-id> --log
+   ```
+
+2. **Analyze** root cause from logs
+
+3. **Implement fix** based on analysis
+
+4. **Test locally** with `tester` agent before pushing
+
+5. **Iterate** if tests fail, repeat from step 3
+
+## Notes
+- If `gh` unavailable, instruct user to install: `gh auth login`
+- Check both failed step and preceding steps for context
+- Common issues: env vars, dependencies, permissions, timeouts

package/.claude/skills/fix/references/workflow-deep.md

@@ -0,0 +1,91 @@
+# Deep Workflow
+
+Full pipeline with research, brainstorming, and planning for complex issues.
+
+## Steps
+
+### Step 1: Debug & Parallel Investigation
+Activate `debug` skill. Launch 2-3 `Explore` subagents in parallel:
+```
+Task("Explore", "Find error origin", "Trace error")
+Task("Explore", "Find affected components", "Map deps")
+Task("Explore", "Find similar patterns", "Find patterns")
+```
+See `references/parallel-exploration.md` for patterns.
+
+**Output:** `✓ Step 1: Root cause - [summary], system impact: [scope]`
+
+### Step 2: Research
+Use `researcher` subagent for external knowledge.
+
+- Search latest docs, best practices
+- Find similar issues/solutions
+- Gather security advisories if relevant
+
+**Output:** `✓ Step 2: Research complete - [key findings]`
+
+### Step 3: Brainstorm
+Activate `brainstorm` skill.
+
+- Evaluate multiple approaches
+- Consider trade-offs
+- Get user input on preferred direction
+
+**Output:** `✓ Step 3: Approach selected - [chosen approach]`
+
+### Step 4: Plan
+Use `planner` subagent to create implementation plan.
+
+- Break down into phases
+- Identify dependencies
+- Define success criteria
+
+**Output:** `✓ Step 4: Plan created - [N] phases`
+
+### Step 5: Implement
+Implement per plan. Use `context-engineering`, `sequential-thinking`, `problem-solving`.
+
+**Parallel Verification:** Launch `Bash` agents: typecheck + lint + build
+See `references/parallel-exploration.md`
+
+**Output:** `✓ Step 5: Implemented - [N] files, [M] phases, verified`
+
+### Step 6: Test
+Use `tester` subagent.
+
+- Comprehensive testing
+- Edge cases, security, performance
+- If fail → debug, fix, repeat
+
+**Output:** `✓ Step 6: Tests [X/X passed]`
+
+### Step 7: Review
+Use `code-reviewer` subagent.
+
+See `references/review-cycle.md` for mode-specific handling.
+
+**Output:** `✓ Step 7: Review [score]/10 - [status]`
+
+### Step 8: Finalize
+- Use `project-manager` subagent to update roadmap
+- Use `docs-manager` subagent for documentation
+- Use `git-manager` subagent for commit
+
+**Output:** `✓ Step 8: Complete - [actions taken]`
+
+## Skills/Subagents Activated
+
+| Step | Skills/Subagents |
+|------|------------------|
+| 1 | `debug`, parallel `Explore` subagents for investigation |
+| 2 | `researcher` |
+| 3 | `brainstorm` |
+| 4 | `planner` |
+| 5 | `problem-solving`, `sequential-thinking`, `context-engineering`, parallel `Bash` |
+| 6 | `tester` |
+| 7 | `code-reviewer` |
+| 8 | `project-manager`, `docs-manager`, `Bash` |
+
+**Rules:** Don't skip steps. Validate before proceeding. One phase at a time.
+**Frontend:** Use `chrome`, `chrome-devtools` or any relevant skills/tools to verify. 
+**Visual Assets:** Use `ai-multimodal` for visual assets generation, analysis and verification.

package/.claude/skills/fix/references/workflow-logs.md

@@ -0,0 +1,36 @@
+# Log Analysis Fix Workflow
+
+For fixing issues from application logs.
+
+## Prerequisites
+- Log file at `./logs.txt` or similar
+
+## Setup (if logs missing)
+
+Add permanent log piping to project config:
+- **Bash/Unix**: `command 2>&1 | tee logs.txt`
+- **PowerShell**: `command *>&1 | Tee-Object logs.txt`
+
+## Workflow
+
+1. **Read logs** with `Grep` (use `head_limit: 30` initially)
+   - Increase limit if insufficient context
+
+2. **Analyze** with `debugger` agent for root causes
+
+3. **Scout** codebase with `scout` agent for issue locations
+
+4. **Plan** fix with `planner` agent
+
+5. **Implement** the fix
+
+6. **Test** with `tester` agent
+
+7. **Review** with `code-reviewer` agent
+
+8. **Iterate** if issues remain, repeat from step 3
+
+## Tips
+- Focus on last N lines first (most recent errors)
+- Look for stack traces, error codes, timestamps
+- Check for patterns/repeated errors

package/.claude/skills/fix/references/workflow-quick.md

@@ -0,0 +1,59 @@
+# Quick Workflow
+
+Fast debug-fix-review cycle for simple issues.
+
+## Steps
+
+### Step 1: Debug
+Activate `debug` skill. Find root cause quickly. Verify the root cause with multiple `Explore` subagents in parallel.
+- Read error message/logs
+- Locate affected file(s)
+- Identify exact fix needed
+
+**Output:** `✓ Step 1: Root cause - [brief description]`
+
+### Step 2: Fix & Verify
+Implement the fix directly.
+- Make minimal changes
+- Follow existing patterns
+
+**Parallel Verification:**
+Launch `Bash` agents in parallel:
+```
+Task("Bash", "Run typecheck", "Verify types")
+Task("Bash", "Run lint", "Verify lint")
+```
+
+See `references/parallel-exploration.md` for patterns.
+
+**Output:** `✓ Step 2: Fixed - [N] files, verified (types/lint passed)`
+
+### Step 3: Verify
+Use `code-reviewer` subagent for quick review.
+
+Prompt: "Quick review of fix for [issue]. Check: correctness, security, no regressions. Score X/10."
+
+**Review handling:** See `references/review-cycle.md`
+
+**Output:** `✓ Step 3: Review [score]/10 - [status]`
+
+### Step 4: Complete
+Report summary to user.
+
+**If autonomous mode:** Ask to commit via `git-manager` subagent if score >= 9.0
+**If HITL mode:** Ask user next action
+
+**Output:** `✓ Step 4: Complete - [action]`
+
+## Skills/Subagents Activated
+
+- `debug` - Always (Step 1)
+- Parallel `git-manager` - Verification (Step 2)
+- `code-reviewer` subagent - Always (Step 3)
+- `context-engineering` - If dealing with AI/LLM code
+
+## Notes
+
+- Skip if review fails → escalate to Standard workflow
+- Total steps: 4 (vs 5-6 in Standard/Deep)
+- No planning phase needed