For teams building UI with AI
Stop re-explaining components.Give AI the rules instead.
Component Forge starts with your target stack, then lets you choose which components AI must build custom and reuse consistently. Export a component contract for Claude, Cursor, ChatGPT, Codex, or your own model so it follows your rules instead of inventing UI every prompt.
Stack first
Start with the component library or markup style AI should actually use.
Custom where it matters
Pick the components AI must build custom instead of falling back to generic defaults.
Rules before prompts
Export a contract your AI tools can follow across new screens and projects.
How it works
One component system, reused everywhere
AI build brief
Build the app using the supplied component contract.
Use approved variants, states, and accessibility rules.
Do not invent new component patterns unless asked.
Output bundleStack-aware
componentforge.jsonReady
component-rules.mdReady
stack adapterReady
Stack selected
shadcn/ui, MUI, Mantine, raw HTML, and more
Custom components
Buttons, forms, nav, tables, overlays, AI states
Rules stay consistent
AI keeps building against the same component rules.
Component Workflow
Choose a stack, mark custom components, export rules AI must obey.
Component Forge starts with the UI stack, then captures which components should be custom and how AI should use them in generated screens.
Stack first
Request Beta AccessThe contract starts where the code starts.
Pick the target stack, select the components AI must build custom, then ship rules that tell agents what to use, what to avoid, and when each component belongs.
1. Target stack
2. Components AI must build custom
Contract preview
AI component rules
Rules are generated for the selected stack and component groups, then exported as files your AI tools can reuse.
Stack
Next/React + shadcn/ui
Contract mode
Custom components first
Selected components
ButtonsFormsNavigationAI States
Use Next/React + shadcn/ui as the implementation target.
Use custom rules for selected component groups before stack defaults.
Do not invent new component patterns when a contract rule exists.
Built for developers and non-developers using AI
Developers can map rules to their stack. Founders and operators can choose the components that matter, then hand the contract to an AI builder without learning every prop or implementation detail.
Reactshadcn/uiMUIMantineHTML + CSS
Files your AI can reference
componentforge.json
component-rules.md
ai-component-prompt.md
stack adapter
How it works
Give AI component rules first, then let it build faster.
The goal is simple: stop re-explaining buttons, forms, tables, dialogs, and states every prompt. Component Forge turns those decisions into files your AI can keep reusing.
01
Choose the stack
Tell Component Forge whether agents should use shadcn/ui, MUI, Mantine, raw HTML, or another target.
02
Select custom components
Pick the buttons, forms, nav, tables, dialogs, and AI patterns that should never be improvised.
03
Point AI at the contract
Tell Claude, Cursor, Codex, or ChatGPT to build against those rules so generated UI stays consistent.