v0.3.0 — Cursor support
The second harness: Spruce now installs into Cursor in addition to Claude Code. Same install command, same 25-command catalog, same slash invocation pattern (/decide, /typeface, /personas) — no mental-model translation between
harnesses.
Install in any project:
npx spruce-skill add
Auto-detects which AI coding tool the project uses (Claude Code, Cursor, or any harness following the Anthropic Agent Skills spec) and installs the right per-harness bundle. Wraps
vercel-labs/skills — the open agent-skills ecosystem — for the underlying installation work, plus a Claude Code slash-command copy when Claude Code is detected.
Same workflow in both:
In Claude Code, type /decide, /typeface, /personas, etc. as native slash commands. In Cursor, the same commands work via slash invocation against the matched skill — /decide matches the decide skill and follows its conversation
flow exactly. The catalog is identical in both places; only the underlying mechanism differs.
Architecture:
Spruce now ships as 25 self-contained skills, one per command. Each skill bundles its own SKILL.md, PHILOSOPHY.md, and full reference library — no cross-skill loading dependency, no custom orchestration layer. Per-harness paths
(.claude/skills/, .cursor/skills/, .agents/skills/) handled by vercel-labs/skills; same skill content works across every harness that supports the Agent Skills spec.
Source files (source/) are unchanged — the build script generates harness-specific output at the repo root. The dist/ directory is retired.
Preserved from v0.2.0:
- All 25 commands across 5 tiers (Setup, Discovery, Generative, Diagnostic, Corrective) work identically.
- Claude Code slash commands at
.claude/commands/still ship alongside the skills installation; the existing Claude Code slash UX is unchanged. - The 13 reference files (Discovery foundation + design dimensions) bundle into each skill so context-rich reasoning travels with every command.
- The
.spruce.mdcontext file remains the foundation every command reads from.
Coming next:
Native support for GitHub Copilot (VS Code), Codex CLI, and Gemini CLI follows the same per-harness pattern — each adds a directory to the build's harness coverage. See
ROADMAP.md for sequencing.