design-brief
Skill0 starsChanged 34 days agoMITView on GitHub
Turn a graphic request into a one-page brief (message, audience, format, copy, success test) before anything is designed.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- ANT1OFF/gramtheir own version, first seen Nov 8, 2026
- drinkspiller/skillstheir own version, first seen Nov 6, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
- taro1037-design/claude-skillstheir own version, first seen Oct 20, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use brief-to-tasks, design-flow and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
julianoczkowskiSkillbrief-to-tasks
Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
Also in 7 projects that use this
- julianoczkowskiSkill
design-flow
Run the full design-to-build workflow as a guided sequence. Orchestrates all designer skills in order, from grilling through review. Use when user wants to go through the complete design process, start a project from scratch, run the full flow, or mentions "design flow" or "full workflow".
Also in 6 projects that use this
45ckSkillinformation-architecture
Define the information architecture for a prototype -- sitemap, navigation model, grouping logic, labeling, and action placement.
Also in 8 projects that use this
ilikescienceSkilldesign-tokens
Expert in design tokens using the DTCG specification. Use this skill when users ask about design tokens, DTCG format, token validation, formatting, transformation, color spaces (sRGB, Display P3, OKLCH), references and aliasing, resolvers, theming with modifiers/contexts, multi-platform design systems, accessibility, or working with tools like jq, jsonata, and terrazzo. Helps with token file creation, resolver configuration, structure, naming conventions, and best practices.
Also in 8 projects that use this
dillonluiSkilldesign-review
Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.
Also in 7 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 7 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- julianoczkowski/designer-skills★ 536same name
- Abhinavbwj/Urban-Design-Skills-Claude★ 131same name
- launchapp-dev/animus-cli★ 39same name
- mshadmanrahman/claude-for-designers★ 32same name
- podo/design-agent-skills★ 32same name
- jhy0285/monofield★ 6same name
- BhaskarManam/pstack★ 4same name
- Nihalgraphics/AI-Product-OS-for-UI-UX-Brand-Prototype★ 2same name
- ANT1OFF/gram★ 1same name
- dennisrongo/claude-skills★ 1same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ask-designerSkill
- brand-contextSkill
- brand-imageSkill
- brand-intakeSkill
- brand-systemSkill
- color-systemSkill
- design-craftSkill
- design-critiqueSkill
- design-grillingSkill
- design-routesSkill
- grill-brandSkill
- logo-labSkill
- make-graphicSkill
- type-systemSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Run design-grilling over this tree.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design brief
Most weak graphics come from a missing decision, not a missing skill: nobody said what the one message was, or where it would be seen. This skill settles those decisions in a short interview and writes them down for /make-graphic.
Load the brand-context and design-grilling skills (the Skill tool, or read their SKILL.md). Reply in the user's language. If there is no brand memory, say so and follow brand-context.
Interview
Run design-grilling over this tree. Skip any node the request already answers, and take facts from the brand memory instead of asking (the channels, the audience, the voice).
- Message: the single thing the viewer should do, feel, or know, in one sentence. Two messages mean two graphics.
- Viewer and moment: who sees it, where, in how many seconds (scrolling a feed, walking past a window, holding a package).
- Format: the channel, then its canvas. Confirm current platform specs before fixing a size; they change.
- Copy: which words are supplied, which you write, and in which languages. Mark every claim, price, date, and number as supplied by the human or as a placeholder.
- Required elements: logo version, legal lines, contact, price, a call to action.
- Brand levers: which parts of the brand carry this piece (the color block, the photography, the display type), taken from the brand memory.
- Imagery: supplied photographs, a generated image (Codex's
imagegen, through/brand-image), or code-only shapes and type. - Success test: how the human will judge it, stated in terms a check can answer (readable at 200 px wide, the offer is the first read, the logo has clear space).
- Constraints and variants: print specs and bleed, deadline, the sizes to adapt it to.
Write
The interview writes to the brief and never to the brand memory. Save brand/briefs/<yyyy-mm-dd>-<slug>.md with one heading per node above (Message, Viewer and moment, Format, Copy, Required elements, Brand levers, Imagery, Success test, Constraints and variants), the human's words quoted where they chose them, and the success test as a checklist. Read it back in plain words and get an explicit yes.
The brief is done when the message fits one sentence, the canvas size is fixed, every number or claim in the copy has a named source, and the success test is checkable. Then tell the human to run /make-graphic on it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.