Skip to main content
UI Guides

Search rules

Search all UI Guides rules by name, category, or source

interactions@Ibelick

Use Existing Components First

MUST

MUST: Use the project's existing component primitives before introducing new libraries. Check for existing Button, Dialog, Popover components first.

Before building custom UI, check if an existing component library already solves the problem

Bad

Good

Why it matters

Building UI components from scratch introduces accessibility bugs, inconsistent behavior, maintenance burden, and duplicated effort. The project's own primitives have already been tested, styled, and documented — reach for those before reaching for a new dependency or a hand-rolled component.

References

Built by Gleb Stroganov, design engineer at Evil Martians.

The rules come from other people's skills and guidelines — Vercel, Rauno Freiberg, @Ibelick, impeccable, Emil Kowalski, Tailwind, RAMS — each one credited on the Sources page. The work here is extraction and wiring: every rule is pulled into one corpus, given a good and a bad example you can operate, a MUST/SHOULD/NEVER rule an agent can paste, and a link back to where it came from.