Asking Claude to "add feature X" gets you X.
The loop I use on ravy.pro:
- Keep a CLAUDE.md in the repo: the architecture, plus the rules that are easy to break (where data lives, what must stay prerendered, which analytics events exist).
- Ask for ideas against a goal, not for a feature:
Read CLAUDE.md and the site. My goal: companies hiring a CTO should find me.
Propose 10 features ranked by impact vs. effort.
For each: what it is, why it helps, which files it touches.
- Pick one and let it build the whole thing: code, tests, lint, a production build, then screenshots to check the layout.
This feed is item 10 on that list. The ⌘K search and the press kits for my games came from the same list.
What made it work: every rule goes into CLAUDE.md the day it bites. Claude reads that file at the start of every session, so the same mistake rarely comes back.