Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/friedbotstudio/baseline/main/.claude/skills/design-ui/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/design-ui)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/design-ui"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/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.
<a href="https://agentmods.dev/skills/friedbotstudio/baseline/design-ui"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/design-ui.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.00126 | $0.03363 |
| Opus 5.5 | $0.00050 | $0.01345 |
| Sonnet 5.5 | $0.00025 | $0.00673 |
| Haiku 4.5 | $0.00013 | $0.00336 |
Grade A, and why
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 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-ui — the impeccable orchestrator
You are the routing layer between workflow phases and the vendored impeccable skill. Phase orchestrators (/tdd Step 6, /chore, /document) and direct user invocations hand you a task_brief; you classify it, translate it to an impeccable recipe, run the recipe step-by-step, persist state for resume, and return a structured Report. Every design move ultimately routes through Skill(impeccable, "<cmd>", "<args>") — you never originate a design artifact yourself.
This skill is first-party and freely editable. The skill it orchestrates (impeccable) is vendored Apache 2.0 and never edited.
Architectural commitments
These are not preferences. They are structural commitments locked by spec docs/specs/design-ui-orchestrator.md and constitutional commitment CLAUDE.md Article X.2:
- You ALWAYS invoke impeccable. Every design move goes through
Skill(impeccable, …). No exceptions, no shortcuts. - You NEVER pick aesthetic direction. Register, palette, type scale, motion vocabulary — all decided inside impeccable's subcommands in main context. You decide which subcommand to invoke, not what design to produce.
- You NEVER write product code. Files under
app/,site-src/,components/,src/— all flow through impeccable's writing subcommands (craft,polish, refines, enhances, fixes). You write only thin glue: state JSON, brief snapshots, audit snapshots. - You ALWAYS classify before acting. A misrouted
task_briefreturns at Stage 0 with one of two terminal states:not_a_design_task(when all surfaces classify as a single non-design lane — pure development or pure copy) with acorrect_lanepointer, ORmixed_brief(when target_files span ≥ 2 lanes per the per-concern rule inreferences/design-vs-development.md) with a structuredlane_splitarray. Design tasks proceed; everything else stops at Stage 0 without invoking impeccable or writing product code.
Mandatory first step
What ships with it
4 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.
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 · 194 lines · 126 tokens per session scan A abe2f5a8ad9c
design-ui is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 126 tokens to every session and 3,363 once invoked, about $0.0005 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-30.
Other skills, from other repositories
cognitive-walkthrough
Deep-dive usability evaluation of specific user tasks. Simulates novice user cognition step-by-step to identify learnability issues, unclear actions, and points of confusion.
don-norman-principles-audit
Evaluate UX/UI using Don Norman's 7 fundamental design principles from The Design of Everyday Things. Audit discoverability, affordances, signifiers, feedback, mapping, constraints and conceptual models.
wcag-accessibility-audit
Comprehensive web accessibility audit using WCAG 2.1/2.2 guidelines. Evaluate compliance across 4 POUR principles (Perceivable, Operable, Understandable, Robust) with A, AA, AAA conformance levels.
nielsen-heuristics-audit
Evaluate UX/UI using Jakob Nielsen's 10 usability heuristics. Comprehensive audit of visibility, control, consistency, error prevention, recognition, flexibility, aesthetics, error recovery, and documentation.
information-architecture-audit
Audit or design the information architecture of a site/app — organization, labeling, navigation, search, content inventory, sitemaps, card sorting and tree testing, with prioritized findings.
ui-design-review
Comprehensive visual design and aesthetics evaluation. Analyzes typography, color, spacing, hierarchy, consistency, branding, and current product-category conventions for polished, professional interfaces.