メニュー
Normalize Usernode design input into a DS spec. Use for Figma URLs, screenshots, sketches, wireframes, or text briefs before building design-system widgets or screens.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Audit the Usernode agent harness against curated external Flutter, mobile UX, design-system, and agent-skill harnesses. Use when comparing plugins or skills, refreshing the benchmark list, or evaluating whether to adopt outside ideas without losing Usernode identity.
Audit Usernode design-system widgets, screens, or PR changes. Use for verify-widget, screen-audit, PR audit, DS compliance, and mobile UX hard-ban review.
Build or redesign Usernode Flutter screens using Material 3, existing DS components, and mobile UX taste rules. Use for screen-from-design or redesign-existing-screen work.
Build or revise Usernode design-system widgets from normalized design input. Use for DS component work in lib/design_system, including Figma/screenshot/sketch/text-intake pipelines.
Run Usernode Flutter Rust Bridge codegen with the matching upstream flutter_rust_bridge revision. Use when Rust APIs or FRB bindings change.
Bootstrap or repair the Usernode design-system agent harness. Use in this repo when skills, hooks, Claude/Codex discovery adapters, or portable DS agent setup are missing or stale.
| name | usernode-ds-design-intake |
| description | Normalize Usernode design input into a DS spec. Use for Figma URLs, screenshots, sketches, wireframes, or text briefs before building design-system widgets or screens. |
Turn any design input into a normalized implementation artifact for usernode-ds-build-widget or usernode-ds-build-screen.
Write or update lib/design_system/.specs/<Name>.spec.yaml for design-system widget work. For screen work, produce the same fields in the implementation notes or a screen spec if one is useful.
Required fields for design work:
meta:
name: <Name>
input_type: figma | screenshot | sketch | wireframe | text-only
reference: <url-or-path-or-description>
text_only_override: false
intent:
summary: <what the user wants>
scope: widget | screen
target: new | existing
pattern_decision:
operating_mode: <user/session/trust/device context>
chosen_pattern: <M3 or existing DS pattern>
rejected_alternatives:
- pattern: <name>
reason: <why rejected>
uncertainty:
- <known ambiguity, especially for text-only override>
lib/design_system/DESIGN_SYSTEM.md, lib/design_system/docs/CONSTRAINTS.md, and the relevant screen/widget docs.usernode-mobile-ux-taste reasoning before implementation work begins.lib/design_system/.specs/BUILD_INSTRUCTIONS.md.