Stats
Actions
Tags
From rampstack-skills
Creates structured creative briefs that align stakeholders before execution. Use for project kickoffs, redesigns, or handing work to designers and developers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rampstack-skills:creative-briefThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bridges discovery and execution. Translates "we want a website" into a brief a designer, developer, or AI agent can actually run with.
Bridges discovery and execution. Translates "we want a website" into a brief a designer, developer, or AI agent can actually run with.
design-standards)pm-spec-writing)brand-discovery first)content-and-copy)creative-direction for the structured aesthetic axes)A brief needs answers to ten questions. Before writing, confirm you have answers (or can elicit them) for:
If you have fewer than five of these, run a quick intake first. See "Eliciting missing info" below.
Output a markdown brief with these ten sections. Keep each section tight. A good brief is two pages, not ten.
One paragraph answering: what, who, why, when. The kind of thing you would say at a kickoff in thirty seconds.
Primary audience first. Include who they are, what they are trying to do, what is blocking them today, and where you reach them. Add secondary audiences only if they materially change the work.
What success looks like. Pair every objective with a measurable signal.
Objective: drive trial signups. Signal: 3 percent conversion from homepage to signup within 30 days of launch.
The one thing you want a visitor to walk away knowing. If they see only the homepage hero and bounce, what should they remember? One sentence.
Pick three to five adjectives. Pair each with what you are NOT (e.g. "confident, not arrogant"). See references/voice-and-tone-guide.md for frameworks and worked examples.
Mood, palette, type, and imagery direction. Three to five reference URLs are worth more than 500 words. Note what you like AND what you would reject.
A bulleted list of what is being made. Be specific. "Homepage" is not a deliverable. "Homepage with hero, three feature blocks, testimonial carousel, and contact CTA" is.
Time. Budget. Technical (existing stack, required integrations, hosting). Brand (logo, colors, fonts that must be used). Legal (compliance, accessibility level required).
Three to five sites or brands you want to feel like, three to five you want to feel different from. Note WHY for each.
Who signs off. What artifact triggers sign-off (a Figma file, a staging URL, a PDF). What happens if there is no sign-off by a deadline.
If the user comes with a partial answer (e.g., "I want a website for my coffee shop"), do not just write a generic brief. Ask. Use these prompts.
For audience
For objectives
For voice
For visuals
For scope
Do not ask all of these. Pick the ones that fill the actual gaps.
references/creative-brief-template.md as the structure. Keep it under 1500 words.creative-brief.md in the project root. Offer to make it a Word doc or PDF if the user wants something to share with stakeholders.creative-direction next. It produces a structured aesthetic brief using four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition) that content, copy, and art-direction skills consume directly.When the user's input matches one of these patterns, push back before writing.
Default output is a markdown file at creative-brief.md in the project root. Structure follows the template exactly.
If the project is large, split: keep the main brief under 1500 words and put detail in linked appendices (audience-research.md, brand-guidelines.md, etc.). Briefs that try to be everything end up read by no one.
references/creative-brief-template.md - Fillable template. Copy and use as the starting point.references/voice-and-tone-guide.md - Voice frameworks, brand archetypes, and worked patterns.references/example-brief.md - A worked example for a fictional B2B SaaS, showing what a "good" filled brief looks like.Read the template before drafting. Read the voice guide if the user has not already specified a voice. Read the example if you are unsure how filled-out a section should be.
npx claudepluginhub rampstackco/claude-skills --plugin rampstack-skillsGenerates design briefs for UX/UI and product design projects covering overview, goals, user personas, constraints, success criteria, and deliverables. Includes generate/validate scripts.
Guides you through writing a human-centered design brief including challenge statements, audience definition, and stakeholder alignment.
Walks through four directional axes (tone, aesthetic, audience, sensory ambition) to produce a structured aesthetic brief. Use when a project needs aesthetic coherence across many small decisions and the user has only a vague feeling, or when multiple downstream skills need a shared brief.