Written brief
Describe the component purpose, content, behavior, and approved variations.
AI for developers
Turn a brief, component, screenshot, or design reference into reviewable React and TypeScript, complete with the editable fields and controls needed by content teams.
Start from the Admin UI or use your preferred AI coding tool with the React Bricks Skill. In both workflows, generation uses your repository context and project conventions.
Flexible inputs
The reference communicates intent. The generated component should still use the tokens, primitives, breakpoints, and conventions of the project where it will live.
Describe the component purpose, content, behavior, and approved variations.
Turn existing React code into a brick with editable content and controlled options.
Use a visible page section as a reference for hierarchy, styling, and responsive intent.
Provide a layout or interface pattern that captures the result you want to build.
Two entry points
Start from the product context in React Bricks, where authorized team leads can propose component changes, or work directly in the repository. Both paths produce code for developers to inspect, adapt, and merge through the usual project workflow.
Admin UI
A marketing or design lead can propose a new brick or request changes to an existing one, such as additional editable fields, variants, or sidebar controls. AI creates a code proposal in the connected repository for developers to review, adapt, and merge.
AI coding tool
Install the React Bricks Skill so your coding assistant receives the product conventions and implementation guidance it needs to create and edit bricks more reliably.
Generation workflow
Identify visual structure, reusable patterns, content fields, variants, and responsive behavior.
Create normal React and TypeScript using the primitives and styling conventions already present in the project.
Define the schema property that maps text, images, links, repeatable items, and approved visual options to props.
Adapt and test the result, then register the brick only when it is ready for editors.
Developer control
Generation shortens the path to a strong first implementation. Your team then applies the same engineering standards used for every other component before registering the brick for editors.
One design system, two workflows
Brick generation helps developers extend the component system. Content generation helps teams use that approved system to produce pages and content faster.
Content and page generation
AI writes into editable fields, selects approved variants, and arranges registered bricks. Marketing teams can then refine the result directly in the visual editor.
Explore content and page generationBrick generation
AI generates React and TypeScript in the project repository. Developers review and register the finished brick, making it available to editors and content generation workflows.
See the complete AI overviewWatch the complete product demo or compare the generated workflow with the manual steps for creating a custom brick.