Frontend Product UX Planning
Use this skill before visual styling or implementation when the task involves a page, app, dashboard, workflow, landing page, or product surface.
Product surfaces include browser extensions, web apps, desktop/Tauri/Electron or native-WebView surfaces, mobile apps, and Android/Compose screens. The user does not need to say "Frontend Design" when the work is clearly about a user-facing interface.
Workflow
- Define the product job in one sentence.
- Identify the audience, domain, frequency of use, and content density.
- Map the primary workflow, secondary workflows, and handoff actions.
- Choose the first screen by user intent, not by marketing convention.
- List required states: empty, loading, error, success, permission, offline, long-content, and small-screen.
- Define actionability and lifecycle rules: what is visible, enabled, disabled, pending, destructive, or user-only.
- Decide what information must be real, user-provided, or clearly sample.
- Remove filler copy, decorative labels, fake telemetry, and themed wording for standard actions.
- For Product UI Copy handoff, freeze
SURFACE,UI_ROLE,PRODUCT_STATE,USER_JOB,USER_CONSEQUENCE_OR_NEXT_ACTION,NEIGHBORING_VISIBLE_COPY,LOCALE,PROTECTED_MEANING,DISCLOSURE_LEVEL, andLENGTH_OR_VIEWPORT_CONSTRAINT.
Ownership
- Own the P0 product/state contract before visual styling or implementation.
- Distinguish normal user flows from diagnostics, admin-only tools, and developer-only recovery surfaces.
- For visible metrics, rankings, model scores, provenance, and status values, require a durable semantic source; do not let UI styling invent unsupported numbers or priority claims.
- When a UI action will be handed to the user, define the expected next state or the safe user-only boundary so the coordinator can verify reachability.
- Escalate missing product/legal/trust facts rather than letting wording hide them. Product UI Copy may improve expression only after protected meaning is stable.
Output Standard
- Navigation is predictable and supports moving in and out of major views.
- Standard actions use standard labels.
- Screens show meaningful content, not ornamental status text.
- Dashboards and operational tools prioritize scanning, comparison, and repeated action.
- Marketing pages make the product, object, place, or offer visible in the first viewport.
Handoff
After planning, route to:
- the Frontend Design coordinator for delegate selection and admission;
visual-directionfor whole-screen direction;design-system-tokensfor reusable tokens;- the implementation builder only after the coordinator has accepted the product/design contract.