A guide for designing or reviewing how people use a digital product, from navigation and screen content to forms, voice flows, and chat. It also covers accessibility and what users see when content is empty, loading, successful, or failing.

Use it to map information structure, user interactions, keyboard or touch behaviour, content guidance, and accessibility needs for web, mobile, desktop, games, command-line tools, voice, or chat.

It turns a feature idea into clear behaviour that developers can build and check. This helps prevent confusing navigation, missing screen states, and inaccessible interactions.

ux-design — Skill for Codex by ashermahonin/agentic-skills

Install

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.

Any agent

npx skills add ashermahonin/agentic-skills --skill ux-design

Clone the repo

git clone --depth 1 https://github.com/ashermahonin/agentic-skills

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/ux-design/github.svg)](https://agentmods.dev/skills/ashermahonin/agentic-skills/ux-design)

Your own site

<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/ux-design"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/ux-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/ux-design"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/ux-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 847 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00069	$0.00847
Opus 5.5	$0.00028	$0.00339
Sonnet 5.5	$0.00014	$0.00169
Haiku 4.5	$0.00007	$0.00085

Measured 2mo ago against content hash 29f0e5dae2b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ux-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 2mo 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.

agentic/skills/ux-design/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UX Design

Purpose

Turn a feature intent into a UX specification that implementation can verify. Cover information structure, interaction, content, accessibility, and the empty, loading, error, success, and permission states that affect the task.

Product context

Read references/ux-spec-template.md.
Pull the platform matrix from platform-detector and the user journeys from user-journey-mapper.
Identify the surface being designed: marketing page, app screen, dashboard, HUD, modal, onboarding, settings, error path, voice flow, chat surface.
Use Context7 MCP for current platform UX guidelines: Apple HIG, Material Design 3, Microsoft Fluent, Web Platform best practices, WCAG, game-engine UI patterns.

Design and validation

Information architecture. Map the surface's content hierarchy: what is primary, secondary, tertiary; what is hidden behind progressive disclosure.
Interaction patterns. Pick patterns from the platform's standard library before inventing new ones. Document every gesture, keyboard binding, focus order, touch target size.
Screen states. For each screen, design every state: default, empty, loading, partial-loading, error (network, validation, permission), success, offline. Skipping a state is a finding.
Micro-copy guidelines. Specify tone, voice, language register, action verbs vs. labels, error message format, confirmation pattern. Coordinate with i18n-localization if the product ships in multiple languages.
Design tokens. Reference or extend the project's design system: color, typography scale, spacing, radius, shadow, motion, sound. Tokens, not hardcoded values.
Accessibility baseline. Set per-surface a11y requirements (WCAG 2.2 AA minimum for web; platform-native a11y APIs for mobile/desktop; HUD readability for games). Hand off to accessibility-audit for verification.
Acceptance criteria. Per surface, write 5–15 checkable criteria the implementation can prove via tdd-workflow or visual regression.
DESIGN.md sync. If the project follows the google-labs-code DESIGN.md convention, update it; otherwise produce or extend the local design contract.

Read the full file on GitHub · 58 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

2mo ago First seen · 58 lines · 69 tokens per session scan A 29f0e5dae2b1

Subscribe to this mod's changes

ux-design is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 847 once invoked, about $0.0003 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-08-31.

Design and UX Frontend

ux-design next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ux-designashermahonin/agentic-skills	Skill	10	2mo ago	MIT	A	69	Codex
webgl-holographic-foilnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	41	Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	53	Claude Code, Codex
html-ppt-taste-brutalistnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	78	Claude Code, Codex
visual-ralphYeachan-Heo/oh-my-codex	Skill	34k	3d ago	MIT	A	52	Codex
glance-canonical-layoutsandroid/skills	Skill	10k	yesterday	Apache-2.0	A	56	Claude Code
accessibilitymicrosoft/hve-core	Skill	1.6k	yesterday	MIT	A	47	Claude Code