Remember design system
Skill memi-design/memi/plugins/memoire/skills/remember-design-system
Use when an agent is about to build or refactor interface code and needs a compact, repository-specific brief covering existing tokens, components, routes, conventions, and verification commands.From its SKILL.md
npx -y skills add memi-design/memi --skill remember-design-systemAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.4 KB, as published. Nobody here has run it
Remember The Design System
Build design context from the repository instead of guessing from the prompt. This is a preflight for UI work, not a request to redesign the product.
Build The Brief
Translate the user's task into a short intent, then run from the repository root:
npx -y @memi-design/[email protected] agent brief . --intent "<user's interface task>" --detail compact --json
If the task changes colors, spacing, typography, radii, or shadows, add token evidence:
npx -y @memi-design/[email protected] tokens --from ./src --report --json
Apply The Memory
- Prefer existing components and shadcn primitives over new abstractions.
- Map every new component to atom, molecule, organism, template, or page.
- Reuse semantic CSS variables and Tailwind theme tokens. Do not introduce raw hex values when a token exists.
- Preserve route, state, loading, empty, error, focus, and responsive behavior identified by the brief.
- Expand to
--detail standardonly when compact output omits evidence needed for the edit.
Handoff
Before editing, state the components and tokens you will reuse. After editing, cite files changed, evidence followed, checks run, and any design assumptions that remain.