memi

Memi

The design layer for agentic AI.

Give your coding agent an interface brief before it edits. Memi maps the UI already in your repository, surfaces file-anchored accessibility and design-system risks, and gives you a deterministic check to rerun before merge. Start with the CLI, then add the same gate to every pull request.

Memi Studio is available today; Memi Canvas is currently in development. No account, API key, Figma file, global install, or daemon is required for the first audit.

Start with your next interface · Get Memi Studio · Read the research

Quickstart: find your first interface issue

Run one non-destructive audit in any frontend repository. It needs no account, API key, Figma file, global install, or daemon.

npx -y @memi-design/cli@latest diagnose . --json --no-write --fail-on none

The result carries normalized finding IDs, confidence, provenance, and file:line evidence so an agent can act on a specific finding instead of guessing.

Give the same context to your coding agent:

npx skills add memi-design/memi --skill audit-frontend-design

Then ask:

Audit this frontend before editing it. Prioritize the five changes that will matter most to users, reuse the existing system, and verify the result after the patch.

If Memi catches a real interface issue in your project, share the finding. Real reports are the most useful signal for what to improve next.

Cost and offline operation

Local source diagnosis uses deterministic rules: no model call, API key, or model fee. It checks the repository you provide and returns findings your agent can verify. Installation, CPU time, CI runners, and any agent you choose still have costs. The published research has not established an end-to-end dollar or token savings advantage.

Start with one diagnosis, address the highest-confidence finding, and rerun the same check. Use --agent-context for a bounded file index instead of sending a whole repository to a model. Its routing is heuristic; a smaller context is not proof of a cheaper successful task. --files scopes reported findings without launching Git; it still scans the tree for aggregate statistics.

Published beta: Install the exact 2.8.0-beta.2 package for the 2.8 frontend workflow. Stable remains 2.7.9; the beta is not a stable release. See current release state and known limitations.

The beta2 npm release record identifies its published source and immutable artifact evidence. The beta1 npm release record preserves the earlier release's history; it does not validate beta2. The 2.8 locked default and explicit capability contract do not apply retroactively to 2.7.9.

npx -y @memi-design/cli@2.8.0-beta.2 --version

npx -y @memi-design/cli@2.8.0-beta.2 agent brief . --frontend --intent "Improve this interface" --json

The beta keeps managed security review, SwiftUI parity, and full DesignWorkbench certification explicitly pending. It is not stable or employer-approved. Publication provenance and platform receipts belong to the exact released artifact.

The beta prevents local diagnosis from writing project files by default, keeps paid integrations optional, and requires explicit grants for networking, subprocesses, and source report persistence. An npm install needs registry access; offline first-run claims require the separately verified bundle. See the acceptance ledger, known limitations, and release truth.

The 2.8 frontend workflow: the beta provides a repository-aware frontend brief, four useful locked MCP tools, validated Figma/Paper evidence inputs, and explicit component-reuse conflicts. See the frontend workflow for runnable beta commands and the release plan for remaining gates. Managed independent security scanning and the reviewed-candidate-audit and swiftui-rendered-rerun receipts remain pending for stable. Paper pixel parity is unassessed. Of 158 inventoried CLI paths, 105 remain deferred; broad grants do not enable them. No complete-task dollar or token savings claim is established.

What 2.8 changes for frontend agents

The practical benefit is more useful local evidence and clearer failure signals: a brief identifies an existing component before an agent duplicates it, diagnosis distinguishes unchecked categories from assessed findings, and diagnose --receipt-only provides a separate metadata-only result without persisting a source report. Regression tests also exposed and corrected candidate defects in bounded file reads, malformed event handling, and failure exit codes. Those corrections improve specific behavior; they do not establish universal design quality, security certification, or lower task cost.

Earlier packed results at source 2a6d0e44 are historical evidence for those exact bytes. Later defensive runtime fixes supersede that artifact as a release candidate; each corrected source checkpoint is verified through a separate local package and digest. See the verification record for the source, artifact, and scope of each result. Local candidate receipts remain evidence for their original bytes; they do not replace the published npm record.

The repository remains authoritative for code. Memi supplies evidence; Codex edits and runs the project's actual checks. Existing custom CSS and component systems do not need a shadcn migration. This beta deliberately defers many legacy command paths; it is not yet a drop-in upgrade for every 2.7 workflow.

Put the check on every pull request

Copy examples/github-actions/memi-design.yml into your repository as .github/workflows/memi-design.yml. The starter is pinned to the reviewed public Action commit and gives reviewers:

• a PR check that fails only on newly introduced interface debt;
• a memi-design-health artifact with the human-readable report; and
• SARIF annotations when the repository grants security-events: write.

The workflow does not need an API key or a Memi secret. Fork pull requests still receive the check and report; SARIF upload is skipped automatically when GitHub does not grant that permission.

If you prefer to configure it by hand, the complete GitHub Action guide documents every input, output, permission, and evidence file.

One product layer, three surfaces

See the product

What Memi adds to an agent workflow

Compatible with the shadcn registry and v0 design systems.

Evidence at a glance

The V15 confirmatory audit is a public technical disclosure, not a leaderboard. It separates receipt admission, rendered design quality, functional acceptance, and resource observations.

| 10 complete model-graded matched pairs | Rendered design-quality comparisons that survived the