원클릭으로 Manus에서 모든 스킬 실행

usernode-mobile-ux-taste

스타3

포크2

업데이트2026년 6월 11일 13:31

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 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Usernode-Labs

Usernode-Labs/flutter-mobile-app

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Usernode Mobile UX Taste

This is the "which pattern" layer. SCREEN_PATTERNS.md and LAYOUT.md explain how to implement the chosen pattern.

Pattern Decision

Before code, write a pattern_decision block:

operating mode: quick check, setup, transaction, recovery, diagnostics, or exploration;
session shape: glance, step-by-step, interruptible, high-focus;
trust level: normal, elevated, or high trust friction;
device context: one-handed mobile first, small-screen safe;
chosen pattern: root tab, pushed detail, PSL page, sheet, dialog, wizard, inline state;
CTA placement and escape route;
rejected alternatives with one-line reasons.

Usernode Defaults

Transaction, wallet, recovery, identity, and permission flows have high trust friction.
Bottom nav roots should stay predictable and scannable.
Sheets are for bounded, reversible choices; pushed pages are for complex or high-trust work.
Primary CTAs should sit where thumbs can reach them and remain visible with keyboard/insets.
Prefer existing M3 and DS patterns. New patterns need explicit human approval.

Hard Bans

Tap targets under 48dp for interactive controls.
Keyboard-covered primary CTAs.
Content or actions hidden under status/home indicators.
Gesture-only controls without a visible affordance and semantic label.
Icon-only navigation without label/tooltip.
Sheets or modals with no obvious escape route.
New visual patterns created from a screenshot/Figma/text brief without M3/existing-DS gap proof.

Text-Only Input

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.

이 저장소의 다른 Skills

같은 저장소

usernode-agent-harness-audit

Usernode-Labs/flutter-mobile-app

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.

2026-06-123

usernode-ds-audit

Usernode-Labs/flutter-mobile-app

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.

2026-06-123

usernode-ds-build-screen

Usernode-Labs/flutter-mobile-app

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.

2026-06-123

usernode-ds-build-widget

Usernode-Labs/flutter-mobile-app

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.

2026-06-123

usernode-frb-codegen

Usernode-Labs/flutter-mobile-app

Run Usernode Flutter Rust Bridge codegen with the matching upstream flutter_rust_bridge revision. Use when Rust APIs or FRB bindings change.

2026-06-113

usernode-ds-design-intake

Usernode-Labs/flutter-mobile-app

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.

2026-06-113

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.

Usernode Mobile UX Taste

This is the "which pattern" layer. SCREEN_PATTERNS.md and LAYOUT.md explain how to implement the chosen pattern.

Pattern Decision

Before code, write a pattern_decision block:

operating mode: quick check, setup, transaction, recovery, diagnostics, or exploration;
session shape: glance, step-by-step, interruptible, high-focus;
trust level: normal, elevated, or high trust friction;
device context: one-handed mobile first, small-screen safe;
chosen pattern: root tab, pushed detail, PSL page, sheet, dialog, wizard, inline state;
CTA placement and escape route;
rejected alternatives with one-line reasons.

Usernode Defaults

Transaction, wallet, recovery, identity, and permission flows have high trust friction.
Bottom nav roots should stay predictable and scannable.
Sheets are for bounded, reversible choices; pushed pages are for complex or high-trust work.
Primary CTAs should sit where thumbs can reach them and remain visible with keyboard/insets.
Prefer existing M3 and DS patterns. New patterns need explicit human approval.

Hard Bans

Tap targets under 48dp for interactive controls.
Keyboard-covered primary CTAs.
Content or actions hidden under status/home indicators.
Gesture-only controls without a visible affordance and semantic label.
Icon-only navigation without label/tooltip.
Sheets or modals with no obvious escape route.
New visual patterns created from a screenshot/Figma/text brief without M3/existing-DS gap proof.

Text-Only Input

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.