Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add nWave-ai/nWave --skill nw-ux-emotional-designgit clone --depth 1 https://github.com/nWave-ai/nWaveWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nwave-ai/nwave/nw-ux-emotional-design)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-ux-emotional-design"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-ux-emotional-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-ux-emotional-design"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-ux-emotional-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.01351 |
| Opus 5.5 | $0.00016 | $0.00540 |
| Sonnet 5.5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
nw-ux-emotional-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Emotional Design and Delight
Patterns for creating interfaces that feel good to use. Use during discovery to map emotional arcs and during requirements to specify delight moments.
Walter's Hierarchy of User Needs
Four layers satisfied in order (bottom to top):
/\
/ \
/ PL \ 4. PLEASURABLE - Delight, surprise, emotional connection
/------\
/ USABLE \ 3. USABLE - Easy to learn, intuitive, efficient
/----------\
/ RELIABLE \ 2. RELIABLE - Consistent, dependable, no crashes
/--------------\
/ FUNCTIONAL \ 1. FUNCTIONAL - It works, serves its purpose
------------------
Key insight: Delight only works if product is usable. Beautiful animations on buggy, confusing interface make things worse. Invest in foundation before polish.
Applying the Hierarchy in Requirements
- Phase 1 stories: functionality works correctly
- Phase 2 stories: reliability (error handling, edge cases, recovery)
- Phase 3 stories: usability (simplify flows, reduce steps)
- Phase 4 stories: delight (only after above are solid)
Surface Delight vs Deep Delight
Surface Delight (momentary, contextual)
Playful animations | witty microcopy | surprising easter eggs | visually pleasing illustrations
Deep Delight (sustained, holistic)
Interface anticipates user needs | complex tasks feel effortless | users achieve flow state | tool becomes extension of thinking
Prioritization rule: Deep delight generates loyalty and return usage. Surface delight creates momentary reactions but cannot compensate for usability failures. Invest in deep delight first.
Requirements Implications
- "System suggests most likely next action" (deep) is higher priority than "Save button has satisfying animation" (surface)
- Stories reducing steps, anticipating needs, removing friction are delight stories even if they don't feel "fun"
Empty States
Empty states (no data, first use, zero results) are opportunities, not dead ends.
Good Empty State Design
- Explain what will appear when there is content
- Clear call to action to create first item
- Illustration or visual interest making state feel intentional
- Guidance or templates for first-time users
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 139 lines · 39 tokens per session scan A e3b34cf40232
nw-ux-emotional-design is a skill published in the GitHub repository nWave-ai/nWave (620 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,351 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other skills, from other repositories
tdd
Use this skill to practice test-driven development — writing tests before implementation, using tests to drive design, and validating implementation against pre-written tests. Activates when implementing new functionality, refactoring code, or fixing bugs where regression coverage is needed.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
craft-studio
Router for the ArtCraft craft apps (PhotoCraft, VectorCraft, FilmCraft, LightCraft, PdfCraft, EffectCraft, DesignCraft, FigCraft, WordCraft, SoundCraft, DeckCraft, CADCraft, GridCraft) driven headless via pi-craft. Use to choose which app fits a job and run the discover-execute-save-verify loop - "which craft app…
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.