CLAUDE.md & AI Config Collection

Claude Code reads CLAUDE.md on every session start. Having the full stack, commands, and directory structure upfront eliminates 80% of 'wrong guess' edits.

Specifying async patterns and the repository layer prevents Claude from generating synchronous code that doesn't match your architecture.

'Celery tasks for anything > 500ms' is an actionable rule Claude can apply consistently. The split settings pattern tells Claude which file to edit for environment-specific changes.

Rust has strict idioms. 'No unwrap() in production' and 'compile-time checked queries' are constraints Claude can enforce consistently, producing code that compiles cleanly.

'Use pgx directly, not GORM' is the kind of specific instruction that prevents Claude from defaulting to the most popular library. Opinionated rules produce consistent code.

Mobile projects have platform-specific gotchas that generic AI code misses. Specifying 'NativeWind, not StyleSheet' and 'expo-secure-store, not AsyncStorage' catches the two most common RN mistakes.

A minimal CLAUDE.md is better than none. Even just listing your commands and 5 key rules eliminates the most common AI code mistakes for any project.

Cursor rules for Next.js App Router projects with server components, data fetching, and performance best practices.

Cursor rules file (.cursorrules) for React + TypeScript projects. Establishes coding conventions and best practices.

Cursor rules for Python data science with pandas, scikit-learn, and visualization best practices.