agentleFS
tesslagoblintesslagoblin/fashion-brand-claude-skills/skills/design-brief/SKILL.md

design-brief

Skill0 starsChanged 50 days agoMITView on GitHub

Two halves of the campaign design brief. (A) Direction: picks a 2-4 color palette, fonts, and aesthetic notes for a campaign from your brand reference. (B) Cards: turns the finished lockup slides in a campaign deck into one design-brief card per lockup on your project board, with reference images attached, drafted for review before anything reaches the design team. Trigger: design brief, lockup brief, design direction, color palette for this campaign, font suggestions, turn the lockup slides into brief cards, make the lockup cards.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brief-to-tasks, design-flow and 7 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

    brief-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

  • launchapp-devSkill

    color-system

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

    Also in 3 projects that use this

  • ilikescienceSkill

    design-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

  • dillonluiSkill

    design-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

  • 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

  • +1 more from julianoczkowski

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Palette: Start from the mood's frozen row in the brand reference.

    line 45
  2. Distinctive:

    Color swatches go on the card as images,: never as "see the slide". If swatches are drawn as shapes, render the slide and crop them to an …

    line 75
  3. Distinctive:

    Give the design team a heads-up: when a batch lands, and check the cards are still in place the next day.

    line 91
  4. Distinctive:

    Never overwrite a calendar link that is already set.

    line 99
  5. Distinctive:

    Keep all intermediate files UTF-8.

    line 105

“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

Design Brief

Part A writes design direction into the campaign deck. Part B takes the finished lockup slides out of the deck and turns them into brief cards your designers work from. Run A while planning, B once the deck is signed off.

Setup

brand_reference: "[FILL IN]"        # the brand-guardrails reference (palettes, fonts, per-mood starting points)
deck_tool: "[FILL IN]"              # Google Slides, PowerPoint, Figma...
lockup_slide_title: "[FILL IN]"     # e.g. "Campaign Graphic"; the text that marks a lockup slide
project_board: "[FILL IN]"          # Basecamp, Asana, Monday, Trello, Jira...
draft_location: "[FILL IN]"         # your own board/column where drafts land first
design_queue: "[FILL IN]"           # the design team's column where approved briefs go
design_owner_role: "[FILL IN]"      # e.g. "design manager" (assignee on promotion)
asset_owner_role: "[FILL IN]"       # e.g. "content lead" (tagged for imagery)
asset_lead_days: [FILL IN]          # card due date = campaign start minus this, e.g. 14
design_lead_days: [FILL IN]         # design done by campaign start minus this, e.g. 5
no_weekend_dates: true              # a Sat/Sun date rolls back to Friday
card_title_format: "[FILL IN]"      # e.g. "{Campaign} | {Header} | {dates}"
calendar_link_back: "[FILL IN]"     # your sales/promo calendar field for the brief link, or "none"

Inputs

  • Part A: campaign name, mood, priority, and whether it is the core-brand campaign
  • Part B: the deck link (ask if not given) and scope (all lockup slides, or named ones)

Workflow

Part A: design direction (into the deck)

  1. Palette. Start from the mood's frozen row in the brand reference. If filled, use it. If blank, pick 2-4 hex values from the brand palettes, get sign-off, and write them into the table so the next campaign is a lookup.
  2. Fonts. Core-brand campaign: brand fonts only. Other campaigns: a display font suited to the mood (only from the allowed list), with body and caption from the brand guide.
  3. Aesthetic. 2-4 sentences for the designer: type treatment, color use, texture, what to avoid. Tie it to the mood's keywords.

Part B: lockup slides to brief cards

  1. Pull the deck fresh. Extract every lockup slide's text boxes and images with their positions. Image links from slide APIs often expire, so map and post in the same session as the pull.
  2. Build the card title from the campaign header slide just before the lockup (dates, priority) and the lockup's own header line. Placeholders like XX% pass through as written. No priority found: drop that segment and flag it.
  3. Build the body in this order, bold labels, omitting any empty section (no "TBD"):
    1. URL(s) for the collection
    2. Font inspo (the slide's typography field, often images only)
    3. Suggested colors
    4. Main aesthetic
    5. Other elements
    6. Images: a line tagging the asset owner
    7. Copy: eyebrow/sticker, header, CTA, verbatim. A promo code goes on the sticker line next to the sale name, never as its own line.
    8. Sale messaging (sale lines only)
    9. Brand messaging (brand lines only)
    10. A link back to the exact source slide
  4. Match images to sections by position: an image belongs to the nearest field label above it in the same column. Drop decorative images (logos in a corner, anything outside the content columns). When unsure, include it and flag it.
  5. Color swatches go on the card as images, never as "see the slide". If swatches are drawn as shapes, render the slide and crop them to an image.
  6. Multi-drop campaigns: one card equals one design request. One title covering all drops, a shared block up top (URL, "design the system once, swap colors and copy per drop", font options, shared elements), then one section per drop with its colors, aesthetic, copy, and messaging.
  7. Post every card as a draft to draft_location, with the asset-owner tag as plain text so no one gets notified by a draft. Report every card link plus a flags list.
  8. Promote only on the owner's say-so, per card or "promote all": copy to design_queue, assign the design owner, turn the plain-text tag into a real mention, and set dates:
    • card due = campaign start minus asset_lead_days
    • a timeline line: design done by campaign start minus design_lead_days
    • weekend dates roll back to the Friday before
    • a date already in the past means the lockup is behind: flag it
  9. Link back to the calendar (optional). Propose the full lockup-to-calendar-row mapping first and write only after approval. Match on dates first, priority second, name only as a confirm (names drift between deck and calendar).
  10. Give the design team a heads-up when a batch lands, and check the cards are still in place the next day. Unannounced cards get swept aside.

Rules

  • Colors and fonts come from the brand reference only.
  • Brand messaging and sale messaging are separate sections. Never merge them, never repeat a line.
  • The storyline is not part of the brief; the slide link covers it.
  • Never overwrite a calendar link that is already set. Flag it instead.
  • Duplicate lockup slides for one campaign: ask, do not post twice.
  • A real gap to flag: main aesthetic or colors empty, no reference images anywhere, a placeholder left in the copy, or a duplicated slide still carrying another campaign's images. An images-only typography field is normal, not a gap.
  • New lines approved or words vetoed during brief review go back into the brand reference the same day.
  • Keep all intermediate files UTF-8; slide text carries smart quotes.

Output format

Part A:

color_palette: ["#1B2A41", "#E07A5F", "#F4F1EA"]
font_suggestions: display Fraunces Bold; body Inter Regular; caption Inter Medium
aesthetic_direction: Sun-faded photography with a warm film grain. Big serif headline set tight,
  small caps eyebrow. Terracotta only on the CTA. No icons.

Part B card:

Coastline Weekend | 25% Off Linen | 6/12-6/15
Due 5/29 (assets) | design done by 6/5
URL: northwind.example/collections/linen
Font inspo: [2 images]
Suggested colors: [swatch image]
Main aesthetic: Sun-faded, warm, relaxed. Linen texture close-ups.
Other elements: [1 image]
Images: @content lead
Copy:
  Sticker: Linen Weekend | code: TIDE25
  Header: 25% Off Linen
  CTA: Shop Linen
Sale messaging: 25% off the linen edit / Four days. Every linen piece.
Brand messaging: Made for the long way home / Slow mornings, salt air
Source slide: [link]

Example brand: Northwind Apparel.

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.