← ClaudeAtlas

conventionslisted

Write an existing codebase's unwritten conventions into path-scoped .claude/rules/ files with golden files, or refresh them after the code moved on.
viettdann/arclight-kit · ★ 0 · AI & Automation · score 65
Install: claude install-skill viettdann/arclight-kit
# Conventions Write down what a competent developer new to this repo would get wrong: the conventions the code follows that no linter checks. The output is a few short rules files Claude Code loads when it reads or edits matching files, so it costs no context elsewhere. ## 1. Mode If `.claude/rules/conventions*.md` exists, run Update (step 6). Otherwise run a first scan. Say which in one line and continue. ## 2. Inventory - Read what is already written down: `CLAUDE.md`, `AGENTS.md`, `CONTRIBUTING.md`, `.editorconfig`, linter and formatter configs (`eslint`, `biome`, `prettier`, `.globalconfig`, `Directory.Build.props`, analyzers). Anything they state or enforce stays out of the rules. - Split the repo into layers by `git ls-files` (for example ASP.NET projects, a Next or Vite frontend, shared packages). Each layer gets its own scan and its own rules file. - Size each layer by source file count and pick the depth: up to 50 files, read them all; 50 to 500, read shared and infrastructure code fully and sample two or three files per dimension; above 500, sample from `git log --since=6.months --name-only` first, then the largest and most imported files. Recently changed files show where the team is heading; old files show what exists. - Done when every layer has a path glob, a file count, and a chosen depth, and the list of what existing docs and configs already enforce is written down. ## 3. Scan each layer | Dimension | Look for | | --- | --- | | File anatomy | Folder by