Components, templates, design and tools for agentic work Private alpha · free for now

The library, one command away.

The Baselumen CLI will pull any component, or a whole site template, into your project from the terminal: the same SDF source you see in the library, written in as files you own. It is not released yet. Until it is, an agent connected over MCP reaches the same catalogue.

Browse components Read the docs

In active development

In development

The CLI is in active development, and the baselumen package is not published yet. Until it is, any MCP-capable agent can reach the same tools: connect it by signing in, or create a token under Agents & MCP and give your agent the endpoint shown there.

The commands it will carry. A small, predictable surface.

Sign in once with baselumen login and a token from Agents & MCP. Every command takes --json, and baselumen mcp runs every tool the hosted endpoint offers, the design tools included, as a local MCP server for your agent, plus two that write components and templates straight to disk.

  • Add a component

    Writes the component's source into ./components — one typed .tsx by default. It will not overwrite a file you already have unless you pass --force.

    baselumen add cta

  • List the library

    Prints all 186 components with their category, status and the builds each one ships. Add --category to narrow it.

    baselumen list

  • Search

    Matches against name, slug, description and category, so you can find a component without leaving the terminal.

    baselumen search pricing

  • Pick a build

    html, react, vue or svelte — the same SDF component in the form your project uses. --dir changes where the files land.

    baselumen add hero --surface vue

  • Start from a template

    Scaffolds one of 12 whole-site templates into its own folder: a complete Astro project that also imports into Terminal. baselumen templates lists them.

    baselumen template meridian

  • Brief your coding agent

    Adds a Baselumen section to CLAUDE.md and AGENTS.md in the current folder, so an agent working there knows these commands. Safe to run twice.

    baselumen init

Type a command. Get files you own.

The session as the CLI is being built: log in with a token, ask what it may do, search the catalogue, add a component and scaffold a template. Every line is what its source prints.

  • login checks the token before it saves it.
  • add writes the React build by default, and its stylesheet when it has one.
  • template writes a complete Astro project into its own folder.

Run

Command
  • Every command--json

In active development: the baselumen package is not published yet.

The baselumen CLI as it is being built: every line is what its source prints for the command. Pick a command to run it. The drawing is a terminal session with the baselumen CLI: baselumen login a bl_ token; baselumen whoami; baselumen search "pricing toggle"; baselumen add pricing-toggle; baselumen template meridian. Each command is typed and its output printed under it.

How it works. One source, your files.

  • One source of truth

    The CLI reads the same catalogue as the library, through the hosted MCP endpoint. What you preview there is what lands in your repo. Listing and searching are open on every plan. Fetching source is recorded as a copy: Free fetches the free component set, and Pro and Agency fetch everything.

  • Self-contained output

    Files are written into your project, not installed. You own them and edit them, and nothing changes underneath you on someone else's version bump. Every class carries the sdf- prefix, so nothing collides with yours.

  • Themed by tokens

    Set --sdf-* custom properties once and every one of the 186 components you add inherits your brand — color, radius, and type — through the cascade.

Want the CLI early? Tell us what you're building.

Until the package is published, an agent connected over MCP reaches the same catalogue.

Tell us Connect an agent

In active development: not released yet

Made inTerminal