# Contributing

## Workflow

1. Create a branch for your work: `git checkout -b fix/issue-N-name` or `git checkout -b feat/issue-N-feature-name`
2. Make changes and commit with clear messages
3. Open a Pull Request for review
4. Do not merge directly to `main` for reviewable changes
5. After approval, squash and merge

## Guidelines

- Use clear, descriptive commit messages
- Keep PRs focused and reasonably sized
- Document any non-obvious decisions
- Test changes before submitting

## Branches

- `main` — stable, reviewed content only
- `develop` — experimental work for 0.2.x
- `fix/*` — bug fixes
- `feat/*` — new features
- `docs/*` — documentation updates
- `refactor/*` — refactoring
- `research/*` — new research notes