Start with the Developer Must-Read for the maintained development workflow, validation requirements, and completion criteria.
Before implementation and again before PR submission, complete the human contributor-intent gate in the repository's author self-review skill. Reuse explicit, traceable human answers and ask only for missing decisions. The gate applies to contributor work, not independent read-only reviews.
Keep the existing performance and code-quality requirements in the developer guide, including the performance skill and refactoring skill. Scale evidence to the changed behavior and disclose unrun checks; documentation-only changes do not justify irrelevant GPU benchmarks.