Menu
Plan UX/UI before code. Structured discovery interview to design brief
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Surface deepening opportunities in a codebase — shallow modules, seam leaks, missing locality — and grill through whichever one you pick. Architecture-pattern aware (monolith / distributed / serverless).
Reconcile and validate all documents in the project's docs/ directory
Full-project code audit workflow: audit then fix
Systematic root cause analysis. No fixes without investigation
Principal Engineer persona. Production-first technical judgment
| name | ui-shape |
| description | Plan UX/UI before code. Structured discovery interview to design brief |
/ui-shape [feature] - Plan UX/UI before code. Structured discovery interview → design brief. No code, only thinking.
Ask in natural dialogue, not all at once:
Purpose & Context:
Content & Data:
Design Goals:
Constraints:
Anti-Goals:
Synthesize into structured brief:
1. Feature Summary (2-3 sentences) 2. Primary User Action (the ONE thing) 3. Design Direction (how it should feel, aesthetic approach) 4. Layout Strategy (spatial approach, hierarchy, rhythm) 5. Key States (default, empty, loading, error, success, edge cases) 6. Interaction Model (click, hover, scroll, feedback, flow) 7. Content Requirements (copy, labels, messages, dynamic ranges) 8. Recommended References (which domain references help during implementation) 9. Open Questions (unresolved items for implementer)
Get explicit confirmation. If user disagrees, revisit discovery questions.
The brief guides implementation via any approach. For full discover-then-build in one step, use /ui-craft instead.
