openprd-frontend-design

To prevent generic frontend interfaces, enforce a design-first framework that prioritizes aesthetic intent, factual accuracy, and structural integrity before writing UI code. This approach uses quality gates and anti-slop rules to ensure high-fidelity, professional-grade visual systems.

The three-direction engine for UI prototyping generates three distinct, heterogeneous design directions using Contrast, Reference Transfer, and Design Lens techniques. This mechanism forces varied aesthetic exploration to avoid safe but hollow AI defaults in component architecture.

Start a professional design plan for a product dashboard by initiating the design starter with specified project context. This locks in the aesthetic direction, theme, and page layout while verifying the design against real-world constraints and brand assets.

Yes, verified product facts are required before building UI component architecture. A Design Asset Contract ensures every interface task is backed by factual product data, brand assets, and clear aesthetic goals to maintain professional design standards.

The best way to avoid default SaaS card stacks in frontend page layout is applying an anti-template framework with rigorous visual quality assurance. This enforces aesthetic intent and structural integrity, guiding the UI away from generic template-heavy outputs.

You should not use automated aesthetic design frameworks for UI development when a project requires highly specialized, non-standard component architecture that cannot pass strict quality gates or adhere to the required Design Asset Contract verification process.