Design Onboarding Mental Model
Use this skill when the problem is not just readability but understanding: the user needs a correct mental model of a product, workflow, concept, or feature. It applies to onboarding UI, first-run flows, empty states, feature announcements, pitch/explainer decks, PDF guides, diagrams, and tutorial visuals.
Workflow
- Identify the user's likely existing mental model and where it differs from the intended conceptual model.
- Read
references/principles.md when designing onboarding, walkthroughs, empty states, explainers, educational decks/PDFs, or feature introductions.
- Define the first useful action, the core concept to teach, and the minimum vocabulary the user needs.
- Teach through concrete examples, narrative sequence, progressive disclosure, and visible cause-effect feedback.
- Pair with execution skills as needed:
frontend-design, presentations, documents, imagegen, figma, or react.
Output Expectations
Return an onboarding or explanation structure that states what the user believes, what they need to believe instead, what proof or example teaches it, and what first action confirms learning.
Boundaries
Do not use this skill for ordinary text cleanup without a mental-model problem. Use improve-readability-information-design for wording and layout, and reduce-cognitive-load for memory/complexity reduction inside an already understood workflow.
1---2name: design-onboarding-mental-model3description: Design onboarding, first-run experiences, walkthroughs, empty states, product explainers, training flows, explainer decks, educational PDFs, and feature introductions around accurate user mental models. Use when Codex needs to help new users understand what something is, how it works, why it matters, what to do first, or how to update an incorrect expectation.4---56# Design Onboarding Mental Model78Use this skill when the problem is not just readability but understanding: the user needs a correct mental model of a product, workflow, concept, or feature. It applies to onboarding UI, first-run flows, empty states, feature announcements, pitch/explainer decks, PDF guides, diagrams, and tutorial visuals.910## Workflow11121. Identify the user's likely existing mental model and where it differs from the intended conceptual model.132. Read `references/principles.md` when designing onboarding, walkthroughs, empty states, explainers, educational decks/PDFs, or feature introductions.143. Define the first useful action, the core concept to teach, and the minimum vocabulary the user needs.154. Teach through concrete examples, narrative sequence, progressive disclosure, and visible cause-effect feedback.165. Pair with execution skills as needed: `frontend-design`, `presentations`, `documents`, `imagegen`, `figma`, or `react`.1718## Output Expectations1920Return an onboarding or explanation structure that states what the user believes, what they need to believe instead, what proof or example teaches it, and what first action confirms learning.2122## Boundaries2324Do not use this skill for ordinary text cleanup without a mental-model problem. Use `improve-readability-information-design` for wording and layout, and `reduce-cognitive-load` for memory/complexity reduction inside an already understood workflow.
amaledtuning