promptingFEATURED

>Use CLAUDE.md for Persistent Context

CLAUDE.mdcontextproject-setup
Source:▶How I Start EVERY Claude Code Project|@AI with Avthar

Every time you start a new conversation with Claude Code, you're essentially introducing yourself to a stranger. Claude doesn't remember your project structure, coding preferences, or the architectural decisions you made yesterday. This context switching creates friction and leads to generic responses that don't align with your specific project needs.

The solution? Create a CLAUDE.md file in your project root. This simple file acts as your project's persistent memory, automatically giving Claude the context it needs to provide better, more targeted assistance from the very first message.

Setting Up Your CLAUDE.md File

Start by creating a CLAUDE.md file in your project's root directory—the same level as your package.json or README.md. Claude Code automatically reads this file at the beginning of every conversation, so everything you document here becomes part of the conversation context.

Here's a basic template to get you started:

# CLAUDE.md

## Project Overview
Brief description of what this project does and its main technologies.

## Architecture
Key architectural decisions and patterns used.

## Coding Standards
Your team's coding conventions and preferences.

## Development Environment
Important setup details and requirements.

The key is to include information that will help Claude give you more relevant suggestions and avoid common misunderstandings about your project's structure.

Essential Sections to Include

Project Overview and Tech Stack

Start with the basics. Claude needs to understand what type of project you're working on and which technologies you're using:

## Project Overview
A React Native mobile app for task management with offline-first capabilities.

## Tech Stack
- React Native 0.72
- TypeScript
- React Navigation 6
- Redux Toolkit + RTK Query
- React Native Async Storage
- Expo (managed workflow)

This prevents Claude from suggesting web-specific React solutions when you're building for mobile, or recommending different state management libraries when you've already committed to Redux.

Coding Standards and Preferences

Document your team's coding conventions so Claude's suggestions align with your existing codebase:

## Coding Standards
- Use functional components with hooks exclusively
- Prefer named exports over default exports
- All components should have TypeScript interfaces for props
- Use absolute imports with path mapping (@/components, @/utils)
- Follow conventional commits for git messages
- All async functions must include proper error handling

## File Naming
- Components: PascalCase (`UserProfile.tsx`)
- Hooks: camelCase starting with "use" (`useUserData.ts`)
- Utilities: camelCase (`formatDate.ts`)
- Constants: UPPER_SNAKE_CASE (`API_ENDPOINTS.ts`)

Project Structure

Help Claude understand your folder organization so it can suggest appropriate file locations and import paths:

## Project Structure

src/ components/ ui/ # Reusable UI components features/ # Feature-specific components hooks/ # Custom React hooks services/ # API calls and external services utils/ # Pure utility functions types/ # TypeScript type definitions constants/ # App constants and configuration


## Key files:
- `src/services/api.ts` - Main API configuration
- `src/types/User.ts` - User-related TypeScript types
- `src/utils/storage.ts` - Local storage helpers

Architectural Decisions

Document important architectural choices and patterns your project follows:

## Architecture Decisions
- Using clean architecture with separation between UI, business logic, and data layers
- API responses are normalized using RTK Query's entity adapters
- All forms use React Hook Form with Zod validation
- Error boundaries are implemented at the feature level
- We use the repository pattern for data access

## State Management
- Global state in Redux store for user auth and app settings
- Local component state for UI-only concerns
- Server state managed by RTK Query
- Form state handled by React Hook Form

Advanced Context Strategies

Environment-Specific Information

Include details about your development workflow and tooling:

## Development Environment
- Node.js 18+
- pnpm for package management
- ESLint + Prettier for code formatting
- Husky for pre-commit hooks
- Jest + React Testing Library for testing

## Available Scripts
- `pnpm dev` - Start development server
- `pnpm build` - Production build
- `pnpm test` - Run test suite
- `pnpm lint` - Run ESLint
- `pnpm type-check` - TypeScript compilation check

Current Focus Areas

Use a dedicated section to highlight what you're currently working on:

## Current Focus
Working on implementing the notification system:
- Push notifications for task reminders
- In-app notification center
- Email digest functionality

## Known Issues
- Performance issues with large task lists (investigating virtualization)
- iOS-specific styling inconsistencies in dark mode
- Intermittent sync conflicts in offline mode

This helps Claude understand the current priorities and can lead to more relevant suggestions.

Pro Tips for Effective CLAUDE.md Files

Keep it updated: Your CLAUDE.md file should evolve with your project. When you make significant architectural changes or adopt new conventions, update the file immediately. Stale information can lead Claude to give outdated advice.

Be specific about constraints: If you have specific requirements or limitations, document them clearly. For example, if you can't use certain libraries due to licensing restrictions, or if you need to maintain compatibility with older browser versions.

Include examples of your coding style: Instead of just saying "use functional components," show a sample component that demonstrates your preferred patterns:

## Component Example
```typescript
interface UserProfileProps {
  userId: string;
  onUpdate: (user: User) => void;
}

export const UserProfile = ({ userId, onUpdate }: UserProfileProps) => {
  const { data: user, isLoading } = useUserQuery(userId);
  
  if (isLoading) return `<LoadingSpinner />`;
  
  return (
    `<div className="user-profile">`
      {/* Component implementation */}
    `</div>`
  );
};


**Avoid information overload**: While context is valuable, don't include every detail about your project. Focus on information that directly impacts how Claude should assist you. A 500-line `CLAUDE.md` file might overwhelm the context window.

## Common Pitfalls to Avoid

Don't duplicate information that's already clear from your codebase structure. If your `package.json` already shows you're using React 18, you don't need to repeat that in `CLAUDE.md`.

Avoid including sensitive information like API keys, database credentials, or internal company details. Remember that this file becomes part of every conversation context.

Don't write your `CLAUDE.md` file once and forget about it. As your project evolves, outdated context can actually hurt more than help.

## What's Next

Now that you have persistent context set up, you can explore more advanced prompting techniques like using conversation starters in your `CLAUDE.md` file, or creating project-specific prompt templates. Consider also documenting your testing strategies and deployment processes to give Claude even more context for comprehensive assistance.

The `CLAUDE.md` file is your foundation for better Claude Code interactions—everything else builds on this persistent context layer.
←cd ~/tips