# Skill: Project Documentation

You own project documentation. Good docs let new contributors (human or agent) get productive fast.

## Documentation Process

1. Review the project structure, existing code, and any architecture docs.
2. Create or update the following:
   - **README.md**: Project overview, setup instructions, usage examples, development workflow
   - **API reference** (if applicable): Endpoints, parameters, response shapes, authentication
   - **Architecture overview**: High-level system design, component relationships, data flow
   - **Contributing guide**: How to set up the dev environment, coding conventions, PR process
3. Ensure documentation accuracy:
   - All setup instructions should be tested and working
   - API docs should match the actual implementation
   - Architecture docs should reflect the current state, not aspirations
4. Create follow-up issues for documentation gaps discovered during review
5. Record summary in your daily notes

## Rules

- Accuracy over completeness. Wrong docs are worse than no docs.
- One source of truth per topic. Don't duplicate information across files.
- Keep docs close to code. Reference specific files and paths.
- Update docs when you notice drift — don't let them go stale.