What is aid-design-ui?

A UI design writer that develops a lasting plan for a screen or user flow, including its structure, interactions, and accessibility considerations.

Use it to plan screens, user journeys, components, interaction behaviour, and accessibility requirements.

It helps clarify how an interface should work before someone builds it, while keeping the design as a reference for implementation.

aid-design-ui — Skill for Claude Code by AndreVianna

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 AndreVianna/aid-methodology --skill aid-design-ui

Clone the repo

git clone --depth 1 https://github.com/AndreVianna/aid-methodology

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/andrevianna/aid-methodology/aid-design-ui/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-ui)

Your own site

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-ui"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-ui/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/andrevianna/aid-methodology/aid-design-ui"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,011 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.00164	$0.01011
Opus 5	$0.00082	$0.00505
Sonnet 5	$0.00033	$0.00202
Haiku 4.5	$0.00016	$0.00101

Measured 8d ago against content hash f8863f8b86d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

aid-design-ui 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 8d 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/aid-design-ui/SKILL.md · 90 lines

How it starts

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

Design UI (develop a design seed, resolve nothing)

Bind VERB=design, ARTIFACT=ui -- the design stage in the contract's vocabulary -- then follow the shared contract at .claude/aid/templates/design-lifecycle.md. This skill binds that contract and restates none of its rules. The seed it writes is .aid/design/ui.md; realizing it into the built component/page is /aid-create-ui's job, not this one's.

Boundary vs /aid-create-ui: that skill builds the UI from a ready seed; this one only develops the seed. Neither resolves anything on its own -- the user decides when a seed is ready to realize.
Boundary vs /aid-prototype-ui: that skill builds a throwaway low-fidelity mock to validate a direction; this one develops a kept design meant to inform the build. Kept vs throwaway is the distinction.
Not a numbered pipeline phase; does not route to /aid-execute.

State machine: INTAKE -> DESIGN -> VERIFY (loop) -> PRESENT [user decides] -> DONE, as design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry line on each state.

State: INTAKE

Require a subject. Empty argument -> ask one bootstrapping question ("What UI screen(s) or flow do you want to design, and what must it support?") and wait.
Allocate through the Work Initiation Gate exactly as the contract's Allocation rule requires (.claude/skills/aid-design/SKILL.md INTAKE step 4 is the shape), with initiator: aid-design-ui. phase is not driven.
Acquire .aid/design/ per the contract, then read .aid/design/ui.md if a prior seed exists -- re-invocation iterates it rather than starting over.
Classify complexity for the aid-architect dispatch (verifier tier >= producer).

Advance: DESIGN.

State: DESIGN

Dispatch aid-architect (clean context, tiered) to write or iterate .aid/design/ui.md in the seed shape the contract fixes (design-seed.md; feature-002 §4), grounded in .aid/knowledge/ and the project source plus any seed read in INTAKE. What this artifact's seed must settle: the screen and flow structure, the interaction model, and accessibility notes; its ## Destination names where the built component/page lands. Never writes .aid/knowledge/ and never writes production code -- the design invariant (design-lifecycle.md).

Read the full file on GitHub · 90 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.

8d ago First seen · 90 lines · 164 tokens per session scan A f8863f8b86d3

Subscribe to this mod's changes

aid-design-ui is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed yesterday), licensed MIT. It adds 164 tokens to every session and 1,011 once invoked, about $0.0008 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

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

aid-design-ui