The README. Every entry ships one in a fixed order: install, usage, props, content, tokens and motion. Your agent finds the files and the knobs before it edits a single line.

It follows yours. Entries are plain React 19, TypeScript and Tailwind v4, with no bundler tricks, so your agent drops them into the app you have and keeps your folders and imports.

Yes. Only the interactive parts carry “use client”; the rest renders on the server. Each entry is prerendered and hydrated in a Next.js App Router build before it ships.

Yes. All copy and data sit in one typed content file, apart from the markup. Your agent rewrites the headline and the answers there, and the layout, spacing and states stay untouched.

No. Entries read from one shared kit of color, type and radius tokens and never restyle it. Point the kit at your brand once, and every section your agent adds picks it up.

Then it’s one token to put back. Durations and curves live in the entry’s tokens, not inline in the markup, and the README names each one, so your agent can restore them exactly.

Code, when you want the exact build. The prompt, when your agent should fit the layout to an app it already knows. Both end on the same layout and the same kit tokens.

You do. Anything your agent builds from an entry is yours to ship on your own and client sites under the commercial license. Only reselling the layouts by themselves is ruled out.