Claude Rules for Coding
Community-submitted CLAUDE.md rules for general coding and software development. These rules help Claude Code write better code, enforce style guides, and follow team best practices.
1 rule matching Coding
CLAUDE.md Rules for Coding & Development
CLAUDE.md is a Markdown configuration file that Claude Code reads at the start of every session. By committing one to your repository, you give Claude persistent knowledge about your project's conventions — code style, commit message format, test commands, lint rules, what to avoid — so you stop repeating yourself in every prompt. The general-coding CLAUDE.md rules in this directory cover patterns that aren't language-specific: how teams set up commit-message conventions for Conventional Commits or imperative mood, how to structure a "what NOT to do" list of project-specific gotchas, when to insist on running tests before any push, and how to keep the file lean enough that it doesn't burn through Claude's context window. If you're new to CLAUDE.md, start here. If you're refining a file you already maintain, browse these examples for ideas you can adapt.
Why add Coding rules to your CLAUDE.md?
CLAUDE.md files let you give Claude Code persistent instructions for your project. Coding-focused rules typically cover commit message conventions, code style enforcement, how to run tests, which linters to use, and patterns to avoid. Adding these rules to your repository means Claude follows your team's standards automatically — without you having to repeat yourself in every prompt.