Back to articles
My exact Claude Code setup for every new project (copy-paste configs)
How-ToSystems

My exact Claude Code setup for every new project (copy-paste configs)

via Dev.tobrian austin

Every time I start a new project, I spend the first 10 minutes setting up Claude Code properly. After doing this 20+ times, I've got it down to a repeatable system. Here's the exact folder structure and config files I use. The folder structure your-project/ ├── CLAUDE.md ← project memory ├── .claude/ │ ├── settings.json ← behavior rules │ └── commands/ ← custom slash commands │ ├── review.md │ ├── test.md │ └── deploy.md └── src/ Step 1: CLAUDE.md — project memory This is the most important file. Claude reads it at the start of every session. # Project: [your project name] ## What this is [One sentence description] ## Stack - Language: Node.js 20 - Framework: Express - Database: PostgreSQL - Tests: Jest ## Key conventions - Use async/await, never .then() chains - All functions must have JSDoc comments - Error handling: always throw, never return null for errors - File naming: kebab-case.js ## What NOT to do - Don't use var (ESLint will catch it) - Don't commit .env files - Don't write

Continue reading on Dev.to

Opens in a new tab

Read Full Article
6 views

Related Articles