Inside the Developer Kit: 79 skills, one terminal command.

The Developer Kit ships 79 skills covering planning, implementation, review, testing, debugging, and a long tail of integration-specific helpers. Here's the tour.

The workflow trio

Three skills do the heavy lifting for most feature work:

• /build — end-to-end feature implementation. You describe the feature in plain English; /build scouts the codebase, drafts a plan, executes it, runs tests, and self-reviews.
• /scout — fast, read-only codebase exploration. Hand it a question ("where do we handle webhook retries?") and it returns the answer with file:line references, no code edits.
• /plan — pure planner. Takes a goal, returns a phased implementation plan in your ./plans directory. Hands it off to /build or to you.

Specialised sub-agents

The kit includes a dozen sub-agent definitions that /build picks from depending on what it sees: backend-developer, frontend-developer, code-reviewer, tester, debugger, docs-manager, journal-writer, project-manager, and more. You don't usually call these by hand — they're spawned automatically when needed.

Integration deep-dives

Where Developer Kit pays for itself is the long tail of stack-specific skills:

• Shopify — themes, GraphQL, custom apps, checkout extensibility.
• three.js + shader — 3D scene setup, GLSL fragment shaders, post-processing.
• Better Auth + payment-integration — auth flows + Stripe / Lemon Squeezy patterns.
• HeroUI (React / Native / Migration) — component-library deep knowledge.
• TanStack, Remotion, Mintlify, Mermaid v11 — each one a focused skill.
• chrome-devtools, mcp-builder, mcp-management — for when you're extending the agent itself.

Quality & ops

A second tier of skills keeps work shippable:

• code-review — runs the code-reviewer agent against your last change.
• security-scan — static-analysis prompts for common vulnerabilities.
• test + test-orchestrator — generate, run, and triage tests across stacks.
• fix — guided debugging for a specific error message or failing test.
• deploy, devops, git, worktree — release plumbing.

Thinking & process

The "soft" skills end up being some of the most used:

• brainstorm — structured idea-generation when you're stuck.
• sequential-thinking — breaks down ambiguous problems before code.
• problem-solving — root-cause analysis on production incidents.
• research, docs-seeker — fetch + summarise external docs without context-bleed.
• retro, journal — capture lessons after each build.

Why 79 and not 7

Each skill is a couple of hundred lines of focused prompt. They're cheap to load (only used when invoked) and expensive to skip (an agent that doesn't know about Shopify checkout extensions writes much worse Shopify code). At 79 skills the kit covers the 99% of stacks people actually ship.