Install
$ agentstack add skill-sarveshsea-memi-design ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
memi Design Tooling
Use memi as Claude Code's local interface-understanding layer before broad UI changes. The goal is to gather product-system evidence before editing code.
First Run
npm i -g @memi-design/cli
memi --version
memi mcp start --no-figma
If a repository has not been prepared for memi yet:
memi suite init --project .
memi agent install claude-code --project .
UI Preflight
Run the smallest useful evidence loop before changing UI code:
memi agent brief . --agent claude-code --intent "$ARGUMENTS" --json
memi diagnose . --json
memi ux audit . --json
memi craft audit . --json
memi tokens --from ./src --report
memi shadcn doctor
If the work depends on a live route, replace . with the local URL for diagnose, ux audit, and craft audit.
How To Use The Evidence
- Read local instructions first:
CLAUDE.md,AGENTS.md, README files,.memoire/, specs, tokens, andmemoire.agent.yaml. - Treat
memi agent briefas the preflight contract: it should shape the plan, risk list, and final verification. - Use
diagnose,ux audit,craft audit, andtokensoutputs to avoid inventing design-system facts. - Prefer existing components, shadcn/ui primitives, Tailwind tokens, and Atomic Design boundaries already present in the app.
- End with the memi commands run, artifacts produced, files changed, and the next verification command.
Registry Work
For installable UI or examples:
memi shadcn export --out public/r
memi shadcn doctor
memi publish --name @you/design-system
Keep registry output valid, source-controlled, and linked from the app or proof repo.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sarveshsea
- Source: sarveshsea/memi
- License: MIT
- Homepage: https://memoire.cv
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.