CompoMo — @ds-mo/ui

Framework-neutral Stencil web components styled with TokoMo tokens. CompoMo ships custom elements plus generated Angular, React, and Vue adapters.

Install

npm install @ds-mo/tokens @ds-mo/icons @ds-mo/ui

Import TokoMo once at the application root:

import '@ds-mo/tokens';
import '@ds-mo/tokens/reset';
import '@ds-mo/tokens/globals';

Use

Custom elements auto-define when their module is imported:

import '@ds-mo/ui/dist/components/ds-button-filled.js';

<ds-button-filled label="Save"></ds-button-filled>

Angular applications should prefer per-component standalone adapters:

import { DsButtonFilled } from '@ds-mo/ui/angular/ds-button-filled';

React applications use the generated wrappers:

import { DsButtonFilled } from '@ds-mo/ui/react';

Vue applications use the generated wrappers:

<script setup lang="ts">
import { DsButtonFilled } from '@ds-mo/ui/vue';
</script>

Install @ds-mo/icons in the consuming application. ds-icon resolves exact canonical IcoMo export names at application bundle time.

Public support surfaces

• @ds-mo/ui/shell — framework-neutral shell contracts.
• @ds-mo/ui/toast — toast manager.
• @ds-mo/ui/utils — generic helpers such as registerIcons.
• @ds-mo/ui/prose.css — renderer-neutral semantic prose styling.
• @ds-mo/ui/control-elevation.css — elevated outer control wrappers.

There is no global component CSS bundle; styles ship with each custom element.

Browser baseline

CompoMo targets the moving Baseline Newly available browser set. Components may use a web-platform feature once it is interoperable across the Baseline core browsers; consumers that retain older browser releases must provide their own fallback or remain on an earlier compatible CompoMo release.

Agent recipes

The package includes the local compomo-mcp executable with generated component metadata and executable Custom Elements, Angular, React, and Vue composition recipes.

# .codex/config.toml
[mcp_servers.compomo]
command = "./node_modules/.bin/compomo-mcp"

Use registry tools when component selection or a composition contract is unclear. API facts come from Stencil metadata; curated intent comes from co-located component agent JSON and executable patterns.

compomo-mcp uses stdio only. It serves the modern 2026-07-28 protocol and the legacy initialize-based revisions through 2025-11-25; clients that support modern discovery should use automatic version negotiation. Legacy serving may be removed only in a future major release after CompoMo's supported MCP hosts no longer require an initialize-based connection.

Documentation

• Storybook introduction and usage
• Framework integration
• v13 migration guide
• Maintainer documentation router
• Repository instructions

Package versions, components, props, events, and exports are intentionally not duplicated here. Read package.json, Storybook, or the generated registry for current facts.