adisinghstudent/anduril
Overview
This skill applies the Anduril design constraints to UI work and reviews files for violations. It enforces a strict, opinionated system focused on sharp geometry, limited accents, accessible primitives, and performance-minded interactions. Use it to validate designs, suggest fixes, and ensure consistency with Anduril conventions.
How this skill works
Invoke the skill to apply Anduril rules to any UI conversation or supply a file to audit. The skill inspects color usage, typography, spacing, components, interaction patterns, animation rules, and accessibility primitives, then reports violations with why they matter and a concrete fix. It highlights semantic misuse (like lime on light backgrounds), missing ARIA on icon buttons, and prohibited patterns (shadows, gradients, rounded corners).
When to use it
- During UI review to enforce Anduril constraints before implementation
- When auditing a component or page file for accessibility and design consistency
- While designing dark-mode-first interfaces that require a strict accent policy
- When establishing a code-ready spec for frontend engineers
- Before merging design-driven changes that might introduce animations or layout shifts
Best practices
- Limit accent color usage to one per view and never use lime on light backgrounds
- Prefer accessible primitives (Radix, React Aria, Base UI) and reuse project primitives first
- Avoid borders, shadows, gradients, glows, and border-radius—use sharp corners and flat surfaces
- Animate only transform and opacity, prefer motion/react, and respect prefers-reduced-motion
- Show contextual errors next to the action and use AlertDialog for destructive operations
Example use cases
- Scan a page file and get a list of Anduril violations with exact code or markup fixes
- Convert a design spec to Anduril-compliant guidance (colors, type, spacing, components)
- Validate accessibility: confirm aria-labels for icon-only buttons and keyboard behaviors
- Check animations to ensure they use only compositor props and respect 200ms limits
- Enforce performance rules like avoiding large backdrop-filters and unnecessary will-change usage
FAQ
No. Anduril forbids lime on light backgrounds; use near-black accents instead.
Are rounded corners or shadows ever allowed?
Never. Anduril mandates sharp corners and no shadows for cards and surfaces.
What animation properties are allowed?
Only compositor properties: transform and opacity. Keep interaction feedback under 200ms and avoid layout animations.
