Generating Feature Content Context
Quick start
Collect or infer:
- •Feature name and purpose
- •User goals and tasks the feature supports
- •Feature states (empty, loading, error, success, etc.)
- •UI components and their copy needs
- •Business rules and constraints
- •Edge cases and exceptions
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- •Identify the feature scope and boundaries
- •Document user goals and primary tasks
- •Map all feature states systematically
- •Catalog UI components requiring copy
- •Document business rules affecting content
- •Capture edge cases and exception handling
- •Compile terminology and naming decisions
- •Validate completeness against rubric
- •Run the rubric check. Revise until it passes.
Degrees of freedom
Freedom level: Low
- •Default: follow templates exactly
- •Allowed variation: depth of state coverage based on feature complexity—as long as rubric passes
- •Strict constraints: Must cover all states; must include terminology; must document constraints
State awareness
- •New feature: Build context as feature is designed; iterate with product/engineering
- •Existing feature: Audit current copy to extract implicit context; document gaps
- •Feature update: Start from existing context; document what's changing
- •AI consumption: Ensure structured format; include examples for each component
References
- •Templates: TEMPLATES.md
- •Rubric: RUBRIC.md
- •Examples: EXAMPLES.md
- •Context pack schema: reference/context-pack-schema.md