A writing tool for creating a UX specification for one mobile screen, user flow, or persistent interface element. The specification records layout, states, transitions, wording, accessibility, platform conventions, and implementation details.

Use it after a PRD is approved to document a screen or flow in a form engineers can implement.

It fills the gap between a product requirements document (PRD), which defines what to build, and code, which implements it.

ux-design — Skill for Claude Code by cenconq25

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 cenconq25/claude-code-app-studio --skill ux-design

Clone the repo

git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

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/cenconq25/claude-code-app-studio/ux-design/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/ux-design)

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/ux-design"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/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/cenconq25/claude-code-app-studio/ux-design"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/ux-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,393 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.00061	$0.02393
Opus 5	$0.00030	$0.01196
Sonnet 5	$0.00012	$0.00479
Haiku 4.5	$0.00006	$0.00239

Measured 6d ago against content hash bc41075e30b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 6d 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.

.claude/skills/ux-design/SKILL.md · 305 lines

How it starts

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

UX Design — Per Screen / Flow

A UX spec sits between the PRD (what the system does) and the implementation (how it looks). It captures: layout, states, transitions, copy, accessibility, platform conventions, and the engineer-facing implementation hooks.

Output: design/ux/<screen-or-flow>.md

Purpose / When to Run

Run when:

A PRD has UI Requirements that need spec-level detail
A specific screen or flow is heading into implementation
A flow crosses two PRDs and needs its own UX spec to bridge them

Examples of UX-spec-worthy targets:

A single screen (home, settings-profile, paywall)
A flow across screens (onboarding-flow, signup-flow)
A persistent HUD element (mini-player, floating-action-button)

Inputs

Screen / flow name (required)
Parent PRD(s) — the skill detects from name or asks
design/design-bible.md (required for tokens)
design/concept.md (for tone)
.claude/docs/technical-preferences.md (for platform conventions)

Outputs

design/ux/<screen-or-flow>.md

Phase 1: Resolve Target

If no name passed, ask:

Prompt: "Which screen or flow are we speccing?"
Free text. Capture as kebab-case for filename.

Detect parent PRD: glob design/prd/*.md, search for the screen name in each. If multiple match, ask which is the parent. If none match, ask:

"No PRD currently mentions this screen. Is this a missing PRD section, or is the screen genuinely new?"

If genuinely new, suggest authoring a PRD first.

Phase 2: Read Context

Read parent PRD (Sections 3 Detailed Requirements, 4 Edge Cases, 8 Accessibility relevant)
Read design/design-bible.md — tokens to reference
Read design/concept.md — tone anchor
Read existing design/ux/*.md for screens that share a flow

Phase 3: Skeleton

Write design/ux/<name>.md:

# UX Spec: <Screen / Flow>

> **Status**: In Design
> **Parent PRD**: design/prd/<system>.md
> **Last Updated**: <date>

## 1. Screen Goal
[To be designed]

## 2. User Flow Context
[To be designed]

## 3. Layout & Composition
[To be designed]

## 4. States
[To be designed]

## 5. Empty / Loading / Error / Offline
[To be designed]

## 6. Transitions & Motion
[To be designed]

## 7. Copy & Tone
[To be designed]

## 8. Accessibility
[To be designed]

## 9. Platform Notes (iOS / Android)
[To be designed]

## 10. Implementation Hooks
[To be designed]

## 11. Open Questions
[To be designed]

Read the full file on GitHub · 305 lines

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.

6d ago First seen · 305 lines · 61 tokens per session scan A bc41075e30b0

Subscribe to this mod's changes

ux-design is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 2,393 once invoked, about $0.0003 per session on Opus 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-03.

Design and UX Planning

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

ux-design