How do I install the Memoire Design Tooling skill?

Run npx skillmds@latest add hashgraph-online-awesome-codex-plugins/memoire-design-tooling 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. 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, and the skill stays under its author's original license.

Who published Memoire Design Tooling?

hashgraph-online (@hashgraph-online-awesome-codex-plugins) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memoire Design Tooling by hashgraph-online-awesome-codex-plugins

Name: Memoire Design Tooling
Rating: 4.2 (5 reviews)
Author: hashgraph-online

Memoire Design Tooling

Use when a task spans interface understanding, design-system memory, UI audits, design CI, Figma, shadcn or Tailwind code generation, research, or agent design workflows and needs the correct Memi capability selected.

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

Compact Preflight

npx -y @memi-design/cli@2.7.9 agent brief . --intent "<interface task>" --detail compact --json

Use --detail standard only when the compact brief lacks evidence needed for the edit.

Advanced Paths

memi agent install --dry-run --json
memi scaffold component EvidenceCard --level organism --json
memi ios brief --intent "<SwiftUI task>" --detail compact --json
memi ios scaffold FeatureName --kind screen --module AppModule --json
memi research design --intent "<task>" --json
memi shadcn export --out public/r --json
memi mcp start --no-figma

Review dry-run output before writes. Every created component must state its Atomic Design level, reuse local or shadcn primitives, and use semantic tokens instead of raw hex values.

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-toolingdescription: Use when a task spans interface understanding, design-system memory, UI audits, design CI, Figma, shadcn or Tailwind code generation, research, or agent design workflows and needs the correct Memi capability selected.---# 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```## Compact Preflight```bashnpx -y @memi-design/cli@2.7.9 agent brief . --intent "<interface task>" --detail compact --json```Use `--detail standard` only when the compact brief lacks evidence needed for the edit.## Advanced Paths```bashmemi agent install --dry-run --jsonmemi scaffold component EvidenceCard --level organism --jsonmemi ios brief --intent "<SwiftUI task>" --detail compact --jsonmemi ios scaffold FeatureName --kind screen --module AppModule --jsonmemi research design --intent "<task>" --jsonmemi shadcn export --out public/r --jsonmemi mcp start --no-figma```Review dry-run output before writes. Every created component must state its Atomic Design level, reuse local or shadcn primitives, and use semantic tokens instead of raw hex values.## 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