Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
Responsive Navigation Collapse turns a frequent interface judgment into an executable constraint before generation.
Collapsing navigation is not hiding every entry; it reorders by task frequency and current location.85%Design Systems Page Patternsresponsive / stabilityFixed-format UI elements need stable dimensions and responsive constraints to avoid shifts or overlap.
Boards, toolbars, counters, and button groups need predefined sizing rules.82%Interaction Responsive Motiontables / responsiveTables support comparison, so responsive behavior must preserve columns, sorting, and key actions.
Turning tables into cards indiscriminately can destroy comparison; choose the pattern by data task.82%Interaction Responsive Motionbreakpoints / responsiveResponsive design should recombine layout relationships at breakpoints instead of scaling everything by viewport.
Scaling type and containers causes unpredictable overflow; recomposition is more stable.82%Interaction Responsive Motionmobile / responsiveMobile is not a smaller desktop; content and actions should restack by task priority.
Small screens need important information, controls, and feedback early without overlap.82%Visual Foundationsgrid / layoutA grid is not decoration; it decides span, alignment, responsive recomposition, and density.
A stable grid reduces ad hoc placement and keeps complex pages structured across viewports.82%