The free Build Kit

Answer five questions. Get your kit.

This is the setup we start every project with — the brief, the playbooks, the connections. Answer five short questions and it's yours to download and make your own. Built right here in your browser: no account, no API key, nothing stored.

Make your kit See what's inside

What's inside

CLAUDE.md

The brief

What it is, who it's for, and the rules Claude can't skip — starting with the big one: only real facts, never invented. It reads this first, every time, so you stop re-explaining yourself.

Seven skills

The playbooks

plan · brand · design · humanize · marketing · orchestrate · ship. Reusable playbooks — your standards written once and followed every time. Keep the ones you need, delete the rest.

.mcp.json + checklist

The hands

The wiring that lets Claude read your files, the web, or your repo. A two-connection starter and a safety checklist: connect only what a task needs, one at a time. You keep the final call.

README + resources

The start

Three steps to begin and where to go next. No lock-in, no highlight reel — the exact system, yours to change.

Five questions

Make your kit

Fill these in and your kit downloads as a .zip. Your answers become your CLAUDE.md and never leave this page.

Project nameWhat is it?Who's it for?Your rules / tasteYour stack / toolsoptional

Built in your browser. No account, no upload, nothing stored.

Your CLAUDE.md, so far

# Your Project

## What this is
A project I'm building with Claude.

## Who it's for
(add who this is for)

## The goal right now
Ship a first working version.

## How to work with me
- One task at a time. Show me the plan before any big change.
- Ask before deleting or overwriting anything you didn't create.
- Match the voice and taste below. Never use fake or placeholder data.
- When you're unsure, ask — don't guess. I keep the final call.

## Rules & taste
Be clear and honest. Never invent facts. Ask before any big change.

## Stack / tools
Not specified yet.

## Definition of done
- It matches the goal above and the rules here.
- I've reviewed it. Nothing ships without my sign-off.

Your .zip includes

CLAUDE.md — filled from your answers
skills/ — all seven playbooks
.mcp.json + MCP-CHECKLIST.md
README.md + RESOURCES.md

Install it

Running in three steps

It's just files — no installer, no lock-in. Here's the whole thing.

Unzip your kit

You get CLAUDE.md, a skills/ folder, a starter .mcp.json, and two short guides (README, RESOURCES).

your-project/

CLAUDE.md· the brief
skills/· 7 playbooks
.mcp.json· connections
README.md· start here
RESOURCES.md· where next

Add the brief

Drop CLAUDE.md at the root of your project — or paste it into a Claude Project's instructions. Claude reads it first, every time, so you stop re-explaining yourself.

Claude · Project instructions

Paste your CLAUDE.md here

# Your Project

## How to work with me

- Match the voice and taste below.

- Never use fake or placeholder data.

- I keep the final call.

Bring in the playbooks & hands

Keep the skills you'll use. When a task needs one, tell Claude "follow skills/brand.md." Add .mcp.json when you want Claude to touch real files or the web — one connection at a time (see MCP-CHECKLIST.md).

CLAUDE.md

## The goal right now

Ship a first working version.

## Rules & tasteedit this

Sober and factual. Mobile-first.

Never invent a fact.

## Stack / tools

Next.js, Tailwind, Supabase

What to edit

Make it yours

CLAUDE.mdYour rules and your "never" lines. The generator filled these from your answers — refine them any time.

skills/Open one, tweak it to your craft, delete the ones you won't use. They're plain markdown.

.mcp.jsonStart with one connection, confirm it works, then add more. Connect only what a task needs.

Honest note

This is a v1 on purpose: it generates and downloads, nothing fancier. There's no AI call and no account — just templates filled with your words. From here, /build becomes the working floor, where real builds get documented in the open.

Build with AI. Keep the hand.

The kit does the setup. You keep the taste and the final call. Work in a loop — brief, build, review, ship — and let the system carry the parts that used to be busywork.

Nornic Labs