ruleslisted

# Rules Skill Project rules are markdown files with YAML frontmatter that Claude Code auto-loads when the file paths you edit match the rule's `paths` globs. Rules live at `<project>/.claude/rules/<name>.md` and are shared across every worktree of the project. ## File format Each rule is a single markdown file: ```markdown --- name: coding-standards description: Short human summary used in the admin panel listing. paths: - "**/*.java" - "**/*.py" --- # Coding Standards ...rule body... ``` Three frontmatter fields, all required: - `name` — lowercase, `[a-z0-9][a-z0-9-_]{0,62}`; must match the filename stem. - `description` — one-liner shown in the admin panel. - `paths` — YAML list of glob patterns (gitignore/minimatch-style). A rule auto-applies whenever the current file path matches any glob. ## Default vs user rules Five rule names are reserved defaults shipped with the admin panel: - `coding-standards` - `java-conventions` - `research-principles` - `test-standards` - `validation-pipeline` Defaults are **immutable** through the MCP tools and the admin panel — they cannot be overwritten, updated, or deleted. Any other rule is a user rule, fully editable. User rules are git-ignored by default (`claude/rules/.gitignore` handles the exceptions for the defaults). ## MCP tools | Tool | What it does | |------|--------------| | `rule_list(project)` | Returns every rule in a project with `{name, description, paths, source}`. | | `rule_get(project, name)` | Returns o