FAQ

What's a trait?

A capability that several objects share, like being stocked, having a price or moving through states. You define it once, and every object that lists it gets its fields and what it adds to each screen.

Will it use my design system?

Yes: your objects and traits, written in short YAML files; your brand, made from a recipe or from your own colour values; and your own React or Vue components, mapped in place of the ones it ships. It keeps choosing components by rule, so a screen stays governed while it uses yours.

Can I add my own components?

You can replace any of the 114 components it ships with your own React or Vue component, and the generated code imports yours. Adding components beyond those 114 isn't part of 0.10.1.

Isn't this another design-system MCP server?

It is an MCP server, and most design systems ship one now. The difference is what it works from and what comes back. A design-system server usually gives your assistant documentation to follow. OODS Foundry works from your objects and hands back the generated app, with its receipt and its hash.

Is there AI inside it? Will it make things up?

There's no language model inside OODS Foundry. Your assistant is the AI, and it decides what to ask for. OODS Foundry builds by rule, so the same call gives the same bytes. The sample records on its shipped objects' screens come from their object files; it invents none of their values. An object it drafts from your schema gets illustrative sample values, including names, email addresses and record codes, where your schema gives no example. Some fields still use numbered labels.

What does certification cover?

Charts. Certify a chart and you get 4 results with their findings: accessibility equivalence, determinism, contrast and accuracy. A generated app comes with a receipt instead, and the preview records accessibility results from the running page. Each lists what it didn't check.

Can I use it at work? What does it cost?

Yes, and nothing. OODS Foundry is licensed under Apache-2.0: free for any use, including at work. What it generates for you is yours.

Is it open source?

Yes. OODS Foundry is open source under Apache-2.0. The source repository mirrors each release, and the package is on npm.

Which assistants and computers does it work with?

Claude Desktop, Claude Code and Cursor. The package documents the setup for each, and Get started gives it. It runs on macOS or Linux, with Node.js 22.0.0 or newer. Windows is untested.

Is it ready for production?

After 0.4.1 was published, the OODS Foundry team generated an app for every context each object supports, in React and Vue, from the published package, and every one installed, type-checked, built and mounted. It wasn't repeated for 0.10.1. A generated app labels its sample data and the actions you still need to wire up. Each object's page shows its maturity, and only User is marked stable.

How do I know the demos are real?

Every demo shows the calls and the package version that produced it. The package states the quickstart's hashes itself, in quickstart/expected.json. Run the same calls with @oods/foundry 0.10.1 and compare your content hash with the one on the page.

How is this different from Claude Design?

Claude Design is Anthropic's tool for designing with Claude. It turns a described visual into a first version on brand, which you refine and hand off, and it works with your own design system. OODS Foundry is a tool your assistant calls to build screens from your objects, by rule, and it hands you the list of what it checked. They do different jobs, and you can use both.

Why "object-oriented"?

OODS stands for object-oriented design system. A screen starts from the object it's about, like a Warehouse or a Quote, rather than from a pile of components. If you know Object-Oriented UX, the idea is familiar: start from the objects, not the screens. OODS Foundry builds the screens from them.

Who makes it?

OODS Foundry is an aquex.ai product.

What 0.10.1 covers

• Your components replace shipped ones. Adding components beyond the 114 isn't part of 0.10.1.
• Objects compose in 7 fixed contexts: detail, list, form, timeline, card, inline and workflow.
• Rules live inside one object, like which states it can move between. Rules that span objects aren't part of 0.10.1.
• Certification covers charts. Apps get a receipt instead.
• A brand comes from a recipe, from OODS Foundry's own slots filled by you, or from your team's DTCG token file, which keeps the names, aliases and modes it supports once you accept the draft.
• It runs in Claude Desktop, Claude Code and Cursor on macOS and Linux. Windows is untested.
• Each object's page shows its maturity, and only User is marked stable.
• There's no Figma or canvas integration.