القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | usernode-ds-build-screen |
| description | 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. |
Use this for feature screens under lib/features/ or DS-backed page surfaces.
Determine target mode: new or existing.
Intake: use usernode-ds-design-intake for design input.
Pattern decision: run usernode-mobile-ux-taste before code.
Read:
lib/design_system/DESIGN_SYSTEM.mdlib/design_system/docs/SCREEN_PATTERNS.mdlib/design_system/docs/LAYOUT.mdlib/design_system/docs/CONSTRAINTS.mdMatch before make:
Responsive and platform fit:
LayoutBuilder or available constraints for adaptive choices; do not branch on hardware type or top-level orientation.MediaQuery.viewInsets patterns.Implement the approved screen with localized strings, providers in feature layers, and no business logic in widgets.
Audit:
bash tool/screen-audit.sh <path/to/screen.dart>
Design work must write a pattern_decision: block before implementation. For
new screen specs, store it in lib/design_system/.specs/<ScreenName>.spec.yaml.
For existing-screen redesigns where a spec file is not useful, include the same
pattern_decision: block in the implementation notes before code changes.
The block must record:
Text-only briefs ask for a sketch/reference first. Proceed text-only only after explicit user override.
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 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.
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.