M1rror docs
Everything you need to turn references and your existing code into an approved design system, reviewed screens and a pull request your team merges. Press / or ⌘ K to search.
Start here
Browse by topic
- Getting startedCreate a workspace, start a project and learn the six modes.3 pages
- BoardCollect references, screenshots and notes.1 page
- SystemTokens and components, read from your sources.3 pages
- ScreensEvery screen, every state, every size.2 pages
- CodeYour repository, checked against the system.4 pages
- ReviewPinned comments, guest reviewers and approvals.5 pages
- ShipAn approved release, ready to build.2 pages
- CollaborationMembers, roles and reviewers without an account.3 pages
- IntegrationsGitHub, and coding agents such as Claude Code, Cursor and Codex over MCP.2 pages
- Billing and creditsPlans, seats, usage units and credits.2 pages
- Security and privacyHow your work and your code are protected.2 pages
- Troubleshooting and FAQCommon problems, what the messages mean and answers to frequent questions.2 pages
- Developer docsThe MCP server and its tools, the API and webhooks.3 pages
From the blog
All posts- AI design agents that work from your codebaseWhat an AI design agent needs to improve an existing React app without making it look generic: codebase context, tokens, approval gates and reviewable pull requests.
- Design tokens explained for developersWhat design tokens are, how the W3C DTCG JSON format works, how to name and layer them, and how to turn one token file into CSS variables and TypeScript.
- Designing every state: loading, empty, error (and the ones teams forget)A practical guide to designing loading, empty, error, denied and session-expired states in React, with accessible patterns, code examples and a checklist.