Skip to main content

FOR EVERYONE

Tailor your team — /kit-customize

A profile is a starting point, not a cage. /kit-customize lets you reshape your team after setup — add a role you need, trim one you don't, give an agent a new skill, or save your own preset for next time.

It also activates on its own the moment you ask to create, edit, or delete an agent — so you usually don't even have to remember the command.

What you can do​

  • Add, edit, or delete an agent — start from a kit template or build a fresh custom one.
  • Wire skills and tools onto an agent — names are checked against what actually exists first, so nothing is invented or mistyped.
  • Find or suggest skills — describe a task and it searches for a skill that fits, then suggests it.
  • Lint your agents — checks frontmatter, tool and skill names, and flags any leftover template placeholders.
  • Build a custom profile — assemble your own preset (or start from one of the built-ins) and save it for reuse across projects.

A few examples​

"Add a data analyst to this content project."

It pulls the analyst template, wires the right skills, adds it to your team, and keeps kit.config.json and the CLAUDE.md table in sync.

"Give the frontend agent the Playwright skill."

It resolves the skill name, confirms it exists, and wires it on.

"Is there a skill for writing marketing copy?"

It searches and suggests copywriting, then offers to attach it.

It keeps everything consistent​

When you change the team, /kit-customize doesn't just edit one file and leave the rest stale. It keeps the roles list in your config, the CLAUDE.md table, and the agent files all pointing at the same reality — then lints the result so you don't ship a broken agent.

Made something good? Share it​

Built a role or skill worth reusing? /kit-contribute turns your project agent back into a clean template and opens a pull request upstream — so the next person gets it too.

How it works under the hood
  • Where it lives. /kit-customize is a skill that operates on a project already scaffolded by /kit-init (a .claude/ with a kit.config.json). Each agent is a file at .claude/agents/<name>/AGENT.md with a frontmatter contract: name, description, when_to_use, tools, skills.
  • Name resolution. Before wiring a skill or tool, the names are resolved against the real, available set — so an agent never ends up pointing at a tool that doesn't exist. The same check runs in the linter.
  • Custom profiles. A saved profile is written to ~/.claude/kit-profiles/ and can be selected in a later /kit-init like any built-in. It bundles whatever agent templates it needs.
  • Skill discovery. Searching for a skill uses the find-skills capability to match a task to an installable or available skill.

Where to go next​