ui-architecture

ui-architecture is a skill for Claude Code from wrg32786/aigent-os. It costs 51 tokens per session (951 once invoked), scanned A, original, MIT.

A UI design specification process for a new screen, component, or design system. It describes the parts, layout, colours, text sizes, interaction states, responsive breakpoints, and motion without writing code.

In plain words
What is it for?
Use it to plan web or app interfaces and give an implementer a precise component and layout reference.
Why use it?
It turns a brief into a shared plan before implementation, reducing unanswered design decisions for the developer.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

Good fit Use it to plan web or app interfaces and give an implementer a precise component and layout reference.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wrg32786/aigent-os/ui-architecture
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 wrg32786/aigent-os --skill ui-architecture
Clone the repo
git clone --depth 1 https://github.com/wrg32786/aigent-os

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.

agentmods badge for ui-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/wrg32786/aigent-os/ui-architecture.svg)](https://agentmods.dev/skills/wrg32786/aigent-os/ui-architecture)
Your own site
<a href="https://agentmods.dev/skills/wrg32786/aigent-os/ui-architecture"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/ui-architecture.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 951 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00951
Opus 5 $0.00026 $0.00476
Sonnet 5 $0.00010 $0.00190
Haiku 4.5 $0.00005 $0.00095

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

Security

Grade A, and why

ui-architecture 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 5d 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.

skills/ui-architecture/SKILL.md · 130 lines

How it starts

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

UI Architecture

You are Iris designing a new UI surface. Output is a specification precise enough for Lyra to implement without design questions.

What this skill does

Take a brief for a new screen, component, or design system and produce a complete visual architecture specification. Covers: component tree, layout grid, color tokens, typography scale, interaction states, responsive breakpoints, and motion plan.

Protocol

Step 1: Confirm scope

Restate the brief in one sentence: "Designing a <component/screen> that , targeting <platform/breakpoints>."

Ask ONE clarifying question if scope is ambiguous. Then design.

Step 2: Produce the architecture spec

## UI Architecture: <surface name>

### Purpose
<One paragraph: what this surface does, who uses it, primary action it enables>

### Component Tree
<surface>
├── <ComponentA>
│   ├── <ChildA1>
│   └── <ChildA2>
├── <ComponentB>
└── <ComponentC>

### Layout Grid
- Columns: <N> (desktop) / <N> (tablet) / <N> (mobile)
- Gutter: <Xpx>
- Margin: <Xpx>
- Max-width: <Xpx>

### Color Tokens
- --color-primary: <hex> (<usage>)
- --color-surface: <hex>
- --color-text-primary: <hex>
- --color-text-secondary: <hex>
- --color-border: <hex>
- --color-accent: <hex>
- <semantic tokens as needed>

### Typography Scale
- --text-xl: <size/weight> (<usage>)
- --text-lg: <size/weight>
- --text-base: <size/weight>
- --text-sm: <size/weight>
- --text-xs: <size/weight>

### Spacing System
Base unit: <8px / 4px>
- --space-xs: <X>px
- --space-sm: <X>px
- --space-md: <X>px
- --space-lg: <X>px
- --space-xl: <X>px

### Interaction States (for interactive components)
| State | Visual change |
|-------|---------------|
| default | |
| hover | |
| focus | |
| active/pressed | |
| disabled | |
| error | |
| loading | |

### Responsive Breakpoints
- mobile: <0–Xpx> — <layout changes>
- tablet: <X–Xpx> — <layout changes>
- desktop: <X+px> — <baseline design>

### Motion Plan
- Page transitions: <duration, easing>
- Component entrances: <duration, easing>
- Micro-interactions: <duration, easing>
- Reduced-motion fallback: <what changes>

### Accessibility
- Focus management: <tab order, focus trap if modal>
- ARIA roles: <landmarks and labels needed>
- Color contrast: all text pairs meet WCAG AA 4.5:1
- Motion: respects prefers-reduced-motion

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

  1. 5d ago First seen · 130 lines · 51 tokens per session scan A de5e45206e6d

Subscribe to this mod's changes

ui-architecture is a skill published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 951 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.