# Project Context

> Auto-generated by `mk:project-context`. Edit manually to add unobvious rules.
> Sections marked `<!-- manual -->` are preserved during `update` action.

## Technology Stack

- **Language:** [detected] [version]
- **Framework:** [detected] [version]
- **Runtime:** [detected] [version]
- **Package manager:** [detected]
- **State management:** [detected] (NOT [rejected alternative])
- **Testing:** [unit framework], [e2e framework], [mock strategy]
- **Styling:** [approach] [framework if any]
- **Database:** [type] [ORM if any]
- **Auth:** [provider/approach]

## Critical Implementation Rules

<!-- manual -->

### [Language/Framework]

- [Rule] — WHY: [reason]
- [Anti-pattern to avoid] — WHY: [reason]

### Code Organization

- Components in `[path]` with co-located `*.test.*` files
- Utilities in `[path]` — pure functions only
- API calls use `[pattern]` (e.g., singleton client, fetch wrapper)
- Types/interfaces in `[path]`

### Testing Patterns

- **Unit tests:** [approach — what to test, what NOT to test]
- **Integration tests:** [approach — real DB or mocks?]
- **E2E tests:** [scope — critical user journeys only?]
- **Coverage target:** [percentage or "match existing"]

## Anti-Patterns (DO NOT)

<!-- manual -->

- [Pattern] — WHY: [what breaks if you do this]
- [Pattern] — WHY: [what breaks if you do this]

## Environment & Deployment

- **Environments:** [list]
- **CI/CD:** [tool] [pipeline description]
- **Deploy target:** [platform]
- **Branch strategy:** [main/dev/feature pattern]

## Project-Specific Conventions

<!-- manual -->

- [Convention not inferable from code]
- [Convention not inferable from code]
