hierarchy rule · warning
single-primary-button
One filled / primary Button per component scope.
What it flags
Demote secondary actions to tinted / plain variants.
Examples
On system
<><Button variant="filled">Save</Button><Button variant="plain">Cancel</Button></>Flagged
<><Button variant="filled">Save</Button><Button variant="filled">Cancel</Button></>How to run it
Run npx windcraft check to run this and the other rules over your project. It ships at warning severity by default, and your AI tools can call it on a snippet over MCP through validate_component_code — so drift is caught as the code is written, not just in review.