Page shell
Sidebar, route header, content rail, proof rail, and footer rhythm.
Wireframes and anatomy
The primitive skeleton layer: page, section, card, control, table, overlay, and mobile wireframes that every visual primitive must inherit before styling.
Production answer
Wireframes and anatomy is a reusable Oak Flats Muffler Men UI primitive with documented states, accessibility expectations, theme behavior, and implementation evidence.
Primary CTAReview Wireframes and anatomy states
Generative search brief
Wireframes and anatomy: The primitive skeleton layer: page, section, card, control, table, overlay, and mobile wireframes that every visual primitive must inherit before styling.
Skeleton contracts
Reusable anatomy before paint
These frames define slots and relationships. They are intentionally plain: visual routes can add carbon, chrome, glass, red paint, or motion only after this anatomy stays intact.
Section band
Kicker/header, body slots, repeated items, and action row.
Card anatomy
Header, media or metric body, state slot, and one command zone.
Control row
Label, value/control, helper state, and right-aligned action.
Data table
Header row, body rows, density, overflow, and empty/fault state.
Overlay focus
Modal/sheet/lightbox frame with title, body, actions, and focus return.
Mobile stack
Top bar, content stack, bottom nav or action sheet, and thumb reach.
Anatomy gates
What every primitive must prove
Header first
Every composition starts with route, section, or card identity before controls.
One action zone
Cards and sections expose one primary command area plus optional secondary text action.
Evidence slot
Operational components reserve space for status, proof, or owner context.
Responsive skeleton
Desktop, tablet, and mobile shapes are declared before downstream styling.