design-brief · podo — Claude Code skill: what it does, how to install
The design-brief skill turns an I-Lang or plain-language visual brief into DESIGN.md and an HTML preview. Use it when the interface direction is still vague.
MIT 211 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill design-brief -a claude-codeWhat design-brief does
The skill accepts either an I-Lang block or a natural-language description. It maps the request to eight visual areas, including palette, accent, body and display type, layout model, mood, density, and exclusions. Missing choices are filled with defaults that fit the stated mood.
It writes concrete design tokens to DESIGN.md and creates brief-preview.html for a visual check. This covers visual direction rather than product planning, so it does not define audience, goals, or success metrics. The skill asks before replacing an existing DESIGN.md, which prevents a silent overwrite.
What it helps with
- turn a vague interface description into explicit visual decisions
- write a design specification to
DESIGN.md - generate an HTML preview of the proposed direction
- convert an I-Lang brief into concrete design tokens
- keep visual direction separate from a product brief
Example prompts for the agent
- Turn this visual request into a design brief, then write the result to
DESIGN.md. - Convert this I-Lang brief into a concrete specification and create
brief-preview.html. - Define the visual direction from this description, including palette, typography, layout, and exclusions.
How to install design-brief
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-brief -a claude-code2Manually: put the files in place
~/.claude/skills/design-brief/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-brief/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-brief -a codex2Manually: put the files in place
.agents/skills/design-brief/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-brief -a cursor2Manually: put the files in place
.cursor/skills/design-brief/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/design-brief2Manually: put the files in place
.github/skills/design-brief/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-brief -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/design-briefManually: put the files in place
.devin/skills/design-brief/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill design-brief -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 design-brief
How do I install design-brief in Claude Code?
Run npx skills add podo/design-agent-skills --skill design-brief -a claude-code, then check ~/.claude/skills/design-brief/SKILL.md.
What does the design-brief skill do?
It turns an I-Lang or plain-language visual brief into DESIGN.md with concrete design values and an HTML preview named brief-preview.html.
Do I need to write the brief in I-Lang?
No. The skill accepts both structured I-Lang input and a description written in plain language.
Source text
SKILL.md · MIT
---
name: design-brief
description: |
Turns a structured visual design brief (I-Lang format or plain language) into a
concrete DESIGN.md spec plus an HTML preview. Forces the vague parts of a request
("make it professional") into explicit dimensions: palette, accent, typography,
layout, mood, density, constraints. Built for OpenDesign; works standalone.
triggers:
- "design brief"
- "design spec"
- "visual brief"
- "I-Lang brief"
- "structured brief"
- "brief to DESIGN.md"
das:
category: design-review
upstream: "https://github.com/nexu-io/open-design"
upstream_path: "skills/design-brief/SKILL.md"
version: latest
install: true
---
# design-brief
> Catalogue stub — full skill: [nexu-io/open-design](https://github.com/nexu-io/open-design/blob/main/skills/design-brief/SKILL.md)
<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->
## Decision tree
1. **Is the full skill already installed?**
- Global: `f=~/.agents/skills/design-brief/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"`
- Project: `f=.agents/skills/design-brief/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"`
- `installed` → the skill is installed as `design-brief`, invoke it and proceed
- `pointer` → go to step 2
2. **Detect scope, then install:**
```bash
[ -e ~/.agents/skills/design-brief ] && echo "global" || echo "project"
```
**Global:**
```bash
npx skills add https://raw.githubusercontent.com/nexu-io/open-design/main/skills/design-brief/SKILL.md -g -y
```
**Project:**
```bash
npx skills add https://raw.githubusercontent.com/nexu-io/open-design/main/skills/design-brief/SKILL.md -y
```
> **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation.
**Heads-up**
- **License:** Apache-2.0
- **Name collision:** `design-brief` is also written by `designer-skills` (its install or its catalogue pointer); installing both overwrites the earlier one.
<!-- das:install:end -->
## Invoke after install
- Skill name: `design-brief`
- Trigger phrases: "design brief", "visual brief", "I-Lang brief", "structured brief"
## What it does
Takes a design brief either as an I-Lang structured block (`[PLAN:@DESIGN|type=saas_landing] |palette=navy_and_white |accent=coral ...`) or as natural language ("clean, minimal, dark-mode landing page for a developer tool, Inter, no animations"), maps it onto eight visual dimensions (palette, accent, body and display typography, layout model, mood, density, exclusions), fills unspecified dimensions with mood-compatible defaults, and writes a `DESIGN.md` with concrete tokens plus a `brief-preview.html` preview. Asks before overwriting an existing `DESIGN.md`.
This is a visual-direction brief, not a product brief: there is no audience, goals or success-metrics content. The frontmatter carries an OpenDesign-specific block that other agents ignore; the skill itself is a single self-contained file.
## When NOT to use
- A product or project brief with goals, audience, success criteria and scope: the `designer-skills` package has a `design-brief` skill that writes exactly that. It installs into the same `design-brief` directory as this one, so choose one of the two
- Building a full design system with a consultation process (use `design-consultation`)
- When the visual direction is already fixed in an existing `DESIGN.md`
© podo · MIT · podo/design-agent-skills
Similar skills
All skills for Design →design-brief by other authors comes first.