Use this skill when code or docs work needs the platform's documentation rules applied consistently.

Core Rule

Document why, contracts, constraints, and non-obvious behavior. Do not document obvious mechanics.

Default Workflow

Identify the smallest durable documentation layer that matches the change.
Update code and documentation in the same change.
Prefer language-native doc styles first.
Add repo docs only when behavior, runtime flow, architecture, or operations would be hard to infer from code alone.
Escalate to planning docs only when the behavior affects multiple repos or a platform policy.

When a change affects other repositories or the platform contract between repositories, also update platform-blueprint-specs in the same task.

Cross-repo examples:

API contract, protobuf, auth, or runtime changes that affect frontend, workers, infra, or AI automation

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.

Identify the smallest durable documentation layer that matches the change.
Update code and documentation in the same change.
Prefer language-native doc styles first.
Add repo docs only when behavior, runtime flow, architecture, or operations would be hard to infer from code alone.
Escalate to planning docs only when the behavior affects multiple repos or a platform policy.

When a change affects other repositories or the platform contract between repositories, also update platform-blueprint-specs in the same task.

Cross-repo examples:

API contract, protobuf, auth, or runtime changes that affect frontend, workers, infra, or AI automation