refine
Build data-intensive React applications with Refine. Use when a user asks to create admin panels, dashboards, or CRUD interfaces using Refine with REST, GraphQL, or custom data providers and Ant Design or Material UI.
What this skill does
# Refine — React Framework for Admin Panels
## Overview
You are an expert in Refine, the open-source React framework for building data-intensive applications like admin panels, dashboards, and internal tools. Refine is headless — it provides data fetching, auth, access control, and routing hooks while you choose the UI library (Ant Design, Material UI, Chakra, Mantine, or custom).
## Instructions
### Quick Start
```bash
npm create refine-app@latest my-admin -- \
--ui antd \
--data-provider rest \
--auth-provider custom
cd my-admin && npm run dev
```
### Resource Definition
```tsx
// src/App.tsx — Define CRUD resources
import { Refine } from "@refinedev/core";
import { ThemedLayoutV2 } from "@refinedev/antd";
import dataProvider from "@refinedev/simple-rest";
import routerProvider from "@refinedev/react-router";
function App() {
return (
<Refine
dataProvider={dataProvider("https://api.example.com")}
routerProvider={routerProvider}
resources={[
{
name: "orders",
list: "/orders",
show: "/orders/:id",
edit: "/orders/:id/edit",
create: "/orders/create",
meta: { icon: <ShoppingCartOutlined />, label: "Orders" },
},
{
name: "users",
list: "/users",
show: "/users/:id",
edit: "/users/:id/edit",
meta: { icon: <UserOutlined /> },
},
{
name: "analytics",
list: "/analytics",
meta: { icon: <BarChartOutlined /> },
},
]}
>
<ThemedLayoutV2>
<Routes>
<Route path="/orders" element={<OrderList />} />
<Route path="/orders/:id" element={<OrderShow />} />
<Route path="/orders/:id/edit" element={<OrderEdit />} />
<Route path="/users" element={<UserList />} />
</Routes>
</ThemedLayoutV2>
</Refine>
);
}
```
### List Page with Filtering
```tsx
// src/pages/orders/list.tsx — Auto-generates table with CRUD
import { useTable, useSelect } from "@refinedev/antd";
import { Table, Tag, DatePicker, Select, Space, Button } from "antd";
export const OrderList: React.FC = () => {
const { tableProps, searchFormProps } = useTable({
resource: "orders",
sorters: { initial: [{ field: "created_at", order: "desc" }] },
filters: {
permanent: [{ field: "archived", operator: "eq", value: false }],
},
pagination: { pageSize: 20 },
});
const { selectProps: statusOptions } = useSelect({
resource: "order_statuses",
optionLabel: "name",
optionValue: "value",
});
return (
<Table {...tableProps} rowKey="id">
<Table.Column dataIndex="id" title="Order #" sorter />
<Table.Column dataIndex="customer_email" title="Customer" sorter />
<Table.Column
dataIndex="amount"
title="Amount"
render={(val) => `$${(val / 100).toFixed(2)}`}
sorter
/>
<Table.Column
dataIndex="status"
title="Status"
render={(status) => (
<Tag color={status === "paid" ? "green" : status === "refunded" ? "red" : "blue"}>
{status}
</Tag>
)}
filterDropdown={(props) => <Select {...statusOptions} {...props} />}
/>
<Table.Column dataIndex="created_at" title="Date" render={(d) => new Date(d).toLocaleDateString()} sorter />
<Table.Column
title="Actions"
render={(_, record) => (
<Space>
<ShowButton recordItemId={record.id} size="small" />
<EditButton recordItemId={record.id} size="small" />
</Space>
)}
/>
</Table>
);
};
```
### Data Providers
```typescript
// Refine works with any backend via data providers:
// Built-in: REST, GraphQL, Supabase, Strapi, Appwrite, Hasura,
// NestJS, Airtable, Firebase, Directus, Medusa
// Custom data provider for your API
import { DataProvider } from "@refinedev/core";
export const myDataProvider: DataProvider = {
getList: async ({ resource, pagination, sorters, filters }) => {
const params = new URLSearchParams();
params.set("page", String(pagination?.current ?? 1));
params.set("limit", String(pagination?.pageSize ?? 20));
if (sorters?.[0]) params.set("sort", `${sorters[0].field}:${sorters[0].order}`);
const response = await fetch(`/api/${resource}?${params}`);
const { data, total } = await response.json();
return { data, total };
},
getOne: async ({ resource, id }) => {
const response = await fetch(`/api/${resource}/${id}`);
const data = await response.json();
return { data };
},
create: async ({ resource, variables }) => {
const response = await fetch(`/api/${resource}`, {
method: "POST", body: JSON.stringify(variables),
headers: { "Content-Type": "application/json" },
});
const data = await response.json();
return { data };
},
update: async ({ resource, id, variables }) => {
const response = await fetch(`/api/${resource}/${id}`, {
method: "PATCH", body: JSON.stringify(variables),
headers: { "Content-Type": "application/json" },
});
const data = await response.json();
return { data };
},
deleteOne: async ({ resource, id }) => {
await fetch(`/api/${resource}/${id}`, { method: "DELETE" });
return { data: { id } as any };
},
getApiUrl: () => "/api",
};
```
## Installation
```bash
npm create refine-app@latest # Interactive setup
# Or manually:
npm install @refinedev/core @refinedev/antd @refinedev/react-router
```
## Examples
**Example 1: User asks to set up refine**
User: "Help me set up refine for my project"
The agent should:
1. Check system requirements and prerequisites
2. Install or configure refine
3. Set up initial project structure
4. Verify the setup works correctly
**Example 2: User asks to build a feature with refine**
User: "Create a dashboard using refine"
The agent should:
1. Scaffold the component or configuration
2. Connect to the appropriate data source
3. Implement the requested feature
4. Test and validate the output
## Guidelines
1. **Headless first** — Refine is UI-agnostic; choose Ant Design for speed, Material UI for familiarity, or go fully custom
2. **Data providers for any backend** — Use built-in providers for Supabase, Strapi, Hasura; write a custom one for your API in ~50 lines
3. **Hooks over components** — Use `useTable`, `useForm`, `useShow` hooks for full control; they handle data fetching, pagination, and caching
4. **Access control** — Implement `accessControlProvider` for role-based UI; Refine hides buttons/pages users can't access
5. **Inferencer for prototyping** — Use `@refinedev/inferencer` to auto-generate CRUD pages from API responses; replace with custom pages later
6. **Audit logs** — Enable `auditLogProvider` to track who changed what; critical for internal tools
7. **Real-time updates** — Add `liveProvider` for WebSocket updates; tables refresh when data changes
8. **i18n built-in** — Use `i18nProvider` for multi-language admin panels; Refine handles label translation
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.