Core concepts

M1rror keeps exploration and decisions apart. You and the agent can change a draft freely; a release freezes it so people can approve exactly what they saw; a build plan turns an approved release into scoped code work. This page explains each idea once, so the rest of the docs can be short.

Workspace and projects

A workspace is your team: its members, roles, billing and integrations. A project is one product, app or brand inside it. Your plan sets how many projects a workspace can have (see plans and seats).

The six modes

Every project has the same six modes. Inside a project the top bar takes the mode's colour.

Board

Board mode A spatial board for references, screenshots, notes, groups and comment pins. An accessible Outline lists everything on the board. References carry their tags, why they matter and the rights you recorded for them. Board docs.

System

System mode Your design system: foundations (colour, type, spacing, corners, shadows, motion), components, icons, saved directions and history. It is versioned, exports to code formats and is what screens and code checks are measured against. System docs.

Screens

Screens mode Screens built from your components, previewed at phone (390 × 844), tablet (768 × 1024) and desktop (1280 × 800) sizes. Each screen has the states real apps need: Default, Loading, Empty, Error, Denied and Session expired. Screens docs.

Code

Code mode Connect a GitHub repository and M1rror reads it to find your components, their variations and design issues, explained in plain words. It can also check pull requests. Scans find components in React, Vue, Angular, Svelte, Astro and Rails ERB, and read tokens from CSS, Sass, Less, Tailwind and token JSON in any stack. Drawing components, importing screens from code and the component rules in pull request checks work with React and React Native. Code docs.

Review

Review mode Releases waiting for review, their comments and the decisions on them, plus the taste check. Review docs.

Ship

Ship mode Build plans, builds and pull requests for approved releases, plus languages and app store screenshots and listings. Ship docs.

Drafts, releases and approvals

• Draft. What you are working on now. Edits, agent suggestions and undo all happen here.
• Release. Send for review freezes the draft as a numbered version. A release never changes: if the design changes, that is a new release and a new review.
• Approval. A reviewer's decision (approve, request changes or comment) with a written reason, recorded against that exact release.
• Build plan. For an approved release, a plan of what code may change: allowed files, files it must never touch, what must not change, and a budget. A person with the Repository role authorises it.
• Pull request. A build produces a branch; opening the draft pull request is a separate, human decision. M1rror never pushes to your default branch and never merges.

People, roles and guests

Members hold roles such as Owner, Administrator, Editor, Reviewer and Viewer, plus optional Billing and Repository roles. Reviewers and viewers are free; editors use seats. People without an account can review through a private guest review link. See members and roles.

The design agent and coding agents

The design agent works inside M1rror on whatever you select. Coding agents you already use, such as Claude Code, Cursor or Codex, can connect to M1rror over MCP to read the approved system and plan, and to draft. Agents never approve, change billing, manage members or open pull requests: those stay with people. Work an agent starts, such as a scan or an image, uses your units or credits like any other. See the design agent and coding agents.

Usage units and credits

Agent and analysis work is paid for in usage units from your plan's monthly allowance, reserved before work starts and settled at what it used. Generating images, vectors and video spends credits instead. See usage units and credits.