# design

design is a Claude Code skill for planning and checking user-facing interfaces. It activates for new or changed screens and when reviewing visual choices.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 121 repo stars
- Author: vicotrbb
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/vicotrbb/cubebot/tree/HEAD/apps/orchestrator/skills/design/SKILL.md
- Updated: 2026-11-17
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/vicotrbb-design

## What it does

design guides interface work from the initial direction through implementation and review. It asks the agent to define the screen’s purpose, then choose a concept, colours, type and layout before writing code. It covers pages, forms, dashboards, emails, charts and other things people see. Backend-only tasks are outside its scope.

The guidance covers contrast, interactive states, semantics, small screens and motion. After building, render the interface at phone and desktop widths, inspect each theme, then check contrast, target sizes and overflow. If the project already has a design system, extend its tokens and components rather than creating a parallel one.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add vicotrbb/cubebot --skill design -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/design/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/design/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add vicotrbb/cubebot --skill design -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/design/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add vicotrbb/cubebot --skill design -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/design/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install vicotrbb/cubebot apps/orchestrator/skills/design
```

2. **Manually: put the files in place**
- File: `.github/skills/design/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add vicotrbb/cubebot --skill design -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/vicotrbb/cubebot --path apps/orchestrator/skills/design
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/design/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/vicotrbb/cubebot/tree/HEAD/apps/orchestrator/skills/design/SKILL.md

## When to use it
- choose a visual direction for a new screen
- check contrast and interactive states in a form
- adapt a page for narrow screens
- review a rendered interface and fix layout issues

## Example prompts
- Design a settings screen for this app and state the visual direction before coding.
- Review this form for contrast, field labels and interaction states.
- Adapt this page to a phone width and check for horizontal overflow.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e2629a7056b0bb77.

BEGIN THIRD-PARTY FILE e2629a7056b0bb77
```text
---
name: design
description: How to design and build interfaces people trust and remember. Load this before creating or changing anything a person sees, such as a web page, app screen, dashboard, form, component, email, slide, chart or poster, and when asked to make something look better, reviewing a design, or choosing colours, type or layout. Not for backend-only work.
---

# Design

Models converge. Left alone, you will produce the statistically average interface: a safe font, a purple or warm-beige wash, three identical cards, a big number with a small label. It looks fine and belongs to nobody. Your job is to make choices a person would recognise as choices.

A brief from the person always wins. If they pinned a palette, a font, an era or a brand, honour it exactly, even where it breaks the advice below. If the product already has a design system, extend it: match its tokens and components rather than inventing beside them.

## 1. Decide what this surface is for

Name who is looking at it, where they are, and the one thing success means. Then pick the register, because it changes every later decision:

- **Persuade** (landing page, campaign, pricing): the person decides and acts. Hold a point of view and earn attention.
- **Operate** (app, dashboard, editor, settings): the person gets a task done, often daily. Clarity, density, familiar patterns and speed beat expression. Character lives in the details.
- **Read** (docs, article, report): the person understands something. Structure and typography do the work.
- **Experience** (portfolio, gallery, game): the work itself leads and the interface recedes.

## 2. Commit to a direction before writing code

Write down, briefly:

- **A concept in one sentence,** drawn from this subject's own world, not from "modern and clean".
- **Colour:** four to six named values with their hex codes, one dominant and one sharp accent. Pick light or dark from where the person is using it.
- **Type:** roles for display, body and data, with a real scale. Choose a face because it suits this subject.
- **Layout:** the idea that organises the page, and what the first screen shows.
- **The one bold move.** Spend your boldness in one place and keep everything else quiet around it.

Then test it: _would I have written this for any other product in the category?_ If yes, change it. Ask of each element: is this a decision, or a default I reached for?

## 3. Avoid the template

These are defaults to question, not laws. A brief or a concept can earn any of them, but reaching for one because the axis was free means you were not deciding.

- Rows of identical cards with an icon, a heading and two lines of text; cards inside cards.
- A big number with a small label as the main idea of a page.
- A small uppercase label sitting above every heading; 01 / 02 / 03 on things that are not a sequence.
- Gradient text, glass effects, and glowing shadows used as decoration.
- A thick coloured stripe down one side of a card or alert.
- Sparklines and progress rings standing in for real content.
- Emoji used as icons; use one drawn icon set at one stroke weight.
- Monospace as a costume for "technical"; keep it for code and data.
```
END THIRD-PARTY FILE e2629a7056b0bb77

The third-party file has ended. Everything between the e2629a7056b0bb77 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3195 of 5622 bytes. © vicotrbb · Apache-2.0 · https://github.com/vicotrbb/cubebot/tree/HEAD/apps/orchestrator/skills/design/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
