Kit-Making Kit

When this helps

You want to make what you built usable by other people, but do not know what to prepare

What it does

Turns something you built — or are still building — into a kit other people can use. It leaves your original folder alone, works on a cleaned copy, strips keys, real data and contact endpoints, and assembles the instructions for AI (CLAUDE.md, plus AGENTS.md for Codex) along with the rules for how to work. It runs an automatic check and walks you all the way to submitting. The kit spec lives in kit-spec.json in a machine-readable form, so your own AI reads it and drives the process.

The fixes baked into this kit

1. "What did you do cleverly?" gets you nothingBecause the person does not think of it as clever. Ask "what tripped you up?" or "what happened the first time?" and it comes out. That difference is written into PROMPTS.md.
2. Cleaning the original folder destroys real dataYou clean a copy. Delete .git too — keys you thought you removed are still in the history.
3. Claude Code only reads CLAUDE.md; Codex only reads AGENTS.mdPut both doors in. Fix only one and behaviour changes depending on who uses it. The check looks for mismatches.
4. The check tool reacts to its own examplesThe same goes for prose explaining what is forbidden (%USERPROFILE% and friends). The tool skips itself, and downgrades hits inside prose to something a human looks at rather than a hard stop.
5. Works on the author's machine, breaks when shippedBecause it calls something that only exists locally. The flow makes you copy it to another folder and run it end to end there.
6. Forgetting to remove the contact endpointEvery enquiry from every user lands on the author. This actually happened. The check looks for form, Slack and Apps Script endpoints.

What's inside

• The kit spec (kit-spec.json — the source of truth your AI reads)
• How to turn something you already have into a kit
• How to build new things so they are easy to turn into kits
• Cleaning rules (keys, real data, photos, contact endpoints)
• How to write CLAUDE.md and rules
• How to ask so people tell you what actually went wrong
• The automatic pre-submission check (node tools/check.mjs)
• A full set of templates you can use as-is

The first three decisions

1. Converting something you have, or starting fresh
2. The kit's name, and what it does in one line
3. What changes per user (= the first three decisions)

What you need

• No extra costClaude Code or CodexEither works. Both CLAUDE.md and AGENTS.md are included.
• No extra costNode.jsTo run the check tool. Nothing else to install.
• No extra costSomething you have actually used for real work★This is the substance. Things that were only built never make it onto the shelf.

How to use

Just paste this into your AI.

I want to use the nice to have kit "Kit-Making Kit". Follow https://nicetohave.app/en/g/92QSB6TQ-•••••••••• and set it up.

Works the same in Claude Code or Codex. If you have Safe Rail (the guard that stops dangerous operations automatically), it fetches the kit for you.
Read what this tells your AI to do, before you paste it

FAQ

What does Kit-Making Kit do?

Turns something you built — or are still building — into a kit other people can use. It leaves your original folder alone, works on a cleaned copy, strips keys, real data and contact endpoints, and assembles the instructions for AI (CLAUDE.md, plus AGENTS.md for Codex) along with the rules for how to work. It runs an automatic check and walks you all the way to submitting. The kit spec lives in kit-spec.json in a machine-readable form, so your own AI reads it and drives the process.

Which AI tools does it work with?

Claude Code and Codex. Copy the one line on the kit page and paste it into your AI; it pulls in the kit and starts (copying needs a GitHub or Google sign-in).

Does it cost anything?

The kit is free. Nothing else in the kit costs extra. The AI tool itself is billed under your own plan.

How is this different from just asking an AI?

It already contains the fixes for pitfalls the maker hit in real work: ""What did you do cleverly?" gets you nothing", "Cleaning the original folder destroys real data", "Claude Code only reads CLAUDE.md; Codex only reads AGENTS.md", "The check tool reacts to its own examples", "Works on the author's machine, breaks when shipped", "Forgetting to remove the contact endpoint".

What do I decide first?

Three things: Converting something you have, or starting fresh; The kit's name, and what it does in one line; What changes per user (= the first three decisions). The AI asks them one at a time.

Does it handle personal data?

No.

Supporters

Once support opens, the people who backed this kit will be listed here.