How do I install the Memoire Design Tooling skill?

Run npx skillmds@latest add memi-design/memoire-design-tooling-8 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Memoire Design Tooling safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Memoire Design Tooling?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Memoire Design Tooling free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Memoire Design Tooling?

memi-design (@memi-design) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memoire Design Tooling by memi-design

Name: Memoire Design Tooling
Rating: 4.5 (4 reviews)
Author: memi-design

Memoire Design Tooling

Use when an OpenClaw workspace task involves UI design, interface craft, Figma, design systems, shadcn/ui, Tailwind, Atomic Design, research synthesis, design audits, component specs, or code generation from design evidence.

memi-design Updated Sep 22, 2026

File contents

Memi Design Tooling

Memi gives coding agents repository-specific interface evidence before they edit UI. Start with the smallest workflow that answers the task; Figma, global installation, and a daemon are optional.

Choose A Workflow

Before reviewing or changing frontend UI: use audit-frontend-design.
Before building from an existing product system: use remember-design-system.
When adding deterministic pull-request gates: use enforce-design-ci.
For native SwiftUI, SwiftData, App Intents, or Apple-platform verification: use build-swiftui-interface.
For Figma, research, scaffolding, registry publishing, or multi-agent work: continue below.

Install one focused skill directly:

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

This skill requires the reviewed 2.8 frontend contract. Check memi --version and npm registry availability first. If the beta is unpublished, use a reviewed local build; after publication, use the exact verified beta version. npm stable remains 2.7.9.

Compact Preflight

memi agent brief . --frontend --intent "<interface task>" --max-bytes 16384 --json

Read cited source files when the bounded brief lacks necessary evidence. Optional --design-evidence design/selected-node.json accepts normalized Figma/Paper data supplied by the harness; missing mappings and verification stay explicit.

Local Checks And MCP

memi diagnose . --json --no-write --fail-on none
memi diagnose . --receipt-only --fail-on none
memi --profile locked mcp start --no-figma

Locked MCP exposes four read tools: prepare_frontend_brief, prepare_design_agent_brief, prepare_apple_design_brief, and diagnose_app_quality. The frontend tool supplies actual repository evidence. Many legacy CLI and write tools remain unavailable; capability grants do not unlock deferred command paths. Keep connector calls, project edits, and browser execution in the harness's reviewed workflow.

Reuse local components and tokens according to the consumer project's conventions. Source-bearing JSON is working context; receipt-only is a separate metadata output. See docs/FRONTEND_WORKFLOW.md for the candidate evidence schema and actual verification flow.

Evidence Contract

Read local instructions and existing product-system files first.
Collect the minimum evidence that can change the implementation.
Cite file:line findings and existing components or tokens.
Make scoped edits.
Re-run the same deterministic checks.
Report commands, artifacts, files changed, and remaining assumptions.

Do not claim visual correctness from source checks alone. When rendered behavior matters, verify the actual route at desktop and mobile viewports.

---name: memoire-design-tooling-8description: Use when an OpenClaw workspace task involves UI design, interface craft, Figma, design systems, shadcn/ui, Tailwind, Atomic Design, research synthesis, design audits, component specs, or code generation from design evidence.license: MIT---# Memi Design ToolingMemi gives coding agents repository-specific interface evidence before they edit UI. Start with the smallest workflow that answers the task; Figma, global installation, and a daemon are optional.## Choose A Workflow- Before reviewing or changing frontend UI: use `audit-frontend-design`.- Before building from an existing product system: use `remember-design-system`.- When adding deterministic pull-request gates: use `enforce-design-ci`.- For native SwiftUI, SwiftData, App Intents, or Apple-platform verification: use `build-swiftui-interface`.- For Figma, research, scaffolding, registry publishing, or multi-agent work: continue below.Install one focused skill directly:```bashnpx skills add memi-design/memi --skill audit-frontend-design```This skill requires the reviewed 2.8 frontend contract. Check `memi --version` and npm registry availability first. If the beta is unpublished, use a reviewed local build; after publication, use the exact verified beta version. npm stable remains 2.7.9.## Compact Preflight```bashmemi agent brief . --frontend --intent "<interface task>" --max-bytes 16384 --json```Read cited source files when the bounded brief lacks necessary evidence. Optional `--design-evidence design/selected-node.json` accepts normalized Figma/Paper data supplied by the harness; missing mappings and verification stay explicit.## Local Checks And MCP```bashmemi diagnose . --json --no-write --fail-on nonememi diagnose . --receipt-only --fail-on nonememi --profile locked mcp start --no-figma```Locked MCP exposes four read tools: prepare_frontend_brief, prepare_design_agent_brief, prepare_apple_design_brief, and diagnose_app_quality. The frontend tool supplies actual repository evidence. Many legacy CLI and write tools remain unavailable; capability grants do not unlock deferred command paths. Keep connector calls, project edits, and browser execution in the harness's reviewed workflow.Reuse local components and tokens according to the consumer project's conventions. Source-bearing JSON is working context; receipt-only is a separate metadata output. See docs/FRONTEND_WORKFLOW.md for the candidate evidence schema and actual verification flow.## Evidence Contract1. Read local instructions and existing product-system files first.2. Collect the minimum evidence that can change the implementation.3. Cite `file:line` findings and existing components or tokens.4. Make scoped edits.5. Re-run the same deterministic checks.6. Report commands, artifacts, files changed, and remaining assumptions.Do not claim visual correctness from source checks alone. When rendered behavior matters, verify the actual route at desktop and mobile viewports.

Frequently asked questions