ecosystem-integrations
MUI ecosystem — FormEngine, react-jsonschema-form, Uniforms, schema-driven forms, Tailwind interop, Framer Motion, and third-party component libraries
What this skill does
# MUI Ecosystem Integrations
Third-party libraries, schema-driven form builders, styling interop, and animation
integrations that extend MUI's capabilities.
---
## Schema-Driven Form Builders
### FormEngine with MUI
JSON config renders live MUI forms with validation and event wiring.
```bash
npm install @react-form-builder/core @react-form-builder/components-material-ui
```
```tsx
import { FormViewer } from '@react-form-builder/core';
import { view as muiView } from '@react-form-builder/components-material-ui';
const contactForm = {
tooltipType: 'MuiTooltip',
errorType: 'MuiErrorWrapper',
form: {
key: 'Screen',
type: 'Screen',
children: [
{
key: 'name',
type: 'MuiTextField',
props: { label: { value: 'Full Name' } },
schema: { validations: [{ key: 'required' }] },
},
{
key: 'email',
type: 'MuiTextField',
props: { label: { value: 'Email' } },
schema: { validations: [{ key: 'required' }, { key: 'email' }] },
},
{
key: 'role',
type: 'MuiSelect',
props: {
label: { value: 'Role' },
options: { value: [
{ value: 'admin', label: 'Admin' },
{ value: 'user', label: 'User' },
]},
},
},
{
key: 'submit',
type: 'MuiButton',
props: {
children: { value: 'Submit' },
variant: { value: 'contained' },
},
events: {
onClick: [
{ name: 'validate', type: 'common', args: { failOnError: true } },
{ name: 'onSubmit', type: 'custom' },
],
},
},
],
},
};
function DynamicForm() {
return (
<FormViewer
view={muiView}
getForm={() => JSON.stringify(contactForm)}
actions={{
onSubmit: (e) => console.log('Form data:', e.data),
}}
/>
);
}
```
**MUI Components Pack** maps JSON types to real MUI components:
`MuiTextField`, `MuiSelect`, `MuiCheckbox`, `MuiSwitch`, `MuiButton`,
`MuiDialog`, `MuiCard`, `MuiAutocomplete`, `MuiDatePicker`, etc.
**Conditional Rendering** with `renderWhen`:
```json
{
"key": "discountCode",
"type": "MuiTextField",
"props": { "label": { "value": "Discount Code" } },
"renderWhen": { "value": "form.data.hasDiscount === true" }
}
```
### react-jsonschema-form with MUI
JSON Schema → MUI form rendering.
```bash
npm install @rjsf/core @rjsf/mui @rjsf/validator-ajv8
```
```tsx
import Form from '@rjsf/mui';
import validator from '@rjsf/validator-ajv8';
const schema = {
type: 'object',
required: ['name', 'email'],
properties: {
name: { type: 'string', title: 'Full Name' },
email: { type: 'string', title: 'Email', format: 'email' },
age: { type: 'integer', title: 'Age', minimum: 18 },
role: {
type: 'string',
title: 'Role',
enum: ['admin', 'editor', 'viewer'],
enumNames: ['Administrator', 'Editor', 'Viewer'],
},
bio: { type: 'string', title: 'Biography' },
},
};
const uiSchema = {
bio: { 'ui:widget': 'textarea', 'ui:options': { rows: 4 } },
role: { 'ui:widget': 'select' },
'ui:order': ['name', 'email', 'age', 'role', 'bio'],
};
function JsonSchemaForm() {
return (
<Form
schema={schema}
uiSchema={uiSchema}
validator={validator}
onSubmit={({ formData }) => console.log(formData)}
/>
);
}
```
**Custom Widgets and Templates**:
```tsx
const widgets = {
DateWidget: (props) => (
<DatePicker value={dayjs(props.value)} onChange={(d) => props.onChange(d?.toISOString())} />
),
};
const templates = {
ObjectFieldTemplate: (props) => (
<Grid container spacing={2}>
{props.properties.map((prop) => (
<Grid key={prop.name} size={{ xs: 12, md: 6 }}>
{prop.content}
</Grid>
))}
</Grid>
),
};
<Form schema={schema} widgets={widgets} templates={templates} validator={validator} />
```
### Uniforms with MUI Bridge
Multi-schema form engine with pluggable styling bridges.
```bash
npm install uniforms uniforms-bridge-json-schema uniforms-mui
```
```tsx
import { AutoForm, AutoField, SubmitField } from 'uniforms-mui';
import { JSONSchemaBridge } from 'uniforms-bridge-json-schema';
import Ajv from 'ajv';
const ajv = new Ajv({ allErrors: true });
const schema = {
type: 'object',
properties: {
name: { type: 'string' },
email: { type: 'string', format: 'email' },
},
required: ['name', 'email'],
};
const bridge = new JSONSchemaBridge({ schema, validator: ajv.compile(schema) });
<AutoForm schema={bridge} onSubmit={(data) => save(data)}>
<AutoField name="name" />
<AutoField name="email" />
<SubmitField />
</AutoForm>
```
### When to Use What
| Tool | Best For |
|------|----------|
| **FormEngine + MUI** | Admin builders, dynamic forms from metadata, runtime JSON config |
| **react-jsonschema-form + MUI** | JSON Schema-driven forms, API-defined schemas |
| **Uniforms + MUI** | Multi-schema support, rapid prototyping |
| **React Hook Form + MUI** | Hand-coded forms with type-safe validation (Zod) |
| **Formik + MUI** | Legacy projects already using Formik |
---
## Tailwind CSS + MUI Interop
### Using MUI with Tailwind
MUI and Tailwind can coexist. Key: Tailwind's preflight conflicts with MUI's CssBaseline.
**Setup** (`tailwind.config.ts`):
```ts
export default {
// Important: disable preflight to avoid conflicts with CssBaseline
corePlugins: {
preflight: false,
},
// Scope Tailwind to avoid class conflicts
important: '#root', // or use selector strategy
content: ['./src/**/*.{ts,tsx}'],
};
```
**Emotion + Tailwind ordering** — ensure Emotion styles take precedence:
```tsx
import createCache from '@emotion/cache';
import { CacheProvider } from '@emotion/react';
const cache = createCache({
key: 'css',
prepend: true, // Emotion styles inserted BEFORE Tailwind → Tailwind can override
});
<CacheProvider value={cache}>
<ThemeProvider theme={theme}>
<CssBaseline />
<App />
</ThemeProvider>
</CacheProvider>
```
**Using Tailwind classes on MUI components**:
```tsx
// Tailwind classes work alongside sx prop
<Button className="rounded-full shadow-lg" sx={{ px: 4 }}>
Mixed styling
</Button>
// Use Tailwind for layout, MUI for component styles
<Box className="flex items-center gap-4 p-6">
<TextField label="Name" fullWidth />
<Button variant="contained">Save</Button>
</Box>
```
### Base UI + Tailwind (Headless + Utility)
The cleanest integration: Base UI hooks for logic/a11y, Tailwind for all visuals.
```tsx
import { useButton } from '@mui/base/useButton';
import clsx from 'clsx';
function TailwindButton({ children, variant = 'primary', ...props }) {
const { getRootProps, active, disabled, focusVisible } = useButton(props);
return (
<button
{...getRootProps()}
className={clsx(
'rounded-lg px-4 py-2 font-medium transition-all duration-150',
variant === 'primary' && 'bg-blue-600 text-white hover:bg-blue-700 active:bg-blue-800',
variant === 'secondary' && 'bg-slate-200 text-slate-900 hover:bg-slate-300',
disabled && 'opacity-50 cursor-not-allowed',
focusVisible && 'ring-2 ring-blue-400 ring-offset-2',
active && 'scale-95',
)}
>
{children}
</button>
);
}
```
---
## Framer Motion + MUI
### AnimatePresence with MUI Dialog
```tsx
import { AnimatePresence, motion } from 'framer-motion';
import Dialog from '@mui/material/Dialog';
function AnimatedDialog({ open, onClose, children }) {
return (
<AnimatePresence>
{open && (
<Dialog
open={open}
onClose={onClose}
PaperComponent={motion.div}
PaperProps={{
initial: { opacity: 0, scale: 0.9, y: 20 },
animate: { opacity: 1, scale: 1, y: 0 },
exit: { opacity: 0, scale: 0.95, y: -10 },
transition: { type: 'spring', stiffness: 300, damping: 25 },
}}
Related 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.