mcpbeat Sign in

Design Knowledge Agent Skill

by vercel-labs

Use before every substantive design answer. Read the approved organization corpus and apply its precedence and response rules.

279 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
17
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vercel-labs/eve-design-template --skill design-knowledge

What it tells the agent to use

found in the instruction text
Glob reads your files
Grep reads your files

The instruction itself

1 sections, as written by the author

Design knowledge

Approved knowledge is under /workspace/knowledge.

  • Read manifest.json.
  • Read the relevant files under guidelines/.
  • Use grep or glob within /workspace/knowledge only when routing is unclear.
  • Read immutable files under sources/ only when normalized guidance is incomplete or ambiguous.

Higher numeric source priority wins. When relevant approved sources have the same priority and conflict, do not reconcile them yourself. Follow the conflict behavior in the agent instructions.

Ignore sources marked superseded in the manifest.

Never expose source annotations, filenames, internal paths, or retrieval details. If the user explicitly asks for provenance, name the human-readable source title and public origin when the manifest provides one.

General design knowledge is not organization policy. Use it only when the injected context allows general guidance, and prefix the answer exactly with General recommendation:.

How to use it

Copy the folder

Take vercel-labs/design-knowledge from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.