create-claude-mdlisted

Analyze the current project and write an effective `CLAUDE.md` — either creating one from scratch or refining an existing one — following official Claude Code guidelines and the principle that shorter is better. ## Steps 1. **Check for existing CLAUDE.md** at the project root. If one exists, read it first. 2. **Inspect project files** to detect build system, test runner, lint/format setup, and conventions: - `package.json`, `pyproject.toml`, `Cargo.toml`, `Makefile`, `*.sln`, `go.mod` - `.eslintrc*`, `.prettierrc*`, `biome.json`, `ruff.toml` - `README.md`, `docs/` directory, `.github/` for PR/branch conventions - `git log --oneline -10` to detect commit message conventions - `git remote -v` to identify the repository 3. **Apply the placement decision** for each rule you find: - Project-wide rules → `CLAUDE.md` - Domain-specific or file-type-specific rules (e.g., "React component rules", "SQL migration rules") → `.claude/rules/<domain>.md` with `paths:` frontmatter - Automated/enforcement behaviors (auto-format on save, lint fixing) → do NOT put in CLAUDE.md; note them as candidates for `settings.json` PostToolUse hooks 4. **Apply the include/exclude filter** before writing each line: ✅ Include: - Bash commands Claude cannot guess (build, test, deploy, migrate, seed) - Code style rules that differ from language/framework defaults - Testing instructions and preferred test runners - Branch naming, PR conventions, commit message format