design-refiner

To turn a vague UI design request into a build-ready brief, use a prompt refinement process that rewrites casual frontend requests using precise terminology while identifying missing aesthetic, technical, and motion details as fill slots.

Documenting missing UX requirements involves identifying absent load-bearing details like stack, scope, and fidelity, then translating them into author-facing fill slots instead of fabricating specifications, ensuring implementation direction remains explicit.

Yes, you can use a design brief refiner for greenfield interface concepts. It processes new interface ideas to provide clearer aesthetic, technical, and verification direction while preserving your original intent and constraints.

Prompt refinement handles implied interaction design techniques by translating casual descriptions into expert terminology, ensuring the resulting UX brief accurately specifies appropriate motion behavior and interaction patterns without executing the requested work.

When refining frontend build requests from reference files, the limitation is that the process strictly rewrites requirements without executing the build, and it will report unresolved design decisions as fill slots rather than inventing missing specifications.