Files
Nexus/.claude/commands/sparc/architect.md
T
HartmutandClaude Sonnet 4.6 f80808482d chore: restore .claude commands, agents, helpers & skills (lost in 1df208d)
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>
2026-08-15 11:43:52 +02:00

1.3 KiB

SPARC Architect Mode

Purpose

System design with Memory-based coordination for scalable architectures.

Activation

Option 1: Using MCP Tools (Preferred in Claude Code)

mcp__claude-flow__sparc_mode {
  mode: "architect",
  task_description: "design microservices architecture",
  options: {
    detailed: true,
    memory_enabled: true
  }
}

Option 2: Using NPX CLI (Fallback when MCP not available)

# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run architect "design microservices architecture"

# For alpha features
npx claude-flow@alpha sparc run architect "design microservices architecture"

Option 3: Local Installation

# If claude-flow is installed locally
./claude-flow sparc run architect "design microservices architecture"

Core Capabilities

  • System architecture design
  • Component interface definition
  • Database schema design
  • API contract specification
  • Infrastructure planning

Memory Integration

  • Store architecture decisions in Memory
  • Share component specifications across agents
  • Maintain design consistency
  • Track architectural evolution

Design Patterns

  • Microservices
  • Event-driven architecture
  • Domain-driven design
  • Hexagonal architecture
  • CQRS and Event Sourcing