# Install design-engineering

> Install the skill one way (skills.sh or the Claude Code plugin), check that it loaded, and use its menu.

Module: Start from zero · Level: beginner · 5 min · https://school.agents.org.in/foundations/start/install-design-engineering

Once the skill is in, one line brings up its menu. If you see this, everything worked:

*[Interactive demo: Type the entry point with nothing after it: the menu comes back, leading with what fits right now.]*

There are two ways to get there. **Pick one.** Both install the same skill; they differ in how you call it afterwards.

## Way 1: skills.sh (any agent)

skills.sh (An installer that copies a skill into the place your agents look for it (Claude Code, Cursor, Codex and others), with one npx command) is an installer that puts a skill where your agent looks for it: Claude Code, Cursor, Codex and many more. Run this in your terminal, inside your project folder:

```bash
npx skills add AgentsORG/design-engineering
```

`npx` runs a tool from npm without installing it for good, so you need [Node.js](/learn/start/set-up-your-agent) for this. The installer asks which agents to link the skill into; pick the one you use.

Afterwards, you call it as:

```bash
/design-engineering
```

## Way 2: the Claude Code plugin

If you use Claude Code, you can install it as a plugin (A package that adds skills, commands or helpers to a harness in one install. design-engineering ships as a Claude Code plugin and as a plain skill) instead. A plugin can bring extra helpers along with the skill, such as specialist reviewers for motion or accessibility. These two lines go **inside Claude Code** (after you have run `claude`), not in a plain terminal:

```bash
/plugin marketplace add AgentsORG/design-engineering
```
```bash
/plugin install design-engineering@agentsorg
```

The first line adds the marketplace (A published list of plugins you add to Claude Code once, so you can install plugins from it by name) (a list of plugins someone publishes); the second installs this plugin from it. Plugins name their commands after themselves, so afterwards you call it as:

```bash
/design-engineering:design-engineering
```

  **Both ways at once (avoid):**

Two copies of the skill. Your agent sees two that match every design request, loads both, and may follow two slightly different versions. Confusing and wasteful.

  **One way (do this):**

One copy, one entry point. If you switch, remove the old one first: `npx skills remove design-engineering`, or `/plugin uninstall design-engineering@agentsorg` in Claude Code.

> **Which should I pick?.** Using Claude Code? The plugin is the fuller install. Using Cursor, Codex or several agents? skills.sh. Not sure? skills.sh works everywhere.

## Check that it loaded

Start a fresh agent session (skills are read when a session starts, so restart after installing). Then type the entry point with nothing after it:

  **Claude Code:**

Type `/design-engineering` (skills.sh) or `/design-engineering:design-engineering` (plugin). As you type the slash, it should appear in the list of commands. Press <kbd>Enter</kbd> and the menu comes back.

  **Cursor:**

In the agent panel, type `/design-engineering` and send it. If the menu of verbs comes back, it loaded. If not, check that you picked Cursor when skills.sh asked which agents to link.

  **Codex:**

Type `/design-engineering` and send it, or just ask "Use the design-engineering skill: show me its menu." The verbs should come back.

  **VS Code:**

In Agent mode, type `/design-engineering` or ask "Use the design-engineering skill: show me its menu." The verbs should come back.

If the agent answers with a general reply about design instead of the menu, the skill did not load. Restart the session; if that does not help, run the install again and read what it prints.

## The no-argument menu

The menu is your map. It lists every verb with a one-line job, and it puts the two or three that fit first: an unfinished change in your project suggests `review`, a `.design` file suggests `tokens`, a video file suggests `film review`.

| Verb | What it does |
|---|---|
| `review` | Reviews UI code as a Before / After / Why table |
| `polish` | For screens that work but feel unfinished |
| `motion` | Should it move? Then the timing, easing and springs |
| `tells` | Lists what makes a screen look AI-made, to delete |
| `a11y` | An accessibility audit with evidence |
| `ship` | A whole-app pass before launch |

**It never runs a verb on its own.** It shows the menu and waits for you to pick, or to describe the job in plain words.

*(Remember which way you installed. Every prompt in this course says `/design-engineering`; with the plugin, read it as `/design-engineering:design-engineering`.)*

**Confirm the install (paste into your agent):**

```text
Is the design-engineering skill loaded? If it is, show me its menu with no verb and tell me which two verbs fit this project right now. If it is not, tell me exactly what you see instead.
```

**Check yourself:** You installed the skill with skills.sh, then also installed the Claude Code plugin. What should you do?

- [ ] Nothing, two copies are more thorough
- [x] Remove one, so the agent loads a single copy
- [ ] Delete Node.js
- [ ] Rename one of them

*Why:* Install one way only. Two copies both match every design request, so the agent may load both and follow two versions.

## In the skill

- https://school.agents.org.in/skill/commands/MOC-commands.md
- https://school.agents.org.in/skill/meta/skill-router.md