Borrowing it
Nothing to install: this file belongs to h0x91b/dev-3.0. 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/h0x91b/dev-3.0/main/.claude/skills/ux-create-manifest/SKILL.mdgit clone --depth 1 https://github.com/h0x91b/dev-3.0Wrote 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/h0x91b/dev-3.0/ux-create-manifest)<a href="https://agentmods.dev/skills/h0x91b/dev-3.0/ux-create-manifest"><img src="https://agentmods.dev/badge/skills/h0x91b/dev-3.0/ux-create-manifest/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/h0x91b/dev-3.0/ux-create-manifest"><img src="https://agentmods.dev/badge/skills/h0x91b/dev-3.0/ux-create-manifest.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.00058 | $0.02316 |
| Opus 5 | $0.00029 | $0.01158 |
| Sonnet 5 | $0.00012 | $0.00463 |
| Haiku 4.5 | $0.00006 | $0.00232 |
Grade A, and why
ux-create-manifest 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 9d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Create Manifest
You are a principal-level product UX architect creating the project's initial UX architecture bible.
Use this skill when:
- The repository has no
docs/ux/PRODUCT_UX_BIBLE.mdordocs/ux/ux-architecture.yaml. - The existing UX manifest is stale, shallow, or disconnected from the actual app.
- The user asks for a UX bible, UX architecture, product UX manifest, IA manifest, surface model, action taxonomy, or baseline UX audit.
Non-negotiable goal
Create a trustworthy, project-specific UX manifest derived from the current repository. Do not write a generic UX manifesto. Do not invent product features. Every observed fact must cite file paths or code evidence. Every inferred rule must be marked as inferred. Every proposed improvement must be marked as proposed.
Default write scope
You may create or update only UX documentation unless the user explicitly requests implementation changes:
docs/ux/PRODUCT_UX_BIBLE.md(include the glossary as a section here — no separate glossary file)docs/ux/ux-architecture.yamldocs/ux/UX_DECISIONS.md(seeded, kept compact — seeux-principal's decision log diet)
The manifest records placement, architecture, and the project's own deltas — its real token classes, documented exceptions, and any override of a better-* rule. It does NOT restate general craft rules; those belong to better-accessibility, better-colors, better-typography, better-writing, better-layout, and better-ui. A quality-floor section that could have been written about any project is a section to delete.
If the project has a test budget on doc size (dev3: src/bun/__tests__/ux-docs-budget.test.ts), respect it — compact rather than raise it.
Never stamp a generated-looking header on a hand-authored file. No updated_at, no
confidence, no source: derived_from_repository on content a human will keep editing:
those fields go stale within weeks and then invite the next reader to delete the file as a
disposable cache. Say what the file is and let git carry the dates.
What ships with it
9 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.
- references/discovery-protocol.md 1.9 KB
- references/heuristics-and-defaults.md 2.1 KB
- references/manifest-schema.md 2.3 KB
- references/report-format.md 989 B
- references/subagent-briefs.md 2.6 KB
- scripts/ux_inventory.py 8.0 KB runs code
- templates/PRODUCT_UX_BIBLE.md 5.6 KB
- templates/UX_DECISIONS.md 347 B
- templates/ux-architecture.yaml 5.5 KB
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.
- 9d ago First seen · 154 lines · 58 tokens per session scan A 6bbc57715bcd
ux-create-manifest is a skill published in the GitHub repository h0x91b/dev-3.0 (252 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 2,316 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-08-30.
Other skills, from other repositories
ui-mockup
Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.
design-engineering
Apply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an…
ui-review
Retroactive visual audit of UI implementation with 1-4 scoring per dimension.
design-process
Engineering design cycle covering requirements elicitation, specifications writing, constraint identification, iterative prototyping, and design communication. Spans the full loop from problem definition through ideation, analysis, prototyping, testing, and redesign. Includes morphological charts, TRIZ, Pugh matrices…
prototyping-fabrication
CAD fundamentals, 3D printing (FDM/SLA/SLS), CNC machining, workshop skills, rapid prototyping methodology, and testing of physical prototypes. Covers fidelity levels, material selection for prototypes, dimensional tolerancing, assembly planning, and the iterate-test loop. Use when building prototypes, selecting…
household-systems-design
Designing the household as an operating system. Covers room-function mapping, work-triangle analysis, storage topology, utility flow, and the Richards/Beecher lineage that treats the home as an engineered environment rather than a stage set. Use when planning a new kitchen, reorganizing a room, diagnosing friction in…