Memoire design tooling

Skill memi-design/memi/skills/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.From its SKILL.md

Install

npx -y skills add memi-design/memi --skill memoire-design-tooling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.3 KB, as published. Nobody here has run it

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/[email protected] 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.