Design System Builder

The Design System Builder (biome id design-system-builder) is a platform-tier biome in which an agent authors a design system with you: HTML components, tokens and architecture docs. Each build is an interactive agent session with a live preview. Chat, files and output stay on that session.

What a user does

  1. Create a build. Creating a design system build provisions its interactive agent session.
  2. Iterate in the session. A planner agent, design-system-builder, delegates the artifacts to specialist agents: html-builder for HTML, CSS and JavaScript artifacts (mockups, landing pages, dashboards, decks, prototypes) and architecture-doc-writer for design documents. The agent writes under deliverables/, and the session serves the HTML live, with no build step. The workspace runs only in an interactive session. A workflow step cannot start it.
  3. Hand off or publish. From a build you can:
    • launch a pipeline run, seeded from the deliverables you select and the agent-authored deliverables/PIPELINE_INTENT.md, which starts a clarification-driven bootstrap and keeps the build active;
    • push selected files or directories to a knowledge-base space, optionally creating the space;
    • publish the authored design system to the template registry as the organisation's. Publishing reads deliverables/xema-design-system.json and nothing else, and proposes publication. Promotion waits on a human answering a decision, so a pending-decision status means the call succeeded.
  4. Manage the build. You can list, rename and archive builds. Archiving ends the interactive session. If a session ends unrecoverably, restart replaces it and keeps the old session id as an audit trail.

Design ideas are searchable. The biome contributes a search result type, design_system_builder_idea, with title, content and tags searchable and org-shared visibility.

What the biome ships

  • Workspace manifests for the planner and the two specialists, plus skills for HTML artifacts, design docs and deliverable structure.
  • A role capability profile for the planner: an interactive agent-session surface with full write access, no repository editing and permission to write to the knowledge base.
  • A service, design-system-builder-api, for the build lifecycle, knowledge-base publication and pipeline handoff. It is available to org and project scopes.

The manifest declares no capabilities of its own. It requires the operations it needs from other services, such as reading an agent session's provisioning status and publishing events.

Previous: ← Apps Next: Document Buddy →