Choose the right primitive
Use the adapter that fits your application instead of introducing a second interaction model by accident.
7 min read ArchitecturePractical field guides for installing, adapting, and shipping Menace UI with confidence.
Start with installationAdd editable Menace source to an existing shadcn project and verify the result before you customize it.
6 min read Getting started02Change the visual system while keeping names, relationships, focus behavior, and state intact.
10 min read Accessibility03Replace demonstration content, audit local assets, and verify the standalone project before deployment.
12 min read TemplatesUse the adapter that fits your application instead of introducing a second interaction model by accident.
7 min read ArchitectureUse movement to explain state changes, then preserve the same information when motion is reduced.
8 min read InteractionSeparate static checks, browser behavior, deployment health, and external delivery into honest proof layers.
9 min read ProductionImplementation index
Install the Aurora Button source, choose a primitive adapter, preserve its token styles, and integrate the component into a React or Tailwind project.
Add keyboard-operable animated tabs to a Next.js route, keep state inside a client boundary, and provide an instant reduced-motion path.
Install and configure the Menace Toast Stack, then verify live announcements, timers, actions, focus behavior, and reduced-motion exits.
Measure animated React components, reduce unnecessary client work, pause offscreen effects, and preserve a usable reduced-motion experience.
Use the shadcn CLI with a Menace UI registry URL, inspect the files and dependencies it adds, and verify the component in your application.
Choose a React Server Component or client component boundary for animated UI based on state, browser APIs, event handling, and shipped JavaScript.
Review a Next.js template for route coverage, responsive behavior, accessibility, performance, dependencies, source ownership, and asset rights.
Adapt installed Menace UI source inside a Tailwind project while preserving component semantics, keyboard behavior, motion fallbacks, and upgrade clarity.
Ready to work from source?