kham.udom work coreai

CoreAI: design system & toolkit UI

Fluent UIReactStorybookMCPDesign systems
Microsoft article ↗ vsc-ui-react ↗

The team. CoreAI is Microsoft's organization for AI platforms, developer tools, and services, including Microsoft Foundry and Azure Developer Services. On that team I worked on two related projects: the CoreAI Design System for internal Azure Developer Services and related Azure Dev portal apps, and vsc-ui-react for the Foundry Toolkit extension. Accessibility is part of both.

Microsoft Foundry landing page with the headline The AI app and agent factory
fig 1. Microsoft Foundry, one of the CoreAI product surfaces this work supports.

1. CoreAI Design System

Azure Developer Services and related portals already used Fluent 2 / Fluent UI components, but the products still felt like separate houses built from the same bricks: different navigation, create flows, tables, and detail pages. The CoreAI Design System is the shared layer that gives those portals common foundations without forcing every product to look identical.

It builds on the Foundry team's design-system work and targets the Azure-facing portals under CoreAI. The delivery model is for people and for agents: a Figma library for designers working in the usual handoff, and an MCP so coding agents and AI-assisted workflows can pull the same getting-started guidance, usage examples, and pattern documentation. I contribute to the React theme package, Storybook, and that MCP. The theme package and MCP are internal; they are not open source.

I was part of the cross-team v-team of designers and design engineers from Foundry and Azure Developer Services that continues to formalize high-impact pattern guidance for the system. Microsoft has written about that work in Designing product simplicity for the AI era, which names me among the contributors.

  1. Problem. Shared Fluent components were not enough. Independently built portals still reinvented the same product patterns, which customers experience as complexity.
  2. System. A CoreAI-wide framework on Fluent: theme, Storybook, Figma library, and MCP, so humans and agents start from the same foundations.
  3. Adoption. Azure portal teams can install the baseline npm package in a few days when repo access and PR review are available. Public write-up: none of those portals used the package in June 2026; by August more than five had it installed.

2. vsc-ui-react for Foundry Toolkit

Separately, I work with the Foundry Toolkit extension team on vsc-ui-react, the public VS Code-styled Fluent UI library that ships inside that extension (1.2M+ installs). It wraps Fluent UI v9 with Griffel and --vscode-* theme tokens so the extension picks up the editor's light and dark theme. TypeScript, Vite, Storybook, and a prepublishOnly gate of build, typecheck, lint, and Vitest.

My public commits, authored as khamudom, add components on top of Fluent and revise ones already in the set:

  1. New wrappers. Checkbox, Switch, Dialog, Link, SpinButton, Popover, MessageBar, Slider, Badge, Accordion, Divider, Breadcrumb, and Tag. Label was co-authored.
  2. API on components already there. SearchBox gained outline and transparent appearances. TabList gained a primary appearance, then the accent was limited to the selected tab. Button gained a compact height adjustment.

Decisions in vsc-ui-react

decision.api

The wrapper owns the prop

VscSpinButton types readOnly on its own props, pulls it out of the rest object so it does not land on Fluent's root, and passes it to the input slot. A consumer-supplied input slot is merged with that, so the read-only style and the caller's slot can both apply.

decision.focus

Focus trap changes how the example closes

VscPopover builds on Fluent's Popover, with default and brand surfaces from --vscode-* tokens. trapFocus blocks outside-click dismissal, so the Storybook and playground examples are controlled: Cancel and Save call setOpen(false). Those surfaces get accessible names. Link and TabList commits include :focus-visible treatment, and the primary tab accent stays on the selected tab when it is focused.

decision.theme

VS Code tokens, not a forked palette

Surfaces, type, and validation states read the editor's theme variables. The brand popover arrow inherits the surface background, which computes to --vscode-button-background. Motion on the popover surface is disabled in the base styles to match VS Code, and the prop that would turn it back on is a no-op on purpose.

Where it ships

The CoreAI Design System ships into Azure Developer Services and related Azure Dev portal apps through the internal npm package, Storybook, Figma library, and MCP. vsc-ui-react ships in the Foundry Toolkit on the Visual Studio Marketplace.

What transfers

On CoreAI I help build the design system that keeps related Azure Dev portals coherent, including the theme, Storybook, and MCP path so people and agents use the same foundations. On the Toolkit side I put VS Code theme tokens on Fluent, keep wrapper APIs honest, and ship those components with Storybook and tests.

Buttons, seals, links, and the exploded button anatomy in the hero share one accent ink token. Adjust hue, saturation, radius, or edition and every Charm component (plus each diagram layer) re-themes live. Hover the diagram to expand it.

Reset to defaults

This drawer is a ch-dialog, the radios are ch-radio, and every button, card, and badge on this page is a Charm component. The sliders mutate Charm's token layer on :root. Your changes are saved in this browser.