I built this after getting tired of writing CLAUDE.md files by hand every time I started a new project or onboarded to an existing codebase.
The problem: Claude and Cursor are both really good when they understand your project's conventions. But getting them that context means either writing a rules file from scratch (tedious) or pasting your package.json and hoping for the best.
rulegen scans your project once and outputs a clean rules file. It picks up language versions, frameworks, test patterns, build conventions, database setup, CI config. Zero deps, runs offline, takes about 2 seconds.
`npx rulegen` in any project root. Defaults to CLAUDE.md but --format cursorrules works too.
Happy to hear what stacks it handles poorly -- I've tested it mostly on Node/Python/Go projects and there are definitely edge cases I haven't hit yet.
vexorkai•1h ago
The problem: Claude and Cursor are both really good when they understand your project's conventions. But getting them that context means either writing a rules file from scratch (tedious) or pasting your package.json and hoping for the best.
rulegen scans your project once and outputs a clean rules file. It picks up language versions, frameworks, test patterns, build conventions, database setup, CI config. Zero deps, runs offline, takes about 2 seconds.
`npx rulegen` in any project root. Defaults to CLAUDE.md but --format cursorrules works too.
Happy to hear what stacks it handles poorly -- I've tested it mostly on Node/Python/Go projects and there are definitely edge cases I haven't hit yet.