components
MUI core component patterns and best practices
What this skill does
# MUI Core Components Reference
## Input Components
### TextField
The most common form input. Wraps `FormControl`, `InputLabel`, `OutlinedInput`/`FilledInput`/`Input`,
and `FormHelperText` in one component.
```tsx
import TextField from '@mui/material/TextField';
import InputAdornment from '@mui/material/InputAdornment';
// Standard usage
<TextField
label="Email address"
type="email"
variant="outlined" // 'outlined' | 'filled' | 'standard'
size="small" // 'small' | 'medium'
fullWidth
required
value={email}
onChange={(e) => setEmail(e.target.value)}
error={!!emailError}
helperText={emailError || 'We will never share your email'}
InputProps={{
startAdornment: <InputAdornment position="start"><EmailIcon /></InputAdornment>,
}}
inputProps={{ maxLength: 100, 'aria-label': 'email address' }}
/>
// Multiline / textarea
<TextField
label="Description"
multiline
rows={4}
// or: minRows={2} maxRows={8} for auto-grow
fullWidth
/>
```
### Autocomplete
Combines a text input with a dropdown for both free-form and constrained selection.
```tsx
import Autocomplete from '@mui/material/Autocomplete';
import Chip from '@mui/material/Chip';
import CircularProgress from '@mui/material/CircularProgress';
// Static options
<Autocomplete
options={countries}
getOptionLabel={(option) => option.label}
isOptionEqualToValue={(option, value) => option.code === value.code}
value={selectedCountry}
onChange={(_, newValue) => setSelectedCountry(newValue)}
renderInput={(params) => (
<TextField {...params} label="Country" />
)}
/>
// Multiple selection with chips
<Autocomplete
multiple
options={tags}
value={selectedTags}
onChange={(_, newValue) => setSelectedTags(newValue)}
renderTags={(value, getTagProps) =>
value.map((option, index) => (
<Chip label={option} {...getTagProps({ index })} key={option} />
))
}
renderInput={(params) => (
<TextField {...params} label="Tags" placeholder="Add tag" />
)}
/>
// Async / server-side options
const [open, setOpen] = React.useState(false);
const [options, setOptions] = React.useState([]);
const [loading, setLoading] = React.useState(false);
<Autocomplete
open={open}
onOpen={() => { setOpen(true); fetchOptions(); }}
onClose={() => setOpen(false)}
options={options}
loading={loading}
renderInput={(params) => (
<TextField
{...params}
label="Search users"
InputProps={{
...params.InputProps,
endAdornment: (
<>
{loading && <CircularProgress size={20} />}
{params.InputProps.endAdornment}
</>
),
}}
/>
)}
/>
```
### Select
```tsx
import Select from '@mui/material/Select';
import MenuItem from '@mui/material/MenuItem';
import FormControl from '@mui/material/FormControl';
import InputLabel from '@mui/material/InputLabel';
import Checkbox from '@mui/material/Checkbox';
import ListItemText from '@mui/material/ListItemText';
<FormControl fullWidth size="small">
<InputLabel id="role-label">Role</InputLabel>
<Select
labelId="role-label"
label="Role"
value={role}
onChange={(e) => setRole(e.target.value)}
>
<MenuItem value="admin">Administrator</MenuItem>
<MenuItem value="editor">Editor</MenuItem>
<MenuItem value="viewer">Viewer</MenuItem>
</Select>
</FormControl>
// Multiple select with checkboxes
<Select
multiple
value={selectedRoles}
onChange={handleChange}
renderValue={(selected) => (
<Box sx={{ display: 'flex', flexWrap: 'wrap', gap: 0.5 }}>
{selected.map((value) => <Chip key={value} label={value} size="small" />)}
</Box>
)}
>
{roles.map((role) => (
<MenuItem key={role} value={role}>
<Checkbox checked={selectedRoles.includes(role)} />
<ListItemText primary={role} />
</MenuItem>
))}
</Select>
```
### Checkbox, Radio, Switch
```tsx
import Checkbox from '@mui/material/Checkbox';
import Radio from '@mui/material/Radio';
import RadioGroup from '@mui/material/RadioGroup';
import Switch from '@mui/material/Switch';
import FormControlLabel from '@mui/material/FormControlLabel';
// Checkbox with indeterminate state
<Checkbox
checked={allSelected}
indeterminate={someSelected && !allSelected}
onChange={handleSelectAll}
/>
// Radio group
<RadioGroup value={alignment} onChange={(e) => setAlignment(e.target.value)}>
<FormControlLabel value="left" control={<Radio />} label="Left" />
<FormControlLabel value="center" control={<Radio />} label="Center" />
<FormControlLabel value="right" control={<Radio />} label="Right" />
</RadioGroup>
// Switch
<FormControlLabel
control={
<Switch checked={darkMode} onChange={(e) => setDarkMode(e.target.checked)} />
}
label="Dark mode"
/>
```
### Slider and Rating
```tsx
import Slider from '@mui/material/Slider';
import Rating from '@mui/material/Rating';
// Range slider
<Slider
value={priceRange}
onChange={(_, newValue) => setPriceRange(newValue as number[])}
valueLabelDisplay="auto"
min={0}
max={1000}
step={10}
marks={[
{ value: 0, label: '$0' },
{ value: 500, label: '$500' },
{ value: 1000, label: '$1000' },
]}
/>
// Star rating
<Rating
value={rating}
onChange={(_, newValue) => setRating(newValue)}
precision={0.5}
size="large"
/>
```
---
## Display Components
### Typography
```tsx
import Typography from '@mui/material/Typography';
// Semantic element with visual variant
<Typography variant="h1" component="h2">Page title</Typography>
// Caption with ellipsis
<Typography
variant="body2"
color="text.secondary"
noWrap
sx={{ maxWidth: 200 }}
>
Long text that will be truncated
</Typography>
// Paragraph with bottom margin
<Typography variant="body1" gutterBottom>
First paragraph with bottom margin.
</Typography>
```
### Chip
```tsx
import Chip from '@mui/material/Chip';
import Avatar from '@mui/material/Avatar';
<Chip label="Active" color="success" size="small" />
<Chip label="Draft" variant="outlined" onDelete={handleDelete} />
<Chip
avatar={<Avatar alt="User" src="/user.jpg" />}
label="Jane Smith"
onClick={handleClick}
clickable
/>
```
### Avatar and Badge
```tsx
import Avatar from '@mui/material/Avatar';
import AvatarGroup from '@mui/material/AvatarGroup';
import Badge from '@mui/material/Badge';
// Avatar with fallback initials
<Avatar src="/user.jpg" alt="John Doe">JD</Avatar>
// Avatar group with overflow count
<AvatarGroup max={4}>
{users.map((u) => <Avatar key={u.id} src={u.avatar} alt={u.name} />)}
</AvatarGroup>
// Notification badge on icon
<Badge badgeContent={unreadCount} color="error" max={99}>
<NotificationsIcon />
</Badge>
// Online indicator dot
<Badge
overlap="circular"
anchorOrigin={{ vertical: 'bottom', horizontal: 'right' }}
variant="dot"
color="success"
>
<Avatar src="/user.jpg" />
</Badge>
```
### Tooltip
```tsx
import Tooltip from '@mui/material/Tooltip';
<Tooltip title="Delete this item" placement="top" arrow>
<IconButton aria-label="delete"><DeleteIcon /></IconButton>
</Tooltip>
// Tooltip on disabled element (needs a wrapping span)
<Tooltip title="You don't have permission">
<span>
<Button disabled>Restricted action</Button>
</span>
</Tooltip>
```
### Alert
```tsx
import Alert from '@mui/material/Alert';
import AlertTitle from '@mui/material/AlertTitle';
<Alert severity="warning" variant="filled" onClose={handleClose}>
<AlertTitle>Warning</AlertTitle>
Your subscription expires in 3 days.
</Alert>
// severity: 'error' | 'warning' | 'info' | 'success'
// variant: 'standard' | 'filled' | 'outlined'
```
### Table
```tsx
import Table from '@mui/material/Table';
import TableBody from '@mui/material/TableBody';
import TableCell from '@mui/material/TableCell';
import TableContainer from '@mui/material/TableContainer';
import TableHead from '@mui/material/TableHead';
import TableRow from '@mui/material/TableRow';
import Paper from '@mui/material/Paper';
<TableContaiRelated 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.