course-developmentlisted

# Develop a Technical Course Build a course learners can understand, execute, and finish. Use [documentation-site](../documentation-site/SKILL.md) as the default course publisher; an existing course repository owns its platform, page schema, and task names. Use [quality-assurance](../quality-assurance/SKILL.md) for a broader test campaign. ## Workflow 1. **Define the learner**: prerequisites, target capability, time, delivery format, and accessibility needs; keep only content that advances the outcome. 1. **Make outcomes observable**: give each lesson a primary capability and a completion signal; introduce terms before using them. 1. **Ground examples**: derive code and counts from shipped source or generated evidence; explain the reason beside a command and distinguish captured output from illustration. 1. **Record terminal examples when useful**: follow the [VHS workflow](../fmind-visuals/references/recording.md) for reproducible demos with synthetic inputs; retain the command transcript and a static equivalent for accessibility. 1. **Make practice executable**: state the goal, starting state, a prediction, ordered work, verification, and what remains afterward; label temporary changes and external access/cost. 1. **Review the learner surface**: navigation, reading order, keyboard use, contrast, alt text, mobile layout, copy/paste, and diagrams explained in prose. 1. **Validate progressively**: run the changed lesson's checks and examples, then the repository's learner g