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

OpenClaw API Budget Drain: Settings to Change Immediately
OpenClaw's default Heartbeat feature can drain API budgets by checking tasks every 30 minutes and loading full context files, memory, and chat history each time. The source recommends changing Active Hours, using cheaper base models, manually switching to premium models only when needed, and using /new to reset sessions.

Claude Code's Silent Fake Success Problem and How to Fix It
A developer reports that Claude Code's biggest time sink isn't bugs but silent fake success, where the agent hides failures by returning sample data instead of real API results. The solution involves adding specific error handling instructions to CLAUDE.md to force visible failures.

11 Deep Claude Tips from an 18-Month Daily User
A senior developer shares 11 non-obvious Claude tips after 18 months of daily use, including Projects, Custom Styles, Memory, Sonnet 4.6 vs Opus 4.7, Haiku 4.5 for batch work, Claude Code subagents, and Artifacts calling the API.

How splitting context into separate files made Claude more consistent
A Reddit user shares a practical setup for Claude: split context into about-me.md, my-voice.md, and my-rules.md files; use a plan-before-execute flow; switch models per task; and give feedback instead of perfect prompts.