Use CLAUDE.md to Persist Project Conventions Across Claude AI Sessions

A Reddit user reports that adding a CLAUDE.md file to the project root is the single highest-leverage change they've made with Claude Code. Claude reads this file at the start of every session, so you never need to re-explain conventions like TypeScript usage, Tailwind vs. CSS modules, test folder structure, or data model relationships.
Key Details
- Placement: Create a file named
CLAUDE.md in the root of your project directory. - What to include: Coding conventions (e.g., "We use TypeScript, always. No default exports. Tailwind, not CSS modules. Tests go in tests folders."), plus project architecture context — how modules connect, data models, and which files are critical vs. scaffolding.
- Behavior: The file is read automatically at the start of every Claude session. No manual invocation needed. Conventions are applied without being asked.
- Result: The user noticed "Claude's edits got noticeably better once it had that context baked in from the start of the session."
Practical Example
# CLAUDE.mdConventions
- Language: TypeScript
- Exports: named exports only (no default exports)
- Styling: Tailwind CSS (no CSS modules)
- Testing: tests go in dedicated tests/ folders
Architecture
- Frontend: React with React Router
- API layer: Express routes in /api
- Data models: Prisma schema in /prisma
- Critical files: /src/app.ts, /src/config.ts
After adding this file, the user reports never having to retype those rules per session.
Who It's For
Developers using Claude Code or any Claude-powered coding agent who want consistent behavior across chat sessions without repeating instructions.
📖 Read the full source: r/ClaudeAI
👀 See Also

High CPU/RAM and Gateway Restarts in OpenClaw? Disable IPv6 for Telegram
Setting autoSelectFamily: false and dnsResultOrder: 'ipv4first' in Telegram bot config stops ENETUNREACH errors, fixing high CPU, event loop freezes, and gateway restarts.

How to Run OpenClaw Without Breaking the Bank
Reddit user digitalknk shared a practical guide on running OpenClaw efficiently. A battle-tested setup focused on stability and cost control.

Using Light-Context Cron Jobs for Daily OpenClaw Tips
A user shares their setup of a daily cron job that posts OpenClaw tips to a Nextcloud Talk channel, highlighting the --light-context flag to reduce bootstrap overhead for isolated tasks.

Using AI to Generate Project Tickets Before Coding Reduces Scope Drift
A developer found that asking AI to generate detailed project tickets with tasks, sub-tasks, scope, and acceptance criteria before writing any code significantly reduced scope creep and large diffs. Each AI agent only receives its specific sub-task, not the entire plan.