frontend-design
Create working React and Tailwind interfaces that fit the product, preserve explicit constraints, and make the primary task clear. Read only the references relevant to the requested work.
Match the requested scope
For advice, comparison of workflows, or questions about which skill to use, answer without executing those skills. Do not edit files, persist context, create reports, or start an interview. For an explicit review, inspect and report. Implement fixes only when the user requests them or has already authorized them. Reuse prior authorization within its scope.
Context Gathering Protocol
Gather only the context needed for the requested decision. Use this order:
- Reuse the user's current instructions, prior answers, and any direction or creative authority already granted.
- Resolve the target application's context using project context. Read its
.better-react-web-ui.md, applicable parent defaults, matching page brief, and existing design documents. Legacy files are fallback inputs within the same scope. - Inspect the affected code, callers, assets, and existing design system. Treat observed implementation as evidence of the current system, not proof of unstated audience needs.
- Ask only about missing facts that materially change the work. Label reasonable assumptions and proceed with reversible choices within the authorized scope.
For a new design direction, establish the audience, intended task, and brand tone. Under explicit creative delegation, choose and record reasonable assumptions without another approval checkpoint. Never invent user answers or product facts.
For a focused repair, use the relevant code and constraints. Do not require a brand interview before fixing keyboard focus, overflow, or a measured performance defect.