artisign

The design step
in your agentic workflow.

Your coding agent designs the screens through MCP, on a shared design system. You watch it happen in the browser and leave comments. Everything is plain files in your project.

npm install -g artisign
View source

or try it once without installing: npx artisign

Open source · AGPL-3.0 ·
macOS and Linux · Node ≥ 22.4

The artisign Board: every screen of a project as a tile, with click routes drawn between them
The Board of a real project: every screen as a tile, the click routes drawn between them.

Watch one session,
brief to review.

Claude Code runs the design workflow in artisign for a coffee finder app: the brief, design options, a design system, screens, then a review comment in the browser that the agent works through. One recorded session, cut between steps, with captions and music. Under two minutes.

Bring the agent
you already use.

artisign is an MCP server. On first run, artisign offers to connect your AI tool, plus a short skill that teaches it to put the design system first. One connection serves every project.

Create an artisign project in ~/work/acme
artisign · init_project
└ ~/work/acme
artisign · set_tokens
└ color · spacing · typography
artisign · write_html
└ login
artisign · get_screenshot
└ login · look, then adjust
›
artisign Screens view: the screen tree, the rendered dashboard screen and its variant tree
  • Design system first

    The agent reads the tokens and components before it writes, then composes screens from refs.

  • Look at every write

    get_screenshot renders exactly what the preview renders, so the agent checks its own work before you do.

  • Comments become work

    Click an element to comment. The agent picks it up with list_comments and answers with reply_comment.

Connects to Claude Code Claude Desktop Cursor Codex CLI VS Code opencode

One system.
Every screen.

Agents write UI one screen at a time. Without a shared system, each screen re-derives its own greys, spacing and button styles. In artisign, screens reference tokens and components instead of raw values. A rebrand is one set_tokens call.

artisign Design System view: colour tokens as swatches with names and values
  • Refs, not values

    $btn-primary in class is a component ref, $spacing.md in a style value is a token ref.

  • Every variant, side by side

    The Design System view shows token swatches by bucket and every component with every variant.

  • Lift what repeats

    promote_to_system turns an inline value or a repeated element into a token, component or pattern.

One screen.
Every state.

Many screens are another screen in a different state, an overlay on top of it, or a step after it. Variants record that: the sidebar shows each family as a tree, the Board draws it as one cluster, and Compare sets a screen beside its variants and marks what differs.

  • Variant tree

    A breadcrumb and a tree map show where a screen sits in its family.

  • Compare

    The main screen and up to three variants in columns, with a diff overlay for added, changed and removed nodes.

  • Flow mode

    Click an element with a flow target and the preview jumps to the screen it points at.

artisign showing a variant of the dashboard screen, with breadcrumb and the variant tree beside the canvas

Comment on the element.
The agent picks it up.

Click an element to anchor a comment. It is appended to comments.jsonl; the agent reads it with list_comments and answers with reply_comment. Notes carry what a screenshot cannot: states, edge cases, content rules.

artisign with the Context panel and a new comment anchored to a card on the screen, dark theme
  • Anchored to a node

    Comments sit on the element id the agent addresses, not on a pixel position.

  • Follow along

    Follow mode makes the preview track the agent’s tool calls and outline the nodes it touches.

  • Live reload

    Any file change on disk shows up in the browser within about 200 ms.

Light or dark.
Same source.

artisign’s interface comes in a light and a dark theme. The screens themselves render from the same source in both, so preview equals output either way.

artisign Screens view in the dark theme
artisign Screens view in the light theme
Dark Light
The same dashboard screen in both themes.

Runs on your machine.
Keeps nothing to itself.

One Node process on 127.0.0.1. No database, no accounts, no hosting. Your designs are files in your project folder, and they are yours.

Plain files.

Tokens, components, screens, flows and comments are human-readable, diffable files next to your code.

acme/
├── artisign.json
├── design-system/
│   ├── tokens.json
│   └── components/
├── screens/login.html
├── flows.json
└── comments.jsonl

Git is the history.

With autoCommit on, every write becomes one commit named after the tool and its target.

  • write_html:dashboard
  • set_tokens:color.primary
  • set_flow:login

No telemetry. No account.

artisign collects nothing and never fetches a URL on your agent’s behalf. The README lists every request it makes.

  • 127.0.0.1:4711
  • sign-up
  • cloud sync
  • analytics

Open source.

Licensed AGPL-3.0. The licence covers artisign’s own code, not the screens, components or tokens you create with it.

github.com/artisign/artisignAGPL-3.0 · bug reports and ideas welcome

Between the brief
and the code.

The preview renders the source, so what you approve is what the coding agent reads: screens, design system, flows and notes, all addressable by name.

01

Brief

You describe the product to your agent in your AI tool.

02 · artisign

Design

Options as mockups, a design system, screens from refs, flows, your comments.

  • write_mockup
  • set_tokens
  • write_html
  • set_flow
03

Build

The coding agent builds from the reviewed design and its notes.

  • get_screen
  • get_design_system
  • set_meta

Designed with itself.

artisign’s own browser preview is designed in artisign. The design/ folder in the repo is a real project, and the source of the interface at 127.0.0.1:4711.

Browse design/

Questions,
answered.

Anything else? Open an issue on GitHub. Vulnerabilities go through private reporting.

Which AI tools work with artisign?

artisign setup connects Claude Code, Claude Desktop, Cursor, Codex CLI, VS Code and opencode. Other MCP clients can add the same stdio server by hand.

Where do my designs live?

In your project folder, as plain files: tokens, components, screens, flows and comments. With autoCommit on, every write is a git commit.

Do I need an account or an API key?

No. artisign has no accounts and collects nothing: no telemetry, no server beyond the local one it runs. Your agent reaches it over MCP from the AI tool you already use.

Does it run on Windows?

No. artisign needs Node.js 22.4 or later on macOS or Linux. Windows is not supported: the store’s atomic writes and path handling have never been verified there, so npm install refuses the platform.

Is it free and open source?

Yes. artisign is free software under the GNU Affero General Public License, version 3 (AGPL-3.0-only). The licence covers artisign’s own code, not the screens, components, tokens or projects you create with it. The name “artisign” and its logo are not part of the licence.

Can I contribute code?

Not right now. Pull requests are closed without review: artisign is AGPL-3.0-only with a single copyright holder, and outside patches would split that ownership until a DCO or CLA is in place. Bug reports, feature ideas and questions are welcome as GitHub issues.

Give your agent
a design step.

npm install -g artisign
Read the README

Then run artisign and ask: “Create an artisign project in ~/work/acme”