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.
npx skills add okwinds/miscellany --skill prd-to-uiux-rd-specgit clone --depth 1 https://github.com/okwinds/miscellanyWrote 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/okwinds/miscellany/prd-to-uiux-rd-spec)<a href="https://agentmods.dev/skills/okwinds/miscellany/prd-to-uiux-rd-spec"><img src="https://agentmods.dev/badge/skills/okwinds/miscellany/prd-to-uiux-rd-spec/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/okwinds/miscellany/prd-to-uiux-rd-spec"><img src="https://agentmods.dev/badge/skills/okwinds/miscellany/prd-to-uiux-rd-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00118 | $0.02618 |
| Opus 5 | $0.00059 | $0.01309 |
| Sonnet 5 | $0.00024 | $0.00524 |
| Haiku 4.5 | $0.00012 | $0.00262 |
Grade A, and why
prd-to-uiux-rd-spec 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 10d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD → UI/UX 研发规格(复刻级)交付流程
目标:把“产品 PRD(总纲)”转化为前端可复刻实现的 UI/UX 研发规格文档包(UI 行为、状态机、数据/事件契约、A11y、验收与测试计划),并让目录结构本身就能传达“做到了什么/没做到什么”。
本 skill 的原则:
- 文档先行:先冻结“壳层/公共基座/契约”,再写模块页面细节。
- 目录即证据:打开文件夹即可判断覆盖度与可落地程度(不是散文集)。
- 可演进:对“未来会增减的内容版块”,用契约/模型承接(前端不写死章节)。
- 安全默认:本 skill 默认不改业务代码;若用户要求写代码,先把规格与契约写清,再另起任务实现。
0) 你需要向用户确认的输入(最少集)
- PRD 路径/链接(或最小 PRD 框架)
- 是否存在只读参考基座(例如旧 UI/UX spec、设计系统、竞品稿件);如果有,路径在哪里、是否允许改动
- 前端关键约束(至少选 1 套):
- 图表库(如 ECharts)
- 图标库(如 lucide-react)
- 导出格式(如 PDF 默认、DOCX 权限、Markdown 复制/导出)
- 交付粒度:L1 小改 / L2 新模块 / L3 核心壳层(默认按 L2 交付)
如果缺 PRD:先用 references/output-contract.md 的“PRD 最小骨架”补齐,否则 UI/UX 规格会漂。
1) 输出契约(你必须产出的文件/结构)
默认推荐(可按仓库约定调整路径,但结构不变):
docs/specs/prds/<date>-<slug>-prd.md:产品 PRD(总纲)docs/specs/ui-ux-rd-spec/:UI/UX 研发规格(可复刻落地)DOCS_INDEX.md:仓库级文档索引(路径 + 一句话说明)docs/worklog.md:工作记录(命令 + 决策 + 结果)
docs/specs/ui-ux-rd-spec/ 目录必须包含:
OVERVIEW.md:UI/UX 总纲(能力地图 + TODO + 入口)DOCS_INDEX.md:本目录索引(每份规格文档的入口)00_SourceInventory/:来源/参考/覆盖映射01_Foundation/:公共基座(tokens/布局/交互/A11y/图标/图表等跨模块约束)02_Components/:可复用组件规格(含数据/事件契约)03_Patterns/:跨模块交互模式补充04_Pages/:页面复刻级规格(每页一份,含状态机/验收/测试计划)05_A11y/:A11y 汇总(新增组件/页面的约束)
模板见:
references/uiux-rd-spec-directory-skeleton.mdreferences/page-spec-template.mdreferences/component-spec-template.mdreferences/coverage-template.mdreferences/replica-readiness-checklist.md
2) 工作流(按顺序执行)
Step 0:业务关键契约抽取 Gate(防“模板化空心”)
风险背景:文档过度模板化会出现“看起来很完整,但缺业务关键契约”的伤害。
本 Gate 的目标:在写 UI/UX 细节前,把“对象/术语/关键流程/权限边界/核心字段”先冻结到可引用的契约里。
最低要求(缺任何一项都不得进入 Step A 的大量产文档阶段):
- 对象与术语(Glossary):至少列出核心对象与关系(
Work/Project/Run/Artifact/...) - 关键流程(Key Flows):每条流程写清“触发→状态机→产物→回流/导出”
- 权限边界(Roles/Permissions):至少写清“默认只读 vs step-up 写入”的规则(若涉及)
- 关键字段口径:成本/耗时/状态等字段的“展示口径”必须能落到字段级(避免后续 UI 争议)
模板(可选):
references/glossary-template.md
Step A:先搭“复刻级骨架”(先让结构自证)
- 创建
ui-ux-rd-spec/并按 skeleton 建好层级与入口文件:OVERVIEW.md:先写约束与导航(不要等写完再补)DOCS_INDEX.md:先登记每个将要出现的模块/页面(可先 stub)
- 如果存在只读参考基座(旧 spec/设计系统):
- 明确只读:在
OVERVIEW.md与00_SourceInventory/写清“引用但不修改” - 目录同构:尽量与只读基座同构,降低“对照成本”
- 明确只读:在
What ships with it
13 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.
- CHANGELOG.md 693 B
- examples/tiny-example.md 692 B
- README.md 2.2 KB
- README.zh-CN.md 2.3 KB
- references/component-spec-template.md 921 B
- references/coverage-template.md 620 B
- references/glossary-template.md 1.2 KB
- references/output-contract.md 1.3 KB
- references/page-spec-template.md 1.9 KB
- references/replica-readiness-checklist.md 1.4 KB
- references/replica-scorecard.md 1.7 KB
- references/uiux-rd-spec-directory-skeleton.md 815 B
- tests/evals_prd-to-uiux-rd-spec.yaml 2.4 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.
- 10d ago First seen · 169 lines · 118 tokens per session scan A 6f73d8bd98cc
prd-to-uiux-rd-spec is a skill published in the GitHub repository okwinds/miscellany (50 stars, last pushed 4mo ago), licensed MIT. It adds 118 tokens to every session and 2,618 once invoked, about $0.0006 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…