Apply the platform blueprint code documentation standard. Use when adding or updating comments, package docs, README/docs content, runbooks, contract comments, or reviewing whether a change needs documentation in Go, TypeScript, Terraform, protobuf, or shared platform docs.
Use this skill when code or docs work needs the platform's documentation rules applied consistently.
Document why, contracts, constraints, and non-obvious behavior. Do not document obvious mechanics.
When a change affects other repositories or the platform contract between repositories, also update platform-blueprint-specs in the same task.
Cross-repo examples:
When cross-repo impact exists, update the smallest durable planning artifact that matches the change:
common/standards/ and matching skills in .codex/skills/ when they existplatform-specification.md when a locked stack or architecture decision changesDo not keep cross-repo behavioral knowledge only in a code repo if other repos depend on it.
Be explicit when documenting:
.proto comments as part of the interface contractWhen reviewing or changing code, ask: