← ClaudeAtlas

product-uilisted

Builds web screens that read as a real product: each screen composed from what production screens of its kind carry (regions, sizes and wording measured on real screens), tokens and wording settled before markup, shadcn/ui on Tailwind v4 or DADS or SmartHR, an OOUI or task-oriented structure chosen at intake, the users recorded and each screen planned (its job, its dominant element, its reading order, its containers) before markup, each container built from a pattern drawn from production design systems and chosen from the brief by a script, a test for whether each user-visible string should exist, text at 14px or more (12px for a short Latin-only run), checks and an independent review. REMOVE mode strips annotations and small text from an existing screen; lookup data answers palette, pairing, style, chart and stack questions. Use for any screen, component or UI wording, and when an interface reads as AI-made. trigger words: 画面, ページ, ランディングページ, ダッシュボード, デザイントークン, AIっぽい, 構成, レイアウト, カードだらけ, 全部カード, 同じ画面, テンプレ感,
tomkd555/product-ui · ★ 0 · Web & Frontend · score 75
Install: claude install-skill tomkd555/product-ui
# product-ui One entry point for building and reworking web interfaces. Each screen is composed from what production screens of its kind carry (`references/real-screens.md`), every design decision lands in `tokens.json` (the colours, the type and the wording), and the result reaches the user once the check scripts and one independent reviewer have passed it. The lookup data and scripts under `scripts/lookup/` and `data/` come from ui-ux-pro-max, adapted to this skill (`THIRD_PARTY_NOTICES.md`). `{SKILL_DIR}` is the absolute path of this skill's directory: `<plugin root>/skills/product-ui` under the plugin, `~/.claude/skills/product-ui` under a manual install. Under the plugin the agents carry the `product-ui:` prefix (`product-ui:review-design-lead`) and the hook registers itself; a manual install uses the bare agent names. The commands say `python`; on macOS and Linux run `python3`. ## Principles 1. **Real screens are the standard.** `references/real-screens.md` records what production screens of each kind carry: their regions, their sizes and their wording, measured on real screens (`research/20261106-real-screens/report.md`). A screen is composed from that record, and a check keeps a threshold only where real screens stay inside it. 2. **A screen ships inside its product.** Every real screen carries its product's header with the logo or the product name, its navigation where the kind has one (a sign-in or sign-up form carries the header alone), and the controls a scree