No AI features ship in the product today
LiveWhat it does: Reactopia's components, SVG tools, and directory work without any model, agent, or AI provider involved. That is stated plainly so expectations stay accurate.
/ai
AI-related work on Reactopia
Reactopia does not ship model-backed features today. This page lists registry and docs work that helps automated tooling, plus ideas that are only planned. Each item has a status label.
AI today
What already works. Stated plainly: no model-backed features ship in Reactopia today.
AI-ready tooling
What is being rebuilt or added so agents can discover and use Reactopia packages: machine-readable metadata, agent-readable docs, and predictable usage patterns.
Machine-readable component registry
LiveWhat it does: Each component has title, slug, description, tag, and published metadata in a predictable shape so tools can read the registry without scraping pages.
See the registry output →Agent-readable MDX documentation
BetaWhat it does: Docs live next to components as MDX, giving structured examples in a format agents can consume directly.
Read an example →Predictable usage patterns
In developmentWhat it does: One slug, one doc, and copyable source. That pattern is being applied consistently across the library.
Agentic direction
Exploratory ideas only. None of this is implemented yet.
Package discovery for coding agents
PlannedWhat it does: A formal manifest so an agent can find, compare, and install Reactopia packages on its own.
Tool schemas and structured interfaces
PlannedWhat it does: Typed, machine-usable interfaces over Reactopia packages for automated tooling.
Why existing tooling wins with agents
Agents are most reliable with predictable, well-described primitives: a registry they can read, docs they can parse, examples they can copy, and versions they can pin. Reactopia was built that way for humans; the AI work is making the same structure easy to read programmatically, starting with the component registry at /browse.