Turn a vague product ask into a grounded, shippable design by establishing business semantics and the user task before proposing a surface. Use when scoping a new surface, redesigning an existing one, or deciding what a feature should be.
Tasks
Ground the business model by documenting concepts, roles, states, lifecycle-closing facts, and obligations before diagnosing any surface
Frame the user view model by separating observed evidence from hypotheses, defining lookup objects, attached proof, first scan, and secondary dimensions
Inputs
vague product asks
domain types and state machines
service behavior
permissions
policy
production facts
user evidence
Outputs
evidence map
business model
user-model hypotheses
structural diagnosis
view model
information architecture
scope and open decisions
design spec
Limitations and checks
Not for auditing a built screen (use ux-audit)
Not for choosing visual details (use ux)
Do not create or modify artifacts unless the user asked for a design artifact, prototype, or repository change
Never design from the surface or turn the business model into the information architecture
Do not infer engineering cost from concept existence alone
Confirm proposed top-level sections are user lookup objects, not merely domain or execution nouns like runs, reports, or table names
Verify every not-modeled item is named with its likely cost drivers in the spec rather than silently dropped
Tag anything unsupported by the existing business model with NEW on any mock or prototype
AI Search
Find projects, verify facts, compare options, or turn a complex need into an actionable plan
Try a searchA click only fills the search box; you stay in control