Build Motivation Trust
Use this skill when the design problem is confidence, motivation, emotional pull, or willingness to continue. It applies to UI, onboarding moments, checkout, landing pages, pitch decks, promotional images, profile pages, PDF one-pagers, posters, and product storytelling.
Workflow
- Identify the desired user belief or behavior: continue, trust, start, return, share, buy, submit, or remember.
- Read
references/principles.md when the task involves progress, rewards, credibility, social proof, emotional tone, human cues, trust signals, or engagement.
- Diagnose trust and motivation blockers: uncertainty, lack of proof, weak progress, unclear value, impersonal tone, excessive friction, or manipulative pressure.
- Add ethical cues: progress visibility, credible proof, human context, useful reward, reassurance, specific value, and clear agency.
- Pair with execution skills as needed:
frontend-design, presentations, documents, imagegen, figma, or react.
Output Expectations
Return a concrete motivation/trust strategy: what emotion or belief to support, what proof to show, what progress cue to add, what friction to remove, and what manipulative pattern to avoid.
Boundaries
Do not use this skill to justify deceptive urgency, hidden costs, forced continuity, confirmshaming, or other dark patterns. Use simplify-decisions-recovery when the main issue is choosing between options or recovering from an error.
1---2name: build-motivation-trust3description: Build ethical motivation, trust, credibility, emotional resonance, progress cues, social proof, and engagement across websites, apps, forms, presentations, pitch decks, PDFs, posters, ads, profile pages, checkout flows, and product visuals. Use when Codex needs to make an experience feel credible, human, motivating, reassuring, memorable, or worth continuing without using dark patterns.4---56# Build Motivation Trust78Use this skill when the design problem is confidence, motivation, emotional pull, or willingness to continue. It applies to UI, onboarding moments, checkout, landing pages, pitch decks, promotional images, profile pages, PDF one-pagers, posters, and product storytelling.910## Workflow11121. Identify the desired user belief or behavior: continue, trust, start, return, share, buy, submit, or remember.132. Read `references/principles.md` when the task involves progress, rewards, credibility, social proof, emotional tone, human cues, trust signals, or engagement.143. Diagnose trust and motivation blockers: uncertainty, lack of proof, weak progress, unclear value, impersonal tone, excessive friction, or manipulative pressure.154. Add ethical cues: progress visibility, credible proof, human context, useful reward, reassurance, specific value, and clear agency.165. Pair with execution skills as needed: `frontend-design`, `presentations`, `documents`, `imagegen`, `figma`, or `react`.1718## Output Expectations1920Return a concrete motivation/trust strategy: what emotion or belief to support, what proof to show, what progress cue to add, what friction to remove, and what manipulative pattern to avoid.2122## Boundaries2324Do not use this skill to justify deceptive urgency, hidden costs, forced continuity, confirmshaming, or other dark patterns. Use `simplify-decisions-recovery` when the main issue is choosing between options or recovering from an error.
amaledtuning