Clarx measures how safely and efficiently an AI agent can navigate, modify, and verify changes in your repository — across five pillars, 25 rules, with scores that improve over time.
Developers should say what something means, not reconstruct its appearance from utility classes. The API encodes intent, appearance, priority, state, and role.
Color, spacing, weight, and motion still matter — they should be decided in the design system, not improvised again at every callsite.
A good component API is no longer just ergonomic for engineers. It must also be unambiguous to AI tools generating or modifying UI.
Interfaces, platforms, and implementation methods keep changing. The durable layer is meaning. Systems built around intention adapt better than systems built around frozen visual recipes.
Components communicate status, urgency, and the next available action without requiring the user to decode visual language each time.
RENDERED INTERFACEA shared vocabulary — intent, emphasis, role, state — replaces drift between Figma libraries and frontend code.
SHARED VOCABULARYSemantic props are easier for models to use correctly than scattered visual overrides. Intent travels well across abstraction layers.
MACHINE-READABLE INTENTButtons take intent (primary, secondary, destructive), emphasis (high, medium, low), and state (idle, loading, disabled). The system resolves visuals.
“This is destructive.” “This is pending.” “This should be subtle.” Those are the decisions that should live in the API.
Install the CLI, run your first scan, connect to CI.