EN VI
Claude Code Project Wizard · v1

Generate the CLAUDE.md your Claude Code projects need.

A 30-second generator for the config bundle Claude Code reads at every session — architecture, conventions, security rules, decision log. Pre-filled for your stack. Reviewable. Free.

Configure your bundle → Why this exists
01Why this exists

Without a config bundle, every Claude session is a stranger on day one.

It re-asks the same questions. Reaches into the wrong files. Rewrites code that's intentionally that way. Three patterns we kept seeing — and what the bundle does about each.

PAIN 01
"Claude rewrote our auth flow because it didn't know it was load-bearing."
Bundle ships docs/decisions/0007-auth.md + a CLAUDE.md rule: auth flows are immutable without an ADR.
PAIN 02
"I keep re-explaining where the database layer lives. Every. Single. Session."
Bundle ships docs/ARCHITECTURE.md + path-scoped CLAUDE.md files in app/, lib/db/, so context loads automatically.
PAIN 03
"It ran rm on a folder I told it not to. Three times in one week."
Bundle ships a pre-tool hook that exits non-zero on dangerous paths, plus a tight permissions.json allow/ask/deny list.
The shape of the fix a typical CLAUDE.md, before and after the bundle runs
CLAUDE.md · session #001 +12 −5
3−You are a helpful coding assistant.
4−Be concise.
5
@@ -0,0 +1,12 @@ added by starter bundle @@
3+Project: my-app · Next.js 15 · pnpm · Node 20
4+Database: PostgreSQL via Drizzle
5+Port: 3000 · src/ layout: feature-first
6
7+## Rules
8+- Auth flows are immutable. Open an ADR before touching.
9+- Never drop DB tables without an explicit user instruction.
10+- Run `pnpm typecheck` before marking any task done.
11
12+## Architecture
13+See docs/ARCHITECTURE.md for system overview and conventions.
14+See docs/decisions/ for ADR log.
What you get back

Three things that change the day after you commit the bundle.

→ 0
re-explanations per session

Stack, layout, and red lines load automatically from path-scoped CLAUDE.md files. You stop being the human prompt.

→ ADR
every architectural decision

The why survives across sessions, members, and weeks. The same debate doesn't restart in next Tuesday's standup.

→ ✘
no more 3 a.m. rm

Hooks block the destructive commands before they run. Permissions narrow the blast radius. Hope is not a strategy.

02Generate your bundle

Pick your phase. Pick your stack. Download.

01

Setup level

each tier extends the previous
CollaborativeRECOMMENDED FOR TEAMS

For teams. Hooks block dangerous commands. ADR system logs every architectural decision so they survive across sessions, members, and weeks.

+ adds hooks, ADR system, custom slash commands on top of Equipped
~62 files
30m setup time
02

Stack

runtime & package manager auto-fill
▲ Next.js
03

Project

written into every file
04

What's in this phase

phase = bundle. nothing to toggle.
COLLABORATIVE Each phase ships a fixed set of components. Picking a phase is the choice — these aren't optional.
● inherited from previous phase ● new in this phase ○ only in higher phases
03FAQ

Common questions, briefly answered.

What is CLAUDE.md, exactly?

A file Claude Code reads at the start of every session. Not a README — an operating manual: stack, architecture, rules, conventions. Without it, Claude guesses. With it, Claude follows your team.

Which phase fits me?

Trying it out → Kickstart. Solo serious project → Equipped. Team of 2–5 → Collaborative (most teams stop here). Production with users → Battle-tested.

Will this overwrite my files?

No. The zip is reviewed by you. You copy what you want. If you already have a CLAUDE.md, open both and merge. Nothing is automatic.

Cursor / Copilot / other tools?

The CLAUDE.md and the docs work with any AI assistant that reads files. The hooks and .claude/settings.json are Claude Code-specific.