AGENT INTEGRATION

Build with an AI agent

Share this site's URL to provide the catalogue, source, and integration rules.
Your agent can choose a component and download the files.

Start with this prompt

01 / HANDOFF
Use Flowstage for the interface we are building.

Read llms.txt, registry.json, and agent-skill.md at this site's root. Choose components that fit the task, fetch their actual source files, and follow their integration references.

Download the source into the project. Keep keyboard controls, reduced motion, and cleanup behavior. Verify the result in the target application.

Includes this site's full URL.

The files behind it

02 / SOURCE
llms.txt

Where to start and what to fetch next.

 registry.json

Source paths, anatomy, tokens, and supported states.

 agent-skill.md

Installation, adaptation, and verification instructions.

 flowkit-starter.html

A complete FlowKit example with local source links.

 motion.md

The SVG motion API, controls, and styling reference.

How it works

01

Pick a component

The agent reads registry.json and chooses an item by its behavior. Each record names the files, entrypoint, anatomy, tokens, and states needed to use it.

02

Download its source

Save the listed files in your project. FlowKit uses lib/flowkit.css and lib/flowkit.js; SVG motion uses lib/motion.css and lib/motion.js. UI components list their own files.

03

Mount and adapt

Load the CSS and JavaScript, then call the item's entrypoint. Use the documented tokens to match your interface. The FlowKit starter and motion reference show complete integrations.

04

Check it in context

Verify the layout, keyboard interactions, playback controls, and reduced motion. When removing a FlowKit or motion view, call destroy() to release its listeners and animation.