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-principlesgit 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-principles)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-ux-principles"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-ux-principles/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-principles"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-ux-principles.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.00035 | $0.01579 |
| Opus 5.5 | $0.00014 | $0.00632 |
| Sonnet 5.5 | $0.00007 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
nw-ux-principles 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Principles
Evidence-based UX fundamentals for guiding interface design during requirements gathering. Use to evaluate designs, write better AC, and ask the right questions during discovery.
Nielsen's 10 Usability Heuristics
Apply when reviewing any interface design or writing AC.
| # | Heuristic | Product Owner Action |
|---|---|---|
| 1 | Visibility of system status | Require feedback for every action within 100ms. Status indicators for all async ops. |
| 2 | Match system and real world | Ban internal jargon from UI. Use domain language from user research. |
| 3 | User control and freedom | Every destructive action needs undo or confirmation. Navigation always allows going back. |
| 4 | Consistency and standards | Require design system. Audit for inconsistent terminology across features. |
| 5 | Error prevention | Require input validation, constraints, confirmation for irreversible actions. |
| 6 | Recognition over recall | Prefer dropdowns over free text when options known. Show recent items. Contextual help. |
| 7 | Flexibility and efficiency | Require keyboard shortcuts for frequent actions. Support mouse and keyboard workflows. |
| 8 | Aesthetic and minimalist design | Challenge every UI element: does it serve current task? Remove decorative clutter. |
| 9 | Help with errors | Error messages state what happened, why, and what to do next. No raw error codes. |
| 10 | Help and documentation | Require contextual help (tooltips, inline guidance). Documentation by task, not feature. |
Heuristic Evaluation Questions
For each screen or workflow under review:
- Is system status visible? (loading, saving, errors, success)
- Does language match user's vocabulary?
- Can users undo or escape from any state?
- Are similar things named and behaving consistently?
- Are error-prone situations prevented or confirmed?
- Are options visible rather than requiring recall?
- Are there shortcuts for frequent actions?
- Is every visible element necessary for current task?
- Do error messages explain problem and solution?
- Is contextual help available?
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 · 156 lines · 35 tokens per session scan A feb8d25506c4
nw-ux-principles is a skill published in the GitHub repository nWave-ai/nWave (621 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,579 once invoked, about $0.0001 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.
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…
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.
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.