memi-design Audit Frontend Design
Audit the real source tree before proposing UI changes. Memi's checks are deterministic and file-anchored; no Figma connection or background process is required.
This workflow targets published beta 2.8.0-beta.2. Use npx -y @memi-design/cli@2.8.0-beta.2 --version to verify the exact package; a local memi must report that same version before these recipes run. The independent stable compatibility baseline is 2.7.9. See current release state and known limitations. npm availability alone does not establish native-binary success.
Run The Audit
From the repository root:
memi diagnose . --json --no-write --fail-on none
For UX behavior and visual craft detail, run only the relevant follow-up:
memi ux audit . --json --no-write
memi craft audit . --json --no-write
A supplied screenshot is context, not proof that Memi performed pixel analysis. Use the harness browser or image tools for actual rendered checks. Use memi diagnose . --receipt-only --fail-on none when the output must exclude source content.
Workflow
- Read repository instructions and identify the requested route or component.
- Run
diagnosebefore broad UI edits. - Group findings by user impact, not by checker name.
- Verify each proposed fix against the cited file and local design tokens.
- Implement only fixes relevant to the user's request.
- Re-run the same command and report assessed quality, category coverage, scan omissions, and remaining findings.
Output
Lead with actionable findings:
| Priority | Evidence | Change |
|---|---|---|
| High | path/to/file.tsx:line and rule id |
Specific code-level fix |
Include the command run, before/after score, files changed, and unresolved risks. Never replace source evidence with generic taste advice.