your-project/
└── .claude/
    └── rules/
        ├── code-style.md
        ├── testing.md
        └── frontend/
            └── react.md

~/.claude/
└── rules/
    ├── preferences.md
    └── workflows.md

# Rule Title

Your markdown instructions here...

---
paths:
  - "src/api/**/*.ts"
---

# API Development Rules

Instructions that only apply to API files...

---
paths:
  - "src/components/**/*.tsx"
---

# React Component Guidelines

- Use functional components with hooks
- Keep components under 300 lines

---
paths:
  - "src/**/*.ts"
  - "lib/**/*.ts"
  - "tests/**/*.test.ts"
---

# TypeScript Guidelines

/memory    # Shows all loaded memory files including rules

.claude/
├── CLAUDE.md                    # Main project overview
└── rules/
    ├── code-style.md            # Coding style and formatting
    ├── testing.md               # Testing conventions
    ├── security.md              # Security requirements
    ├── frontend/
    │   ├── react.md             # React-specific rules
    │   ├── styling.md           # CSS conventions
    │   └── accessibility.md     # A11y requirements
    └── backend/
        ├── api.md               # API design standards
        ├── database.md          # Database conventions
        └── authentication.md    # Auth rules

---
paths:
  - "src/components/**/*.tsx"
  - "src/pages/**/*.tsx"
---

# React Component Guidelines

## Structure
- Use functional components with hooks
- Colocate styles using CSS modules
- Keep components under 300 lines

## Hooks
- Never call hooks conditionally
- Extract custom hooks for reusable logic
- Use useCallback for functions passed to children

## Props
- Use TypeScript interfaces for props
- Destructure props in function signature

---
paths:
  - "src/api/**/*.ts"
  - "src/routes/**/*.ts"
---

# API Design Standards

## Endpoints
- Use RESTful naming: `/api/v1/{resource}/{id}`
- Version all endpoints

## Error Format
```json
{
  "error": "error_code",
  "message": "Human readable message",
  "details": {}
}

### Testing Rules

**`.claude/rules/testing.md`**

```markdown
# Testing Conventions

## Unit Tests
- Minimum 80% code coverage
- File naming: `[feature].test.ts`
- Structure: Arrange-Act-Assert

## Integration Tests
- Location: `tests/integration/`
- Clean up database after each test

## Test Data
- Use fixtures in `tests/fixtures/`
- Use factories for test objects

# Security Requirements

## Authentication
- Require auth for all protected endpoints
- Use JWT with 24-hour expiration
- Implement refresh token rotation

## Data Protection
- Never log passwords, tokens, PII
- Encrypt data at rest and in transit
- Use parameterized queries (prevent SQL injection)

## Dependencies
- Run `npm audit` before deployment
- Pin dependency versions

---
paths:
  - "scripts/**/*.py"
  - "tools/**/*.py"
---

# Python Guidelines

## Style
- Follow PEP 8
- Use type hints for all functions
- Line length: 88 characters (Black)

## Structure
- Use dataclasses for simple data
- Use pathlib.Path instead of os.path
- Use f-strings for formatting

# Create rules directory
mkdir -p .claude/rules

# Create a rule file
touch .claude/rules/testing.md

# Create organized subdirectories
mkdir -p .claude/rules/backend
touch .claude/rules/backend/database.md

# Symlink a shared rules directory
ln -s ~/shared-claude-rules .claude/rules/shared

# Symlink individual files
ln -s ~/company-standards/security.md .claude/rules/security.md