| name | writing-configuration-guides |
| description | Write clear, comprehensive configuration documentation for developer tools and applications. Use when documenting config files, environment variables, feature flags, or initialization parameters. |
Writing Configuration Guides
Quick start
Collect or infer:
- Configuration scope (config file, environment variables, CLI flags, or combined)
- Target runtime or platform
- Required vs optional parameters
- Default values and their rationale
- Security-sensitive values
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- Inventory all configurable parameters and group by function.
- Classify each as required or optional; document defaults.
- Write parameter reference with type, constraints, and examples.
- Add a quick-start minimal config example.
- Document environment-specific overrides if applicable.
- Run the rubric check. Revise until it passes.
Degrees of freedom
- Low freedom: Parameter reference format must follow template exactly.
- Medium freedom: Grouping logic and section order can adapt to product complexity.
- Allowed variation: Additional sections (troubleshooting, migration) as long as rubric passes.
Failure modes to avoid
- Documenting parameters without valid example values
- Omitting units or constraints (e.g., "timeout in seconds, range 1-300")
- Mixing secret values with non-sensitive config without security callouts
- Assuming readers know environment variable inheritance
References