Frontend Design

**Quick judgment** A strong choice when you want highly distinctive, non-generic frontend interfaces and are willing to trade some conventionality for style. It’s optimized for bold, memorable visuals and production-grade code rather than safe, standard UI kits. **Key strengths** - Clear design-thinking framework (purpose, tone, constraints, differentiation) before coding. - Aggressively avoids generic AI aesthetics (fonts, colors, layouts). - Encourages real, working code for modern web stacks with attention to visual details. **Main risks / limitations** - May over-index on visual boldness vs. usability, accessibility, or brand consistency if not explicitly requested. - Complex layouts, heavy motion, and effects can impact performance if not constrained. - Output style can vary significantly between generations; maintaining a unified design system may require manual curation. - Strong bias against common fonts and patterns might conflict with established design systems. **Recommended scenarios** - Creating standout landing pages, marketing sites, or portfolios where memorability and aesthetic impact are top priorities. - Exploring unconventional art-directed interfaces (editorial, brutalist, retro-futuristic, luxury, etc.). - Generating high-fidelity UI concepts to hand off to designers/engineers for refinement. - Less ideal when you need conservative, highly standardized enterprise UI or strict adherence to an existing design system unless you guide it very tightly in the prompt.