Generating the repo is one command. Keeping it current — adding a technology, implementing a feature, reviewing what an assistant wrote — is the rest of them.
It doesn't know your auth provider, your folder conventions, or that you never scaffold a router. So it invents them — differently every session. Scaffolding isn't optional context; it's the whole input.
Nobody picks their whole stack up front. Six commands keep a generated project current without ever overwriting something you edited by hand.
Writes a plan, prompts, a checklist and skeleton files for one feature — tailored to the provider your project selected. Same command, genuinely different output.
Slot in one more technology, or swap a single-select category. Infers what it's replacing from the project itself.
Refresh rules, prompts and docs to the current version using the selection the project already has.
Static, AI-oriented pass over a generated project across architecture, security, performance and DX.
Works on any repo, generated or not — infers the stack from dependencies, and names its evidence.
Checks this machine before you spend a wizard run finding out the hard way.
One preset, one command, and the assistant already knows your stack. No afternoon spent writing rules files by hand.
Everyone's assistant reads the same rules whether they're on Cursor, Cline or Copilot. Check the config into git and it stays that way.
Same scaffolding every time, deterministic output, and a cost estimate you can paste into a proposal.
You already wrote a .cursorrules once. This generates the equivalent for eight tools, per technology, and upgrades them in place.
Every command here runs on your machine, needs no account, and is MIT-licensed. The one paid flag is --idea.