The VaultClaude Code Setup Kit

Premium kit · 11 items · all tested

Always one safe step from a project that works.

You can't read every line Claude writes. You don't have to.

Memory, fences, save points. One afternoon of setup, and Claude Code stops guessing.

01Sessions open with a plan you approve.

02The files that scare you need permission.

03A broken afternoon becomes ten minutes.

Get it — pay what you want

Already bought? Redeem your key →Already bought? Log in →

All testedFree updatesSecure checkout

CLAUDE.md

# CLAUDE.md

## What we're building

## House rules

## When unsure, ask

checkpoint saved

The system

Three parts. That's the whole idea.

Pick a part. See a session today, then the same session with the kit in.

Memory · CLAUDE.md Architect

Every session today

Starting from zero, again

You paste the same context back in. Claude guesses at the rest, then drifts from what you asked. By the third session you're explaining your own project to a tool that should already know it.

What the kit installs

/new

Build the file

Any stack — web app, backend, mobile, game and more.

/audit

Check the one you have

Finds what is missing and what quietly causes drift.

/upgrade

Keep it current

The memory grows with the project instead of going stale.

The guessing stops. So does the drift.

Free · no purchase needed

Get your CLAUDE.md written today.

One question in, a working memory file out — it decides the technical choices for you. There's a fill-in template too, if you'd rather not use AI for it at all.

Both free starters

claude-md.promptFree · tested

Write my first CLAUDE.md.

Ask me ONE question: in plain English, what am I building?

MY ANSWER: {{describe your project in a sentence}}

Then do the rest yourself:
1. Pick a sensible stack and say why in one line. If I already have one, use {{stack, or skip}}.
2. Write the file with these sections: What we are building, House rules, Files you must not touch, When unsure ask.
3. Add three house rules that stop the most common damage for this kind of project.
4. Explain anything technical in one short line. "You decide" is always a valid answer from me.
5. Return the finished file only, ready to save at my repo root as CLAUDE.md.

Open in

Claude ChatGPT Gemini

The paid heart

Two skills. Six commands.

Install them as Claude skills and they do the work. No install? Six standalone prompts cover the same system in any Claude chat.

Installable skill

CLAUDE.md Architect

Builds, audits and upgrades your project-memory file for any stack — carrying guardrail profiles distilled from blueprints run on real projects.

/newWrite the file for your stack, start to finish.

/auditCheck the file you have and fix what drifts.

/upgradeKeep the memory current as the project grows.

Installable skill

Project Guardian

Runs your sessions safely: context-first starts, protected files that need permission, checkpoints, and calm recovery when something breaks.

/kickoffOpen with full context and a plan you approve.

/guardFence the scary files, drop a save point.

/recoverWalk back to known-good in plain English.

What you get

Eleven items. Nothing to configure.

Two skills, six prompts, two free starters, one guide. Every one written in plain English — "you decide" is a valid answer everywhere.

Skill

CLAUDE.md Architect

Build, audit, upgrade — profiles for any stack.

Skill

Project Guardian

Safe starts, protected files, checkpoints, recovery.

Prompt

CLAUDE.md for any stack

The Architect job as one pasteable prompt.

Prompt

Audit the file you have

Finds the gaps that quietly cause drift.

Prompt

Guardrails writer

Decides what gets fenced and what needs permission.

Prompt

Calm recovery walkthrough

Broken app back to known-good, step by step.

Prompt

Session kickoff

Thirty seconds of context before any work starts.

Guide

Which tool, when

The operating manual behind the whole system.

Free

Two starters

One question in, a working CLAUDE.md out. Or fill in the blanks.

04 · Why I made it

I build with Claude Code every day. This is my own setup.

The Architect's stack profiles come from blueprint files run on real projects before they were distilled into a skill. If it didn't hold up, it didn't ship.

— Maurice

→No re-explaining your project.

→No silent rewrites of working files.

→The first recovery pays for the kit.

The full list

Every prompt in the kit

2 free · 6 in the kit

#077

Set up Claude Code the right way

The system behind the kit: memory, fences, save points, and when to use each.

In the kit

#076

Start every session with full context

Thirty seconds of kickoff that ends the start-from-zero tax.

In the kit

#075

Recover when Claude breaks your app

Calm, step-by-step rollback in plain English.

In the kit

#074

Generate a CLAUDE.md for any stack

Guardrail profiles for web, backend, mobile, games and more.

In the kit

#073

Audit and upgrade the file you have

Finds what is missing and what is causing drift.

In the kit

For you if

You're the founder, not the engineer

Solo founders and makers shipping real products with Claude Code and no developer on call. You'd rather ship than babysit diffs.

Not for you if

You already have git discipline

If you're a working engineer with your own dotfiles and habits, you own most of this already. Keep your money.

Where it sits

A standalone kit

One pack, $17. All 7, $119. The Vault is $49, once — all of them, plus every pack I add next.

The offer

Cheaper than one broken afternoon.

Pay what you want, suggested $17. One-time, and the kit keeps growing.

→ 11 items, all tested

→ Future additions included free

→ 30-day refund, just email me

Get it — pay what you want

Secure via Gumroad · license key by email

Already bought? Redeem your key or log in.

Already bought?

Didn’t get access? Redeem your license key

FAQ

Anything else?

No. Every tool in the kit speaks plain English, picks sensible defaults for you, and explains anything technical in a line. "You decide" is a valid answer everywhere.

Still stuck? Email me →

Claude Code Setup KitGet it — pay what you want