remember-design-system — Claude Code skill for UI context
Builds a repository-specific brief before interface work, covering tokens, components, routes, conventions, and checks. Use it before building or refactoring UI code.
npx skills add memi-design/memi --skill remember-design-system -a claude-codeWhat remember-design-system does
The skill runs memi agent brief from the repository root to gather design-system context. For a selected Figma or Paper node, you can pass normalized design data with --design-evidence.
Before editing, the agent identifies components and tokens to reuse and preserves the route, state, and responsive behavior captured in the brief. Afterward, it reports changed files, evidence followed, and checks run. If the brief leaves a detail unresolved, the workflow calls for reading the cited source files. The recipes require local memi to report version 2.8.0-beta.2; npm availability alone does not confirm that the native binary works.
What it helps with
- gather a concise design-system brief from a repository
- find existing components and tokens for a UI change
- preserve route and state behavior during interface edits
- run the project’s actual tests after UI work
Example prompts for the agent
- Before changing this page, inspect the project’s design system and name the components and tokens you’ll reuse.
- Prepare a UI brief for adding a loading state to the profile page.
- Use
design/selected-node.jsonas design evidence for this interface task.
How to install remember-design-system
1Skills CLI (Vercel)
npx skills add memi-design/memi --skill remember-design-system -a claude-code2Manually: put the files in place
~/.claude/skills/remember-design-system/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/remember-design-system/
1Skills CLI (Vercel)
npx skills add memi-design/memi --skill remember-design-system -a codex2Manually: put the files in place
.agents/skills/remember-design-system/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add memi-design/memi --skill remember-design-system -a cursor2Manually: put the files in place
.cursor/skills/remember-design-system/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install memi-design/memi remember-design-system2Manually: put the files in place
.github/skills/remember-design-system/SKILL.md1Skills CLI (Vercel)
npx skills add memi-design/memi --skill remember-design-system -a gemini-cli2Platform CLI
gemini skills install https://github.com/memi-design/memi --path skills/remember-design-systemManually: put the files in place
.devin/skills/remember-design-system/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add memi-design/memi --skill remember-design-system -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about remember-design-system
How do I install remember-design-system in Claude Code?
Run npx skills add memi-design/memi --skill remember-design-system -a claude-code. The skill file is installed at ~/.claude/skills/remember-design-system/SKILL.md.
What does remember-design-system do?
It builds a compact repository brief with design tokens, components, routes, conventions, and verification commands. The agent can use that context before making UI changes.
Which memi version does it require?
The recipes target 2.8.0-beta.2, and the local memi command must report that version. Having the package available through npm does not by itself confirm native-binary support.
Source text
SKILL.md · MIT
--- name: remember-design-system description: 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. --- # 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. This workflow targets published beta **2.8.0-beta.2**. Use `npx -y @memi-design/[email protected] --version` to verify the exact package; a local `memi` must report that same version before these recipes run. The independent stable compatibility baseline is **2.7.9**. See [current release state](https://github.com/memi-design/memi/blob/main/docs/CURRENT_RELEASE.md) and [known limitations](https://github.com/memi-design/memi/blob/main/docs/trust/KNOWN_LIMITATIONS.md). npm availability alone does not establish native-binary success. ## Build The Brief Translate the user's task into a short intent, then run from the repository root: ```bash memi agent brief . --frontend --intent "<user's interface task>" --max-bytes 16384 --json ``` The frontend brief already includes bounded token and story evidence. For a selected Figma or Paper node, use the harness connector and supply its normalized evidence: ```bash memi agent brief . --frontend --intent "<task>" --design-evidence design/selected-node.json --json ``` ## Apply The Memory 1. Prefer existing components and the project's conventions. Do not impose a new component library or CSS framework. 2. Map every new component to atom, molecule, organism, template, or page. 3. Reuse semantic CSS variables and Tailwind theme tokens. Do not introduce raw hex values when a token exists. 4. Preserve route, state, loading, empty, error, focus, and responsive behavior identified by the brief. 5. Resolve stale/conflicting mappings and missing required props before editing. Read cited source files when the bounded brief omits needed details. 6. Treat inferred story IDs and host-supplied mappings as evidence, not rendered verification. Run the actual project tests. ## 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.
© memi-design · MIT · memi-design/memi
