cc-helper
Start a project with your rules already in the folder.
How Claude works in this repo
- Think before coding. State assumptions, ask when something is unclear.
- Simplicity first. No features, abstractions, or config nobody asked for.
- Surgical changes. Every changed line traces back to the request.
- Goal-driven. Define the check, then loop until it passes.
How the UI should look
- An anti-slop checklist for color, type, surfaces, layout, motion, and copy.
- Phone, tablet, and laptop rules. Touch targets 44px or larger.
- A design pick: Claude shows directions in tabs and waits for yours.
- Tokens in okLCH, written in once you choose.
What the rules look like in code
- Hidden assumptions versus asking which export format you meant.
- A discount strategy class hierarchy versus one function.
- A drive-by refactor versus a three-line diff.
- Fixing a sort bug by writing the failing test first.
How it works
It all happens in one terminal session. Tap a step to see where it happens.
$ curl -fsSL https://cc-helper.vercel.app/install.sh | shadded CLAUDE.mdadded DESIGN.mdadded EXAMPLES.md
$ claude> Build a booking page for our climbing gymDESIGN.md has no overview yet. Three questions first:1. Who books: members on phones, or staff at the desk?2. Calm and practical, or loud and sporty?3. Any brand colors or fonts to keep?> Members on phones. Sporty. Brand red is #D7263D.
Published 4 design directions, one per tab:claude.ai/artifact/climb-bookingChalk, Scoreboard, Topo map, Ticket stub> Scoreboard
Wrote Scoreboard tokens to DESIGN.md (+7 lines)Building the booking page. First check: slots sort by time.
Opens in your browser
ChalkScoreboardTopo mapTicket stub
Book a session
Tue 6:00 pm4 spots
Tue 7:30 pm1 spot
Wed 6:00 pm9 spots
Book Tue 6:00 pm
Reply with a tab name, or mix: "Scoreboard layout, Chalk type".
Files that already exist are skipped. Read the script first: /install.sh