VSA + SOLID · .NET/Blazor · Next.js · Claude Code + Cursor

The Dev Loop

A small set of skills that make you the orchestrator: you point the skills, decide at the forks, and keep the board honest. Every skill reads its per-repo settings from one config file, so the same skill body runs across every project — and across both Claude Code and Cursor.

/start-featureimplement in the slicecrucible reviewrefactor/finish-featurePR / Done

🗺️ Flows

The interactive map. Light up any path — happy path, review↔refactor loop, consult forks, bug-mid-work, blocked, verifying, epic fan-out, night shift.

Open the map →

🧰 Skills

The seven instruments, read live from their SKILL.md files — what each does, its trigger, invocation, and full version history.

See the toolset →

⚙️ Setup

Install once at the user level; add one config file per repo. Platform toggle for Claude Code vs Cursor install paths and frontmatter.

Set up a project →
One body, two tools. Cursor and Claude Code both speak the SKILL.md standard, so each skill is authored once. The shared fields — name, description, disable-model-invocation — behave identically in both; Claude Code's extra fields are additive and harmlessly ignored by Cursor. The only per-project variation lives in each repo's GITHUB-PROJECTS.md.
The board (GitHub Projects) is the one shared state every skill reports into. Instruments: /start-feature · crucible-blazor · crucible-nextjs · /finish-feature · /update-docs · /history · night-shift.