documentation-patternslisted

# Documentation Patterns Use this skill when the main problem is document shape and consistency rather than writing quality alone. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## Activation Conditions Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below. - Creating a new API, feature, or config guide - Standardizing Markdown sections across repositories - Writing migration or runbook documents - Picking the right template for a doc request ## Pattern Selection - API docs: endpoints, auth, request and response schema, errors - Feature docs: purpose, UX, dependencies, rollout, support - Config docs: env vars, defaults, examples, failure modes - Migration docs: changed behavior, upgrade path, verification ## Cross-Skill Workflow - Use [documentation-authoring](../documentation-authoring/SKILL.md) to gather context and draft the content before template selection becomes the bottleneck. - Use this skill when structure, section order, or template choice is the main problem. - Finish with [documentation-quality](../documentation-quality/SKILL.md) to review the final document against quality expectations. ## Agent Prompt Template ```text Use the documentation-patterns skill to choose and apply the best structure for a [document type]. Context: [feature, system, migration, or runbook]. Bias toward: [API docs, feature docs, config guide, migration guide, etc.]. Return the recommended