メニュー
Apply Usernode mobile UX judgment before building or reviewing screens/widgets. Use for pattern decisions, one-handed crypto flows, trust friction, CTA placement, sheets, modals, nav, and hard-ban audits.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | usernode-mobile-ux-taste |
| description | Apply Usernode mobile UX judgment before building or reviewing screens/widgets. Use for pattern decisions, one-handed crypto flows, trust friction, CTA placement, sheets, modals, nav, and hard-ban audits. |
This is the "which pattern" layer. SCREEN_PATTERNS.md and LAYOUT.md explain how to implement the chosen pattern.
Before code, write a pattern_decision block:
Ask the user for a sketch, screenshot, or Figma reference first. If they explicitly override and ask to proceed text-only, record the uncertainty in pattern_decision.uncertainty.
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.
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.
