OODS Foundry

Build your screens from your objects.

A design system tells an assistant what a button looks like. It doesn’t tell it what a subscription is. OODS Foundry starts there. Describe what your product is made of and the traits those things share, name a screen by its object and its context, and your assistant composes it from components that each have a versioned contract and React and Vue implementations.

Talk to us about Object-Oriented Design Systems See it at oods-foundry.com

Free on npm · v0.11.2

Start from the objects.

A subscription has a status, a plan and a renewal date, and a cancelled one shouldn’t offer Cancel. Put that in the object once, and every screen OODS Foundry composes for it starts from the same definition. Traits hold what objects share, so a status or an owner is defined once.

Watch one trait change reach the objects that share it

How it works

  1. Bring in your objects.

    Start with a schema file from your database or API, or write an object in YAML. Review the objects and traits OODS Foundry proposes, then accept what belongs. It checks every definition before adding it.

    See a schema become a Membership workspace

  2. Name the screen.

    Ask for an object and a context, such as a Subscription in detail. OODS Foundry composes it from its catalog.

  3. See it, then ship it.

    Preview it in React and Vue on your machine, then generate the code. Every app comes with a receipt: what was built, what was checked, and what wasn’t.

Keep the system you have.

OODS Foundry extends your design system instead of replacing it. Your tokens become a brand, checked for contrast before anything is written, and you can map the components it ships to your own, so screens compose with yours.

Written for your assistant, too.

It runs on your machine.

OODS Foundry is a local MCP server for Claude Code, Claude Desktop or Cursor. It needs no account and no key, and what it generates for you is yours.

Every page of oods-foundry.com has a Markdown version, and its guide for agents covers the install, what to call first and every tool’s schema. Its hosted endpoint, https://oods-foundry.com/mcp, is read-only, so an assistant can try OODS Foundry before you install anything. If you use Claude, add it as a custom connector.

Two ways to start

Or have us set it up.

Object-Oriented Design Systems: we model your product’s objects and the traits they share, layer them on your existing components and tokens, and set your agents up to build screens from them. Several weeks.

Talk to us

OODS Foundry composes from your definitions and its catalog. It doesn’t interpret arbitrary requests. Generated screens still need your data, your logic and your review.