Documentation
README
Happier Documentation
Keep documentation truthful, useful, current, and owned without turning every code change into prose churn. Follow the root constitution and, for published docs, apps/docs/AGENTS.md. For an explicit deep review or QA request, use skills/happier-review as the orchestrator and apply this skill as the documentation-domain standard; this skill does not create a competing general review workflow.
1. Classify the documentation impact
For the changed behavior or contract, decide whether it affects:
- internal technical/product architecture under
docs/**; - published user/operator/self-hoster/contributor behavior under
apps/docs/content/docs/**; - both surfaces;
- neither surface, with a concrete reason.
This is the opening of the README. Read the full README on GitHub.