agentleFS
mshadmanrahmanmshadmanrahman/claude-for-designers/.claude/skills/design-brief/SKILL.md

design-brief

Skill32 starsChanged 49 days agoMITView on GitHub

Turn an interrogated brief into the single source of truth for a design project. Use after /grill-me, before any IA or UI work.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use design-flow, color-system and 1 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.
  • 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

  • launchapp-devSkill

    color-system

    Build a comprehensive color system with palette generation, semantic mapping, and accessibility compliance.

    Also in 3 projects that use this

  • AnthropicSkill

    design-critique

    Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    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
  1. Distinctive:

    Ask these one at a time, and offer a suggested answer with each so a student who is unsure can accept or refine it rather than stall on a …

    line 14
  2. Very specific:

    If a Requirements Handshake exists from /grill-me, pull the confirmed constraints directly into the brief.

    line 16

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are writing a design brief. This is the single source of truth for the project. Everything that comes after this step references it.

First, ask the following if no Requirements Handshake exists from /grill-me:

  • What is the product or feature being designed?
  • Who are the primary users?
  • What emotions should the design evoke when a user succeeds at their task?
  • What does "done" look like for this project?

Ask these one at a time, and offer a suggested answer with each so a student who is unsure can accept or refine it rather than stall on a blank.

If a Requirements Handshake exists from /grill-me, pull the confirmed constraints directly into the brief. Do not re-ask questions that are already answered there.

Then generate a brief with these six sections:

1. Project context What is being built and why now. One paragraph. No vague mission statements.

2. Target user Who this is for. Name a specific person or role, not a demographic range. Include what they care about and what they do not.

3. Emotional tone and design direction The specific emotion the design should produce. Not "clean and modern." Name the actual feeling: confidence, calm, urgency, delight. Then name one reference product that nails that feeling and why.

4. Functional requirements What the design must do. Numbered list. Each item starts with a verb.

5. Constraints What cannot change. Platform, tech stack, existing components, accessibility requirements, legal limits.

6. Success criteria How you will know this worked. Measurable where possible. At minimum: one behavioral signal and one metric.

Be specific throughout. If you cannot be specific, flag it as an open question rather than filling in with vague language.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.