t1k:designer:ux:ui-wireframe
| Field | Value |
|---|---|
| Module | ux |
| Version | 1.14.5 |
| Effort | high |
| Tools | β |
Keywords: mockup, prototyping, UI design, wireframe
How to invoke
Section titled βHow to invokeβ/t1k:designer:ux:ui-wireframeGame UI Wireframe
Section titled βGame UI WireframeβWhen This Skill Triggers
Section titled βWhen This Skill Triggersβ- Planning a new game screen before Canvas implementation
- Deciding screen layout zones (header, content, action bar, nav)
- Mapping content priority for complex screens (shop, inventory, character select)
- Designing screen-to-screen navigation flow
- Choosing between layout templates (split-panel vs grid vs tab-based)
- Handling portrait/landscape breakpoints or safe area constraints
Does NOT cover:
- HUD during gameplay β
t1k-designer-ux-core - Visual styling, colors, typography β
t1k-designer-ux-visual - Canvas RectTransform implementation β UI framework skills (engine layer)
- Touch target sizes, mobile UX β
t1k-designer-ux-core
Layout Zones (Universal)
Section titled βLayout Zones (Universal)ββββββββββββββββββββββββββββββββββββββ HEADER / TOOLBAR (title, back) β β 60β80px; never scrollsββββββββββββββββββββββββββββββββββββ€β ββ CONTENT AREA β β scrollable; max priorityβ βββββββββββββββββββββββββββββββββββββ€β ACTION BAR (confirm/cancel) β β 80β100px; fixed thumb zoneββββββββββββββββββββββββββββββββββββ€β NAV BAR (tab icons) β β 56β72px; bottommostββββββββββββββββββββββββββββββββββββSafe area rules:
- Top: add OS status bar height (44px portrait iOS, 24px Android)
- Bottom: add gesture bar height (34px iOS, 0px Android with 3-button nav)
- Use the engineβs safe area API; never hardcode offsets
Screen Layout Templates
Section titled βScreen Layout Templatesββ See references/layout-templates.md for full ASCII wireframes + usage rules
| Template | Use Case | Key Trait |
|---|---|---|
| Full-screen menu | Main menu, results, rewards | Single focal CTA; bg art fills screen |
| Split-panel | Inventory, equipment, skill tree | Left list + right detail; 40/60 split |
| Grid gallery | Shop, character select, card collection | Equal cells; sort/filter bar at top |
| Dialog/modal | Purchase confirm, alert, input prompt | Max 60% screen width; dark overlay |
| Tab-based | Settings, player profile, leaderboard | Tab bar below header; content swaps |
Content Priority Mapping
Section titled βContent Priority MappingβBefore placing any element, rank it:
- Primary β playerβs next action (equip button, buy button, start game)
- Context β info needed to make that action (item stats, price, cooldown)
- Secondary β supporting info (flavor text, set bonus, history)
- Tertiary β discoverable (advanced filters, share, report)
Placement rule: Primary β bottom action bar. Context β center content. Secondary β below fold or collapsed. Tertiary β overflow menu.
Anchor Strategy for Responsive UI
Section titled βAnchor Strategy for Responsive UIβ| Element | Anchor Preset | Notes |
|---|---|---|
| Header bar | Top + stretch-horizontal | Sticks to top edge |
| Action bar | Bottom + stretch-horizontal | Sticks to bottom safe area |
| Nav bar | Bottom + stretch-horizontal | Below action bar |
| Content scroll | Stretch all sides | Fills between header and action bar |
| Modal/dialog | Center + fixed size | 320β480px wide; max 80% height |
| Floating button | Bottom-right | 72px from safe area edges |
Use ContentSizeFitter + VerticalLayoutGroup for dynamic content lists.
Screen Flow Patterns
Section titled βScreen Flow Patternsββ See references/screen-flows.md for detailed flow diagrams
Core flows:
- Main menu β Lobby β Game β Results β Rewards β (back to Lobby)
- Shop: Category tabs β Item grid β Item detail sheet β Purchase confirm dialog
- Inventory: Grid overview β Item detail panel β Equip/Use confirm
- Character select: Roster grid β Character detail β Loadout β Confirm
- Settings: Category list β Options panel β Apply/revert confirm
Flow rules:
- Every screen has exactly one back path (Back button or gesture)
- Modals/dialogs always return to the screen that spawned them
- Deep links (notification taps) must resolve to a valid back stack
- Never dead-end: result screens always show a next-step CTA
Portrait / Landscape Breakpoints
Section titled βPortrait / Landscape Breakpointsβ- Portrait primary: design at 1080Γ1920; safe content within 1080Γ1700
- Landscape alternate: reflow to side-by-side panels; move nav bar to left sidebar
- Trigger reflow at aspect ratio < 1.2 (landscape) vs > 1.2 (portrait)
- Test at 16:9, 18:9, 19.5:9, 21:9 (foldables)
Wireframe Notation (ASCII Quick Reference)
Section titled βWireframe Notation (ASCII Quick Reference)β[BTN] = button[ICN] = icon[IMG] = image/avatar[TXT] = text label[---] = divider/separator[///] = background fill / art area[ v ] = dropdown[###] = grid of items (3Γ4, etc.)[scrollβ] = scrollable region beginsUse in doc comments, wiki pages, and plan phase files.
Anti-Patterns
Section titled βAnti-Patternsβ| # | Anti-Pattern | Fix |
|---|---|---|
| 1 | No layout zones defined | Define header/content/action/nav before placing any element |
| 2 | CTA in content scroll area | Move primary actions to fixed action bar |
| 3 | Modal wider than 80% | Cap at 480px or 80vw; center with dark overlay |
| 4 | Ignoring safe area | Always apply Screen.safeArea; never hardcode offsets |
| 5 | Same layout for all screens | Match template to content type (grid β split-panel) |
Cross-References
Section titled βCross-Referencesβt1k-designer-ux-coreβ HUD patterns, mobile touch targets, onboarding flowt1k-designer-ux-visualβ colors, typography, visual language applied to wireframest1k-designer-ux-ui-animationβ transition patterns for screen flows defined here- UI framework skills (auto-activated via registry) β layout, anchors, groups implementation
- engine mobile UI skills (auto-activated via registry) β touch input, gesture, safe area
- engine mobile skills (auto-activated via registry) β platform safe area, orientation APIs
Reference Files
Section titled βReference Filesβ| File | Coverage |
|---|---|
references/layout-templates.md | Full ASCII wireframes for all 5 templates with usage rules |
references/screen-flows.md | Detailed screen-to-screen flow diagrams for core game flows |
Hard rules
Section titled βHard rulesβ- Layout zones survive content; pixel comps donβt β wireframe in zones (header / nav / content / actions) before pixels.
- Anchor strategy must include rotation β portrait-only anchors break on tablet landscape unless explicit fallbacks exist.
- Content priority is a stack, not a grid β the wireframe must answer βwhat must the player see if everything else is off-screen?β