claude-md-rules-creatorlisted

Authors CLAUDE.md, CLAUDE.local.md, and `.claude/rules/*.md` (the standing-instruction layer Claude Code prepends as a `<system-reminder>` user message at every session start). Covers the four scopes (managed / user-global / project-team / project-personal), `paths:` for path-scoped rules, `@path` imports (depth 5, external-approval), splitting bloated files, `claudeMdExcludes`, HTML-comment maintainer notes, AGENTS.md interop, monorepo + worktree handling, and debugging "Claude is not following my CLAUDE.md". Use proactively when the user says "add to CLAUDE.md", "write a rule", "init memory", "global instructions", "user-level instructions", "team conventions", "project memory", "claude.md", "rules file", "agent instructions", or asks to refactor an oversized CLAUDE.md or fix instructions the model is ignoring. Triggers even when the user does not say "skill". Pair with `ac:skill-creator` for the surrounding shape, `ac:prompt-writer` for body content, `ac:agent-creator` for subagent CLAUDE.md inheritance.
anilcancakir/claude-code · ★ 1 · AI & Automation · score 77

Install: claude install-skill anilcancakir/claude-code

# CLAUDE.md and Rules Creator You are about to write or edit a CLAUDE.md, CLAUDE.local.md, or `.claude/rules/*.md` file. At runtime these three shapes are the SAME content type: Claude Code's memory loader discovers them, concatenates them with a fixed `MEMORY_INSTRUCTION_PROMPT` prefix, and the API layer prepends the result as a single `<system-reminder>` user message before the conversation starts. The model treats them all the same; the file shape just controls when each loads and how a human maintains it. This skill is the playbook for picking the right shape, choosing the right scope, writing content that actually changes behavior, splitting bloated files, using `@path` imports, and debugging "Claude is not following my CLAUDE.md". Target is Opus 4.8. Same rules work for Sonnet 4.6 and Haiku 4.5 with lower effort levels. ## Three jobs, not one Writing a CLAUDE.md or rule splits into three tasks. Conflating them is the most common authoring mistake. 1. **Surrounding skill shape.** None. CLAUDE.md and `.claude/rules/*.md` are not skills, not commands, not agents. They are plain markdown files the memory loader picks up. No frontmatter fields apply except `paths:` (only on `.claude/rules/*.md`). Route through `ac:skill-creator` ONLY if you are wrapping CLAUDE.md authoring inside a custom slash command or skill. 2. **CLAUDE.md / rule shape.** Where the file lives (managed / user-global / project-team / project-personal), what file name (`CLAUDE.md` / `CLAUDE.local.md` /