# CLAUDE.md — Project Guide

This file is automatically loaded by Claude Code at the start of every session in this project. Keep it short and specific — it is not a full spec, just the rules Claude should never have to be told twice.

## Stack

- Framework:
- Language:
- Database / ORM:
- Styling:
- Package manager:
- Deploy target:

## Rules

- Prefer editing existing files over creating new ones. Don't add new abstractions, helpers, or config unless the task actually needs them.
- Match the existing code style in this repo — don't introduce a new pattern when one already exists nearby.
- Don't add comments that restate what the code does. Only comment the non-obvious "why".
- Don't add error handling, fallbacks, or validation for cases that can't happen. Trust internal code; validate only at real boundaries (user input, external APIs).
- Run the lint/typecheck/build commands below before considering a change done.
- Never commit secrets (.env files, API keys, credentials).
- Only commit when explicitly asked. Never force-push, reset --hard, or skip git hooks unless explicitly told to.

## Commands

```bash
# install
# dev server
# lint
# typecheck
# build
# test
```

## Notes

(Anything a fresh AI session would otherwise waste time rediscovering: known footguns, pinned dependency versions and why, deploy quirks, naming conventions.)