Agent skill

Design Brief

by sanqiufong in sanqiufong/slides-from-anything

Parse a structured design brief written in I-Lang protocol format into a concrete design spec.

Apache-2.0Auto-check passedFrontend & Design

Install Design Brief

skills CLI
$ npx skills add sanqiufong/slides-from-anything --skill design-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sanqiufong/slides-from-anything design-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sanqiufong/slides-from-anything.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/design-brief .claude/skills/design-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
design-brief
GitHub stars
132
Used in
1 other repo
Token cost
~3.3k tokens
SKILL.md length
1,088 words
Files
1
Skills in repo
48
Repo updated
First seen
Licence
Apache-2.0

At a glance

Parse a structured design brief written in I-Lang protocol format into a concrete design spec.

  • Works in 5 steps: Accept input → Validate dimensions → Generate DESIGN.md → …
  • Keywords: design brief
  • SKILL.md covers Background, 1. Accept input, 2. Validate dimensions and 3. Generate DESIGN.md, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Design Brief is an agent skill from sanqiufong/slides-from-anything. Parse a structured design brief written in I-Lang protocol format into a concrete design spec. Eliminates ambiguity from vague requests like "make it professional" by requiring explicit dimensions: palette, typography, layout, mood, density, and constraints. Trigger keywords: "design brief", "create a design brief", "ilang brief", "structured brief".

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Typography. The repository describes itself as: Turn anything into slides. The licence is Apache-2.0.

When your agent uses it

  • Keywords: design brief
  • Create a design brief
  • Structured brief

Example prompts

  • “make it professional”
  • “design brief”
  • “create a design brief”
  • “/design-brief”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Accept input
  2. Validate dimensions
  3. Generate DESIGN.md
  4. Generate brief-preview.html
  5. Report unspecified dimensions

What it can do on your machine

Read from SKILL.md and the folder at commit 65da4ac. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design Brief loads about 3.3k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 1,088 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sanqiufong/slides-from-anything at commit 65da4ac, republished under its Apache-2.0 licence (© sanqiufong). 1,088 words, ~3,339 tokens.

Download SKILL.mdSave it as .claude/skills/design-brief/SKILL.md (or your agent's skills folder).
name
design-brief
description
Parse a structured design brief written in I-Lang protocol format into a concrete design spec. Eliminates ambiguity from vague requests like "make it professional" by requiring explicit dimensions: palette, typography, layout, mood, density, and constraints. Trigger keywords: "design brief", "create a design brief", "ilang brief", "structured brief".
triggers
design brief, create a design brief, ilang brief, structured brief
od.mode
design-system
od.platform
desktop
od.scenario
planning
od.capabilities_required
file_write

Design Brief Skill

Parse a structured design brief into a concrete DESIGN.md and optional visual preview. Agent, follow this workflow exactly.

Background

The 8 dimensions in this skill are derived from analysis of the 71 design systems bundled with Open Design. Every DESIGN.md in design-systems/ resolves at minimum: color palette, accent, typography, display font, layout model, and component style. We distilled these into 8 orthogonal dimensions that cover the decisions a designer makes before any pixel is placed. Mood and density were added because they are the two most common sources of ambiguity in natural language briefs ("make it clean" means different things to different people).

Dimensions intentionally excluded from the brief level: animation timing, responsive strategy, and accessibility contrast. These are enforced at the template level by individual skills (e.g., saas-landing handles its own responsive logic), though the generated DESIGN.md includes sensible breakpoint defaults for downstream consumption.

1. Accept input

The user provides a design brief in one of two formats:

Option A: I-Lang structured brief
[PLAN:@DESIGN|type=saas_landing]
  |palette=navy_and_white|accent=coral
  |typography=inter|display=space_grotesk
  |layout=single_column|max_width=1200px
  |mood=professional_minimal
  |density=spacious|section_gap=96px
  |hero=headline+subhead+cta
  |sections=features,pricing,testimonials,footer
  |exclude=animations,parallax,gradients
  |responsive=mobile_first
Option B: Natural language

"I need a landing page for a developer tool. Clean, minimal, dark mode. Inter font. No flashy animations."

If the user provides Option B, convert it to the structured format using the mapping table below, then proceed. Identify every dimension explicitly stated and flag dimensions that were left unspecified.

Natural language → I-Lang mapping

For each sentence in the natural language input, identify dimension keywords and map to the closest structured value:

Natural language phraseDimensionI-Lang value
"dark mode", "dark theme"palettemonochrome_dark
"light", "white background"palettelight_clean
"earthy", "warm tones"paletteearth_tones
"pop of color", "vibrant"accentelectric_blue (default) or coral
"subtle accent"accentmuted_sage (default) or slate
"clean", "minimal", "simple"moodprofessional_minimal
"playful", "fun", "friendly"moodplayful
"bold", "brutalist", "raw"moodbrutalist
"editorial", "magazine-like"moodeditorial
"spacious", "lots of whitespace"densityspacious
"compact", "dense", "information-rich"densitycompact
"Inter", "system font"typographyinter (default) or system_ui
"serif", "traditional"typographygeorgia (default) or playfair
"monospace", "code-like"typographyjetbrains_mono
"no animations", "static"excludeanimations
"no gradients"excludegradients
"no stock photos"excludestock_photos
"single page"layoutsingle_column
"two columns", "sidebar"layouttwo_column
"mobile first"responsivemobile_first

When a phrase maps to multiple dimensions (e.g. "clean dark landing page" → mood=professional_minimal + palette=monochrome_dark + layout=single_column), resolve each dimension independently. When multiple values are listed for a single mapping, the first is the default; the agent may select the alternative only if surrounding context strongly favors it.

2. Validate dimensions

Every design brief must resolve these 8 dimensions. If any are missing from the input, select sensible defaults using the rules in Section 2.2.

The values listed below form a closed vocabulary. Only values in this table have concrete token mappings in Section 2.1. If the user provides a value not listed here, the agent must prompt for clarification rather than guessing.

#DimensionKeyExample values
1Color palettepalettenavy_and_white, earth_tones, monochrome_dark, light_clean
2Accent coloraccentcoral, electric_blue, emerald, muted_sage
3Body typographytypographyinter, system_ui, dm_sans, georgia
4Display typographydisplayspace_grotesk, clash_display, same_as_body, playfair
5Layout modellayoutsingle_column, two_column, asymmetric
6Moodmoodprofessional_minimal, playful, brutalist, editorial
7Densitydensitycompact, balanced, spacious
8Constraintsexcludeanimations, gradients, stock_photos, carousel
2.1 Symbolic → concrete token resolution

Each symbolic value maps to concrete design tokens. The agent must resolve these before writing DESIGN.md:

Symbolic valueConcrete tokens
palette=navy_and_whiteBackground: #0F172A, Surface: #1E293B, Text: #F8FAFC, Secondary: #94A3B8
palette=monochrome_darkBackground: #09090B, Surface: #18181B, Text: #FAFAFA, Secondary: #A1A1AA
palette=light_cleanBackground: #FFFFFF, Surface: #F8FAFC, Text: #0F172A, Secondary: #64748B
palette=earth_tonesBackground: #FFFBEB, Surface: #FEF3C7, Text: #451A03, Secondary: #92400E
accent=coralAccent: #F97316, Hover: #EA580C
accent=electric_blueAccent: #3B82F6, Hover: #2563EB
accent=emeraldAccent: #10B981, Hover: #059669
accent=muted_sageAccent: #84A98C, Hover: #6B8F73
accent=slateAccent: #64748B, Hover: #475569
typography=interBody: Inter, 400, 1rem/1.6
typography=system_uiBody: system-ui, 400, 1rem/1.6
typography=dm_sansBody: DM Sans, 400, 1rem/1.6
typography=georgiaBody: Georgia, 400, 1.125rem/1.7
display=space_groteskDisplay: Space Grotesk, 700, clamp(2rem, 5vw, 3.5rem)
display=clash_displayDisplay: Clash Display, 700, clamp(2rem, 5vw, 3.5rem)
display=playfairDisplay: Playfair Display, 700, clamp(2rem, 5vw, 3.5rem)
display=same_as_bodyDisplay inherits body font family, weight 600
density=compactSection spacing: 48px, Content padding: 16px/24px
density=balancedSection spacing: 72px, Content padding: 24px/40px
density=spaciousSection spacing: 96px, Content padding: 24px/48px

Symbolic values not in this table are not valid. If the user provides an unrecognized value (e.g., palette=ocean_blue), the agent must prompt for clarification: "I don't recognize palette=ocean_blue. Did you mean navy_and_white, monochrome_dark, light_clean, or earth_tones?"

Show full SKILL.md (362 more words)Show less
2.2 Default resolution rules

When a dimension is unspecified, defaults are selected based on mood compatibility:

Unspecified dimensionDefault rule
paletteIf mood=editorial → light_clean. If mood=brutalist → monochrome_dark. Otherwise → light_clean.
accentIf palette is dark → coral. If palette is light → electric_blue.
typographyAlways → inter (highest cross-platform legibility).
displayIf mood=editorial → playfair. If mood=brutalist → space_grotesk. Otherwise → same_as_body.
layoutAlways → single_column (safest responsive default).
moodAlways → professional_minimal (least opinionated).
densityAlways → balanced.
excludeAlways → none (no constraints unless specified).

If mood is also unspecified, all defaults fall back to the safe neutral set: palette=light_clean, accent=electric_blue, typography=inter, display=same_as_body, layout=single_column, mood=professional_minimal, density=balanced, exclude=none.

3. Generate DESIGN.md

This skill generates a new DESIGN.md from scratch based on the resolved brief dimensions. If a DESIGN.md already exists in the working directory, the agent should ask the user whether to overwrite or skip.

Produce a DESIGN.md following Open Design's 9-section convention. All color hex values, font stacks, and spacing values must come from the resolved tokens in Section 2.1 — do not invent values outside the resolution table.

markdown
# [Project Name] Design System

## Visual Theme & Atmosphere
- Mood: [resolved from mood]
- Feel: [derived from mood — e.g., professional_minimal → "Clean, confident, restrained"]
- References: [if mood=editorial → "Magazine layouts, Monocle, Cereal"; if mood=brutalist → "Exposed structure, raw typography"]

## Color Palette & Roles
- Background: [resolved from palette]
- Surface: [resolved from palette]
- Text primary: [resolved from palette]
- Text secondary: [resolved from palette]
- Accent: [resolved from accent]
- Accent hover: [resolved from accent]

## Typography Rules
- Display: [resolved from display], 700, clamp(2rem, 5vw, 3.5rem)
- Body: [resolved from typography], 400, 1rem/1.6
- Mono: JetBrains Mono, 400, 0.875rem

## Component Stylings
- Buttons: [if mood=playful → "rounded-full", otherwise → "rounded-md"], accent bg, contrast text
- Cards: surface bg, subtle border, 12px radius
- Inputs: [if mood=brutalist → "thick border", otherwise → "transparent bg, bottom border"]

## Layout Principles
- Max width: 1200px
- Grid: [resolved from layout]
- Section spacing: [resolved from density]
- Content padding: [resolved from density]

## Depth & Elevation
- Shadows: [if mood=brutalist → "hard 4px offset", if mood=professional_minimal → "none", otherwise → "subtle sm"]
- Borders: 1px solid [derived from palette, 8% opacity of text color]

## Do's and Don'ts
- DO use the declared color tokens exclusively.
- DO maintain consistent section spacing.
- DO ensure all text meets WCAG AA contrast ratio.
- DON'T invent colors outside the palette.
- DON'T add decorative shadows unless Depth & Elevation allows them.
- DON'T use more than 2 display/body typefaces (monospace is a utility face for code and data — it does not count toward this limit).

## Responsive Behavior
- Breakpoints: 640px (sm), 768px (md), 1024px (lg), 1280px (xl)
- Mobile: single column, stack all sections vertically
- Tablet: allow 2-column feature grids
- Desktop: full layout with max-width constraint
- Images: fluid, max-width 100%, maintain aspect ratio

## Agent Prompt Guide
- Do NOT invent colors outside this palette.
- Do NOT add box-shadows unless specified above.
- Accent color appears maximum 3 times per viewport.
- All interactive elements need :focus-visible outline.
- [if exclude contains items → list each as "Do NOT use {item}."]

4. Generate brief-preview.html

Create a single HTML file that visually renders the resolved design tokens. The preview must contain these 4 sections in order:

  1. Color palette swatches — A horizontal row of rectangles, each showing one color from the Color section. Label each with its role (Background, Surface, Text, Accent) and hex code.
  2. Typography specimens — Three text blocks showing Display, Body, and Mono fonts at their declared sizes. Use a sample sentence ("The quick brown fox...") for each.
  3. Spacing ruler — A visual ruler or stacked bars showing section spacing and content padding values, labeled with their px values.
  4. Component preview — Render 2–3 live components (a primary button, a card with title/body, a text input) using the resolved tokens. These should be functional HTML/CSS, not screenshots.

Style the preview itself with the resolved design system tokens (background color, font, spacing). The preview should look like a design system documentation page.

5. Report unspecified dimensions

At the end of output, list any dimensions the user did not specify and the defaults that were applied, including the rule that selected each default:

Dimensions resolved from defaults:
- display: set to "same_as_body" (rule: mood=professional_minimal → same_as_body)
- density: set to "balanced" (rule: static fallback, no spacing preference given)
- exclude: set to "none" (rule: no constraints unless specified)

This transparency prevents silent assumptions from propagating into the final design.

© sanqiufong, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/design-brief of sanqiufong/slides-from-anything.

Open the folder on GitHubat commit 65da4ac

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sanqiufong/slides-from-anything, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Design Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Design Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Design Brief this skillsanqiufong/slides-from-anything1321 repos~3.3kAutomated safety check: PassApache-2.0
Impeccablebestofjs/bestofjs3.1k26 repos~2.6kAutomated safety check: PassMIT
Tailwindcss Developmentanonaddy/anonaddy4.9k10 repos~865Automated safety check: PassMIT
Design SystemOhh-889/skyroc79511 repos~1.7kAutomated safety check: PassMIT
Make Interfaces Feel Bettersamuelclay/NewsBlur7.6k10 repos~1.5kAutomated safety check: PassMIT
UI UX Pro Maxsaoudi-h/solar-icons19018 repos~11kAutomated safety check: NotesCustom licence

Similar skills

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 26 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Frontend & DesignAuto-check passed
  • Design System

    Ohh-889/skyroc

    Token architecture, component specifications, and slide generation.

    795 GitHub starsUsed in 11 repos~1.7k tokens
    Frontend & DesignAuto-check passed
  • Make Interfaces Feel Better

    samuelclay/NewsBlur

    Design engineering principles for making interfaces feel polished.

    7.6k GitHub starsUsed in 10 repos~1.5k tokens
    Frontend & DesignAuto-check passed
  • UI UX Pro Max

    saoudi-h/solar-icons

    UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.

    190 GitHub starsUsed in 18 repos~11k tokens
    Frontend & DesignAuto-check: notes
  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.6k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from sanqiufong/slides-from-anything

All 48 skills in this repo
  • PPTX HTML Fidelity Audit

    sanqiufong/slides-from-anything

    Audit a python-pptx export against its source HTML deck, identify layout/content drift (footer overflow, cropped content, missing italic/em, lost styling, off-rhythm spacing), and re-export with…

    132 GitHub starsUsed in 1 repo~3.5k tokens
    Auto-check passed
  • Mobile App

    sanqiufong/slides-from-anything

    A mobile-app screen rendered inside a pixel-accurate iPhone 15 Pro frame on the page.

    132 GitHub starsUsed in 1 repo~942 tokens
    Auto-check passed
  • Replit Deck

    sanqiufong/slides-from-anything

    Single-file horizontal-swipe HTML deck in the style of Replit Slides's landing-page template gallery.

    132 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed
  • Live Artifact

    sanqiufong/slides-from-anything

    Create refreshable, auditable Open Design artifacts backed by connector or local data.

    132 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Open Design Landing

    sanqiufong/slides-from-anything

    Produce a world-class single-page editorial landing site in the Atelier Zero visual language (Monocle / Apartamento / Études editorial collage) — the same aesthetic Open Design uses for its own…

    132 GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check passed
  • Web Prototype

    sanqiufong/slides-from-anything

    General-purpose desktop web prototype. An agent skill from sanqiufong/slides-from-anything.

    132 GitHub starsUsed in 3 repos~1k tokens
    Auto-check passed

Questions about Design Brief

What does Design Brief do?

Parse a structured design brief written in I-Lang protocol format into a concrete design spec. Design Brief is an agent skill from sanqiufong/slides-from-anything. Parse a structured design brief written in I-Lang protocol format into a concrete design spec.

When should I use Design Brief?

Design Brief fits situations like: keywords: design brief; create a design brief; structured brief.

How do I install Design Brief in Claude Code?

Run `npx skills add sanqiufong/slides-from-anything --skill design-brief -a claude-code`. Or copy the skill folder (skills/design-brief in sanqiufong/slides-from-anything) into .claude/skills/design-brief in your project. Claude Code loads it when a task matches its description.

How do I install Design Brief in Codex?

Run `npx skills add sanqiufong/slides-from-anything --skill design-brief -a codex`. Or copy the skill folder (skills/design-brief in sanqiufong/slides-from-anything) into .agents/skills/design-brief in your project. Codex loads it when a task matches its description.

Can I use Design Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sanqiufong/slides-from-anything --skill design-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-brief, .gemini/skills/design-brief, .github/skills/design-brief and .opencode/skills/design-brief in your project.

What does Design Brief need to run?

SKILL.md names no scripts, command-line tools or credentials: Design Brief is instructions for the agent only.

Does Design Brief access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Design Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Design Brief use?

Design Brief is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Design Brief use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Design Brief?

Skills that share tags, products or a category with Design Brief: Impeccable (bestofjs/bestofjs, 3.1k stars), Tailwindcss Development (anonaddy/anonaddy, 4.9k stars), Design System (Ohh-889/skyroc, 795 stars) and Make Interfaces Feel Better (samuelclay/NewsBlur, 7.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design Brief?

sanqiufong (a GitHub user) maintains it in sanqiufong/slides-from-anything, which has 132 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 10, 2026.

Source: sanqiufong/slides-from-anything on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.