← ClaudeAtlas

autodev-initlisted

Derive this project's actual conventions from its code and write them into a project-local rules file, so autodev enforces what this codebase already decided instead of a generic default.
djnsty23/claude-auto-dev · ★ 3 · Code & Development · score 65
Install: claude install-skill djnsty23/claude-auto-dev
# autodev-init Every other skill in this plugin ships someone else's conventions. This one reads yours out of the code and writes them down, so `review`, `audit`, and `auto` enforce what your project actually does. Output goes to **`.claude/project-rules.md`** in the project — not into the plugin. It is project-local, git-committed, and human-editable. The generic `standards` and `rule-*` skills stay as the fallback for anything you have not decided. ## Rule one: observe, never assume Every line you write must be backed by a count from this codebase. If you cannot produce evidence, the convention does not go in the file — write it in the "Undecided" section instead. A generated rules file that guesses is worse than none, because `review` will enforce the guess. If `.claude/project-rules.md` already exists, this is a **refresh**: re-measure, show a diff of what changed, and preserve every hand-edited line. Never silently overwrite a human's edit. ## Step 1: Establish the stack ```bash cat package.json 2>/dev/null | head -60 ls -d src app pages components lib server 2>/dev/null cat tsconfig.json 2>/dev/null | head -30 ``` Record: framework and major version, router style, package manager (from the lockfile), TypeScript strictness, test runner, linter/formatter. ## Step 2: Measure the conventions Run these and **keep the counts** — they are the evidence. ```bash # Component style: function declarations vs arrow consts grep -rEc "^export (default )?function [A-Z]" --in