How memi-design/memi works
Memi is a design-intelligence CLI and agent companion: it audits a frontend repository, returns evidence-anchored findings, and provides context for an agent to make and verify changes. The sampled diagnosis engine supports the scan, app-graph construction, and artifact-writing links shown below. Other major README capabilities—frontend briefs, MCP access, Figma evidence, Studio, and research—are represented at their documented subsystem paths; their internal wiring is not inferred from unsampled source.
Main entry points: app-quality/engine.ts Quality Engine · server.ts MCP Server · research/engine.ts Research Engine · bridge.ts Figma Bridge
Components 21
CLI and Agent Entry
- CLI
src/index.ts - Diagnose Command
src/commands/diagnose.ts
Frontend Quality
- Quality Engine
src/app-quality/engine.ts - Source Scanner
src/utils/source-scanner.ts - App Graph
src/app-quality/app-graph.ts - Quality Policy
src/app-quality/policy.ts - Diagnosis Artifacts
src/app-quality/persistence.ts - Score History
src/app-quality/history.ts
Agent Interfaces
- Frontend Brief
src/agents/design-agent-brief.ts - MCP Server
src/mcp/server.ts - Frontend Tools
src/mcp/frontend-tools.ts - Read Tools
src/mcp/read-tools.ts - Studio Runtime
src/studio/server.ts
Design Integrations
- Figma Controller
src/studio/figma-controller.ts - Figma Bridge
src/figma/bridge.ts - Figma Plugin UI
src/plugin/ui/main.ts - Design System
src/engine/core.ts
Research
- Research Engine
src/research/engine.ts - Research Store
- Research Reports
src/research/synthesis.ts
Other components
- Engineer / Agent
Connections 20
- Engineer / Agent → CLI: runs
- CLI → Diagnose Command: dispatches
- Diagnose Command → Quality Engine: invokes
- Quality Engine → Source Scanner: scans sources
- Quality Engine → App Graph: builds graph
- Quality Engine → Quality Policy: applies policy
- Quality Engine → Diagnosis Artifacts: writes findings
- Quality Engine → Score History: appends history
- Engineer / Agent → Frontend Brief: requests context
- Engineer / Agent → MCP Server: connects via stdio
- MCP Server → Frontend Tools: registers
- MCP Server → Read Tools: registers
- Engineer / Agent → Studio Runtime: uses Studio
- Studio Runtime → Figma Controller: handles actions
- Figma Controller → Figma Bridge: calls
- Figma Plugin UI → Figma Bridge: bridges messages
- Figma Bridge → Design System: extracts design data
- Engineer / Agent → Research Engine: runs research
- Research Engine → Research Store: reads and writes
- Research Engine → Research Reports: generates reports