base-headless
MUI Base (unstyled/headless) components and hooks — useButton, useInput, useMenu, useSlider for building custom UI
What this skill does
# MUI Base (Headless/Unstyled) Components
## What is MUI Base?
MUI Base (`@mui/base`) is a library of headless (unstyled) React components and hooks. Unlike Material UI, which ships with Material Design styles baked in, MUI Base provides only the logic, state management, accessibility, and keyboard interactions -- zero CSS. You bring your own styles using Tailwind, CSS Modules, styled-components, vanilla CSS, or any approach you prefer.
```bash
npm install @mui/base
# or
pnpm add @mui/base
```
Key characteristics:
- **Zero default styles** -- components render semantic HTML with no class names or CSS
- **Hooks-first API** -- every component has a corresponding hook (`useButton`, `useInput`, etc.) for maximum flexibility
- **WAI-ARIA compliant** -- accessibility is handled internally (focus management, keyboard navigation, ARIA attributes)
- **Small bundle** -- no theme provider, no emotion/styled-engine dependency
- **Composable** -- hooks return prop-getters (`getRootProps`, `getInputProps`) that you spread onto your own elements
## When to Use MUI Base
| Scenario | Use MUI Base? |
|----------|--------------|
| Building a custom design system (not Material Design) | Yes |
| Integrating with Tailwind CSS or other utility-first CSS | Yes |
| Need maximum control over rendered HTML and styles | Yes |
| Want Material Design out of the box | No -- use Material UI |
| Need a quick prototype with default styling | No -- use Material UI or Joy UI |
| Building a white-label product with multiple brand themes | Yes |
## Core Hooks
### useButton
Provides button behavior including click handling, disabled state, focus-visible detection, and keyboard activation.
```tsx
import { useButton } from '@mui/base/useButton';
import { useRef } from 'react';
import clsx from 'clsx';
interface CustomButtonProps {
children: React.ReactNode;
disabled?: boolean;
onClick?: React.MouseEventHandler;
variant?: 'primary' | 'secondary' | 'ghost';
}
function CustomButton({ children, disabled, onClick, variant = 'primary' }: CustomButtonProps) {
const buttonRef = useRef<HTMLButtonElement>(null);
const { getRootProps, active, disabled: isDisabled, focusVisible } = useButton({
disabled,
rootRef: buttonRef,
});
return (
<button
{...getRootProps({ onClick })}
className={clsx(
'px-4 py-2 rounded-lg font-medium transition-all',
variant === 'primary' && 'bg-blue-600 text-white hover:bg-blue-700',
variant === 'secondary' && 'bg-gray-200 text-gray-800 hover:bg-gray-300',
variant === 'ghost' && 'bg-transparent text-gray-600 hover:bg-gray-100',
active && 'scale-95',
isDisabled && 'opacity-50 cursor-not-allowed',
focusVisible && 'ring-2 ring-blue-400 ring-offset-2',
)}
>
{children}
</button>
);
}
```
**Returned values from `useButton`:**
| Property | Type | Description |
|----------|------|-------------|
| `getRootProps` | `(externalProps?) => props` | Spread onto the root element (button/anchor) |
| `active` | `boolean` | True while the button is being pressed |
| `disabled` | `boolean` | Reflects the disabled state |
| `focusVisible` | `boolean` | True when focused via keyboard (not mouse) |
### useInput
Manages input state including focus, error, and adornment support.
```tsx
import { useInput } from '@mui/base/useInput';
import { useRef } from 'react';
import clsx from 'clsx';
interface CustomInputProps {
placeholder?: string;
value?: string;
onChange?: React.ChangeEventHandler<HTMLInputElement>;
error?: boolean;
disabled?: boolean;
startAdornment?: React.ReactNode;
endAdornment?: React.ReactNode;
}
function CustomInput({
placeholder,
value,
onChange,
error,
disabled,
startAdornment,
endAdornment,
}: CustomInputProps) {
const inputRef = useRef<HTMLInputElement>(null);
const {
getRootProps,
getInputProps,
focused,
error: hasError,
disabled: isDisabled,
} = useInput({
value,
onChange,
error,
disabled,
inputRef,
});
return (
<div
{...getRootProps()}
className={clsx(
'flex items-center gap-2 px-3 py-2 border rounded-lg transition-colors',
focused && 'border-blue-500 ring-1 ring-blue-500',
hasError && 'border-red-500 ring-1 ring-red-500',
isDisabled && 'bg-gray-100 opacity-60',
!focused && !hasError && 'border-gray-300 hover:border-gray-400',
)}
>
{startAdornment}
<input
{...getInputProps()}
placeholder={placeholder}
className="flex-1 outline-none bg-transparent text-sm"
/>
{endAdornment}
</div>
);
}
// Usage
<CustomInput
placeholder="Search..."
startAdornment={<SearchIcon className="w-4 h-4 text-gray-400" />}
endAdornment={<kbd className="text-xs text-gray-400">Ctrl+K</kbd>}
/>
```
**Returned values from `useInput`:**
| Property | Type | Description |
|----------|------|-------------|
| `getRootProps` | `(externalProps?) => props` | Spread onto the wrapper element |
| `getInputProps` | `(externalProps?) => props` | Spread onto the `<input>` element |
| `focused` | `boolean` | True when the input has focus |
| `error` | `boolean` | Reflects the error state |
| `disabled` | `boolean` | Reflects the disabled state |
| `value` | `string` | Current input value (controlled) |
### useMenu / useMenuItem
Build accessible dropdown menus with keyboard navigation, highlight management, and open/close state.
```tsx
import { useMenu } from '@mui/base/useMenu';
import { useMenuItem } from '@mui/base/useMenuItem';
import { useDropdown, DropdownContext } from '@mui/base/useDropdown';
import { useMenuButton } from '@mui/base/useMenuButton';
import { useRef, useState } from 'react';
import clsx from 'clsx';
function MenuButton({ children }: { children: React.ReactNode }) {
const buttonRef = useRef<HTMLButtonElement>(null);
const { getRootProps, active } = useMenuButton({ rootRef: buttonRef });
return (
<button
{...getRootProps()}
className={clsx(
'px-4 py-2 bg-white border rounded-lg shadow-sm hover:bg-gray-50',
active && 'bg-gray-100',
)}
>
{children}
</button>
);
}
function MenuItem({
children,
onClick,
disabled,
}: {
children: React.ReactNode;
onClick?: () => void;
disabled?: boolean;
}) {
const ref = useRef<HTMLLIElement>(null);
const { getRootProps, highlighted, disabled: isDisabled } = useMenuItem({
rootRef: ref,
onClick,
disabled,
});
return (
<li
{...getRootProps()}
className={clsx(
'px-4 py-2 text-sm cursor-pointer transition-colors',
highlighted && 'bg-blue-50 text-blue-700',
isDisabled && 'text-gray-400 cursor-not-allowed',
!highlighted && !isDisabled && 'text-gray-700 hover:bg-gray-50',
)}
>
{children}
</li>
);
}
function Menu({ children }: { children: React.ReactNode }) {
const listboxRef = useRef<HTMLUListElement>(null);
const { getListboxProps, open } = useMenu({ listboxRef });
if (!open) return null;
return (
<ul
{...getListboxProps()}
className="absolute mt-1 w-56 bg-white border rounded-lg shadow-lg py-1 z-50"
>
{children}
</ul>
);
}
// Full dropdown composition
function CustomDropdown() {
const { contextValue } = useDropdown();
return (
<DropdownContext.Provider value={contextValue}>
<div className="relative inline-block">
<MenuButton>Actions</MenuButton>
<Menu>
<MenuItem onClick={() => console.log('Edit')}>Edit</MenuItem>
<MenuItem onClick={() => console.log('Duplicate')}>Duplicate</MenuItem>
<MenuItem disabled>Archive</MenuItem>
<MenuItem onClick={() => console.log('Delete')}>Delete</MenuItem>
</Menu>
</div>
</DropdownContext.Provider>
);
}
```
**Key props from `useMenu`:**
| Property | Type | Description |
|----------|------|-------------|
| `getLisRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.