Restores the entire .claude/ infrastructure that was accidentally deleted
in commit 1df208d ('feat(timeline): add pulse animation for in-flight drag
mutations'). Recovered via git checkout 1df208d^.
Restored:
- .claude/commands/ (gitlooper, sparc/, github/, automation/, monitoring/,
optimization/, hooks/, plan, implement, research, review, perf, visualaudit)
- .claude/agents/ (core/, github/, sparc/, v3/, swarm/, templates/, ...)
- .claude/helpers/ (41 scripts incl. hook-handler.cjs, statusline.cjs)
- .claude/skills/ (20 skills incl. sparc-methodology, github-*, v3-*)
- .claude/settings.json (hooks configuration)
Also updated all CapaKraken → Nexus references in affected command files.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
61 lines
1.1 KiB
Markdown
61 lines
1.1 KiB
Markdown
# SPARC Designer Mode
|
|
|
|
## Purpose
|
|
|
|
UI/UX design with Memory coordination for consistent experiences.
|
|
|
|
## Activation
|
|
|
|
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
|
|
|
```javascript
|
|
mcp__claude-flow__sparc_mode {
|
|
mode: "designer",
|
|
task_description: "create dashboard UI",
|
|
options: {
|
|
design_system: true,
|
|
responsive: true
|
|
}
|
|
}
|
|
```
|
|
|
|
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
|
|
|
```bash
|
|
# Use when running from terminal or MCP tools unavailable
|
|
npx claude-flow sparc run designer "create dashboard UI"
|
|
|
|
# For alpha features
|
|
npx claude-flow@alpha sparc run designer "create dashboard UI"
|
|
```
|
|
|
|
### Option 3: Local Installation
|
|
|
|
```bash
|
|
# If claude-flow is installed locally
|
|
./claude-flow sparc run designer "create dashboard UI"
|
|
```
|
|
|
|
## Core Capabilities
|
|
|
|
- Interface design
|
|
- Component architecture
|
|
- Design system creation
|
|
- Accessibility planning
|
|
- Responsive layouts
|
|
|
|
## Design Process
|
|
|
|
- User research insights
|
|
- Wireframe creation
|
|
- Component design
|
|
- Interaction patterns
|
|
- Design token management
|
|
|
|
## Memory Coordination
|
|
|
|
- Store design decisions
|
|
- Share component specs
|
|
- Maintain consistency
|
|
- Track design evolution
|