Claude Guidelines
Guideline Metadata
Version: 1.0.0 Last Modified: 2025-01-19T00:00:00Z Category: Overview Priority: Essential
This section contains specific guidelines for working with Claude Code (claude.ai/code) on projects. These guidelines ensure consistency and efficiency across all collaborative development work.
Purpose
These guidelines serve as a central reference for: - General working principles and collaboration patterns - Naming conventions and coding standards - Architecture decisions and patterns - Project structure templates - Common solutions and approaches
Structure
The Claude Guidelines are organized into the following sections:
- General Principles - Core working principles and collaboration patterns
- Naming Conventions - Standardized naming across all projects
- Architecture Patterns - Common architectural decisions and patterns
- Project Templates - Standardized project structures for different tech stacks
- Common Solutions - Reusable solutions for recurring problems
Key Principles
When working with Claude Code on projects:
- Consistency First - Follow established patterns and conventions
- Explicit Over Implicit - Clear, descriptive names and structures
- Three-Layer Architecture - Maintain separation of concerns
- Provider Pattern - Isolate external dependencies
- No Magic - Avoid clever tricks in favor of clarity
Quick Reference
File Naming
- Use kebab-case for files: user-provider.ts
- Use PascalCase for components: UserProfile.svelte
- Use lowercase for database: user_accountstable
Function Naming
- Use camelCase for functions: getUserById()
- Use descriptive verbs: fetch,update,delete,validate
- Prefix boolean functions with is,has,can:isValid()
Project Structure
project/
├── src/
│   ├── providers/     # Data access and external services
│   ├── managers/      # Business logic orchestration
│   ├── io/           # Input/output handling
│   ├── models/       # Data structures
│   ├── mappers/      # Data transformation
│   ├── helpers/      # Utility functions
│   └── constants/    # Configuration and enums
├── tests/
└── docs/
Integration with CLAUDE.md
Each project should have a CLAUDE.md file that references these guidelines and adds project-specific instructions. This creates a two-tier system:
- Global Guidelines (this section) - Universal rules for all projects
- Project Guidelines (CLAUDE.md) - Project-specific additions
Example CLAUDE.md reference: