rome: Skill for Claude Code

.claude/skills/ux-semantics-audit/SKILL.md

ux-semantics-audit is a skill for Claude Code from rome-os/rome. It costs 161 tokens per session (1,907 once invoked), scanned A, original, MIT.

A code-based review of an existing user interface against defined usability rules. It checks interface meaning and behavior in React, JavaScript, TypeScript, HTML, or generated app code.

In plain words
What is it for?
Use it to audit an interface, identify high-confidence UX issues, and produce structured recommendations for fixes.
Why use it?
It turns specific, evidence-backed usability problems into findings that a developer can act on. Each finding must point to the relevant file, lines, and code.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is rome-os/rome's own configuration. It tells Claude Code how to work on rome itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rome configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rome-os/rome. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rome-os/rome/main/.claude/skills/ux-semantics-audit/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rome-os/rome

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 ux-semantics-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/rome-os/rome/ux-semantics-audit/github.svg)](https://agentmods.dev/skills/rome-os/rome/ux-semantics-audit)
Your own site
<a href="https://agentmods.dev/skills/rome-os/rome/ux-semantics-audit"><img src="https://agentmods.dev/badge/skills/rome-os/rome/ux-semantics-audit/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.

agentmods 80×15 button for ux-semantics-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/rome-os/rome/ux-semantics-audit"><img src="https://agentmods.dev/badge/skills/rome-os/rome/ux-semantics-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 161 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,907 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.00161 $0.01907
Opus 5.5 $0.00064 $0.00763
Sonnet 5.5 $0.00032 $0.00381
Haiku 4.5 $0.00016 $0.00191

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

Security

Grade A, and why

ux-semantics-audit 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.

The scan reads SKILL.md. This mod also ships 6 executable files (report/build.mjs, report/postcss.config.mjs, report/prompt.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-semantics-audit/SKILL.md · 115 lines

How it starts

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

UX Audit

Evaluate UI code against a curated set of verifiable UX rules and emit findings a coding agent can directly act on. This is a linter for UX semantics, not an aesthetic critique: the goal is high-precision, evidence-backed findings, not a wall of vague suggestions.

Design philosophy (read this — it shapes every judgment call)

  1. Precision over recall. A false positive costs more than a miss: the consuming coding agent will "fix" a non-problem and degrade the design. When in doubt, don't flag.
  2. No evidence, no finding. Every finding must cite the exact file, line range, and quoted code snippet that demonstrates the violation. If you cannot point at the code, the finding does not exist.
  3. Exceptions are where precision lives. Each rule in references/rules.md has an enumerated exceptions list. Before flagging, check the exceptions. A candidate that matches an exception is a pass, not a "borderline flag."
  4. Severity is trust calibration. block findings are mechanical and near-certain — the agent should fix all of them. warn findings involve judgment — the agent should consider them and may reasonably decline with a reason. Never promote a judgment call to block.
  5. Feedback must be constructive and specific. Every finding includes a concrete suggested fix expressed in terms of the actual code, not a restatement of the rule.

Workflow

Step 1 — Scope the audit

Identify the unit of analysis: the view. A view is a screen, page, route, dialog, drawer, or self-contained form — the thing a user perceives at one time. Enumerate the views in scope:

  • If given a whole repo/directory: find view-level components (pages, routes, dialogs, modals). List them and confirm scope with the user if there are more than ~10.
  • If given a single component/file: that component and its rendered children are the view.
  • If given a screenshot or design description alongside code, the code is the source of truth for findings; the image is context.

Read the full file on GitHub · 115 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. 1mo ago First seen · 115 lines · 161 tokens per session scan A 564665437586

Subscribe to this mod's changes

ux-semantics-audit is a skill published in the GitHub repository rome-os/rome (877 stars, last pushed today), licensed MIT. It adds 161 tokens to every session and 1,907 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

html-artifacts

Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for publishartifact, outputiframe, or slackattachhtml.

langchain-ai/open-swe · 52 tokens

browserwing-executor

Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.

MemTensor/MemOS · 42 tokens

web-design

Penguin visual language for generated web pages and app UIs — GitHub-style simplicity with a single blue accent, light and pure-black dark themes, design tokens, component and chat-interface recipes, plus an opt-in warm paper editorial theme.

Prism-Shadow/penguin-harness · 51 tokens

a2ui

Make a reply easier to read and act on with rich blocks inside ordinary Markdown — a choice the user picks from, a form that collects several answers, a procedure as steps with warnings in place, a callout, a Mermaid diagram, a weather card, a live clock or countdown, a dashboard of gauges for a quota, a budget or a…

Prism-Shadow/penguin-harness · 203 tokens

bento-slides

Create and edit Bento presentations — self-contained .bento.html decks whose document is JSON. Use whenever the user wants a slide deck or presentation: from scratch, from source material, or by improving an existing file.

Prism-Shadow/penguin-harness · 48 tokens

ui-design

Design-quality reference for financial-research visual output: typography, color, composition, and avoiding generic AI aesthetics.

ginlix-ai/LangAlpha · 24 tokens