FOR DEVELOPERS

Developers

The software profile is the deep end of the kit. It gives a project a full engineering org, each role carrying the right tools for its lane, and a tidy workflow from issue to merged PR.

Your team

Run /kit-init and pick software:

Role	Owns	Tools it carries
tech-lead	Build system, toolchain, ADRs, CI/CD, scaffolding	Context7, GitHub navigator
backend	API, data model, schema, jobs, realtime, auth	claude-api, Context7
frontend	All client UI, app shell, client UX, animation	claude-api, GSAP, Chrome DevTools, Context7
qa	E2E tests, acceptance, regression, the release gate	Playwright, Chrome DevTools
security	Threat modeling, vuln audits, injection defense, deps	claude-api
devops	Infra, CI/CD pipelines, deploy, release, migrations	Context7, GitHub navigator
designer	Design system, screens, motion, UX	design + GSAP skills
pm	Work state through GitHub; issues, plans, blockers	task workflow skills

Roles defer across boundaries — backend hands UI work to frontend, infra to devops — instead of guessing outside their lane. See Agents & orchestration for the routing model.

Build skills that switch on by themselves

Some skills are stack-gated: they activate only when their technology is detected in your package.json, and stay out of the way otherwise.

Skill	Activates when	Covers
feature-build-refine	@refinedev/* present	Next.js + Supabase + RefineDev architecture
supabase-patterns	@supabase/supabase-js present	Three-client model, server-action auth guard, RLS-first access

If the tech isn't in your stack, the skill simply doesn't apply. And karpathy-guidelines — guardrails against common LLM coding pitfalls — rides along in every profile.

The workflow

The kit assumes a clean path through GitHub: issue → branch → PR → merge → close, with optional Projects v2 board sync. Skills like task-new, task-start, task-pr, and task-close drive each step. Milestones follow a product cadence: Foundation → MVP → Beta → GA.

Opt-in gates and SDD

These stay off until you choose them:

• Pre-push gate — --prepush "<command>" runs a command (e.g. your build) before every git push and blocks the push if it fails. Self-passing: it only acts on git push.
• Spec-Driven Development — --speckit on installs or identifies Spec Kit and drives specify → plan → tasks → implement with review gates.

See Rules & hooks for how these are wired.

Where to go next

• Install — get set up, then /kit-init → software.
• Profiles & configuration — every setting, mapped.
• Commands & scripts — the full command reference.