Build the app, not the plumbing.
64 small packages covering the parts every real app needs and nobody wants to write twice — data grids, spreadsheets, workflow engines, xlsx/pptx/docx writers, Stripe catalogs, feature gating. Install one or take the whole stack; every server capability ships for PHP and Node. Agent-friendly throughout, so you can hand the boring half over and stay in flow.
25 UI packages. Lift any one out.
Not a monolith. Each ships on its own — npm or Packagist — and composes with the rest. Most apps reach for two or three. The companions below take the kit to 64 in total.
Watch an agent work in the surface, not behind it.
When an agent moves a sticky, you see the cursor, the label, and the activity row — it's driving the real surface, not scraping a copy of it.
Real renders. Hover, click, type.
The actual @particle-academy/react-fancy — 199+ primitives, from a button to a full spreadsheet. 28 render live right here; pick any name on the left.
Button
The workhorse button — 18 colors, ghost / circle variants, loading, badge.
Three rules every component lives by.
Purely visual primitives owe only a great authoring surface. Anything stateful or interactive owes both — authorable and inhabitable.
Controlled, not captive
Anything an agent might read or write lives in value + onChange — no internal-only state. State is the contract; the UI just renders it.
Agents are participants
Every interactive surface exposes a register<Surface>Bridge that maps stable handles to MCP tools. Agents drive the component itself, not a DOM scrape of it.
Transport-agnostic
The kit ships zero networking. Your app wires the realtime + relay layer; mutations broadcast AgentActivity so presence, undo, and coaching compose for free.
Two ways to add a component.
npm-install and import, or vendor the source with npx fancy-cli add. PHP packages: composer require. Either way, point your agent at the registry MCP — ui.particle.academy/mcp — and it returns the exact install commands.
There's a plugin for Claude Code and one for Codex — either wires up the hosted registry MCP and bundles skills for architecture, components, design, realtime, SEO and SSR. Any other MCP client drops the hosted server into its config; no API key. Your agent then calls list-components, search-components, and install-instructions against the live registry — no guessing from memory. MCP setup docs →
