You type.The kit doesthe rest.

Agent skills, optional MCP tools, and layered coding standards for AI-assisted development.

Step 1 · You

It starts with your words

youAdd a dark-mode toggle to the header

You ask for a change in plain language. The prompt goes straight to Claude, and everything the kit does happens around it.

Step 2 · Claude

Skills load themselves

The agent reads each skill's short description and loads the skill when the situation matches.

  • plan-first
  • pre-merge-gate
  • pre-commit
  • debug-protocol

Step 3 · Claude

Rules it reads before it writes

An agent reads the layers top down for every file it edits. Framework rules extend or override the universal ones.

  • css
  • html
  • javascript
  • typescript
  • git
  • versioning
  • seo
  • performance

Step 4 · Automatic

Hooks guard every move

Mods run in code, so unlike skills they fire every time. precommit-gate gates git commit and git push.

  • guard
  • standards-chain
  • edit-check
  • precommit-gate
  • output-compact
  • debug-nudge

Your side · You

Commands are yours

Slash commands you type to run a kit action.

  • /kit
  • /next
  • /wrap-up
  • /pickup
  • /audit

The whole kit

One map, four kinds of actor

  • YouCommands, the README and the docs. You type or read them.
  • ClaudeSkills and standards. Claude loads them by matching descriptions.
  • AutomaticMods and their scripts. They fire on tool calls and nobody asks.
  • MaintainersTests and audit write-ups. Never part of a prompt.

Every file in the kit belongs to you, to Claude, to the hooks, or to the people who maintain it.

Go deeper

Browse the modules

Each part of the kit has its own page. Start with the one you need.