creative-brief
Create or refine a creative brief that bridges discovery and execution. Use this skill whenever the user is starting a new project, kicking off a website, beginning a brand build or redesign, briefing a designer or developer or AI agent, or trying to align a team before building. Triggers on creative brief, design brief, brand brief, project kickoff, kicking off, briefing the team, project intake, design direction, brief the designer, brief the dev, where do we start, how do we start, write a brief, project overview, scope this project, align on direction. Also triggers when the user has a vag
Profile →npx skills add rampstackco/claude-skills --skill creative-brief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Creative Brief Bridges discovery and execution. Translates "we want a website" into a brief a designer, developer, or AI agent can actually run with. --- ## When to use - Starting a new project (website, app, brand, campaign) - Kicking off a redesign or rebrand - Handing work to a designer, developer, or AI agent - Aligning a team that has drifted off course - Turning a vague idea into something buildable ## When NOT to use - The user is asking a one-off design question (use `design-standards`) - The user wants a PRD or dev ticket (use `pm-spec-writing`) - The user is doing initial research and has not decided what they are building (use `brand-discovery` first) - The user just wants you to write copy (use `content-and-copy`) - The user already has scope and constraints settled and needs deeper aesthetic direction specifically (use `creative-direction` for the structured aesthetic axes) --- ## Required inputs A brief needs answers to ten questions. Before writing, confirm you have answers (or can elicit them) for: 1. What is the project? 2. Why does it exist? What problem does it solve? 3. Who is the audience? 4. What do you want them to do, feel, or know? 5. What is the personal
- When to use
- When NOT to use
- Required inputs
- The framework: brief structure
- 1. Snapshot
- 2. Audience
- 3. Objectives
- 4. Key message
- 5. Voice and tone
- 6. Visual direction
- 7. Scope and deliverables
- 8. Constraints
- 9. Inspiration and competitors
- 10. Approval
What does the creative-brief skill do?
Create or refine a creative brief that bridges discovery and execution. Use this skill whenever the user is starting a new project, kicking off a website, beginning a brand build or redesign, briefing a designer or developer or AI agent, or trying to align a team before building. Triggers on creative brief, design brief, brand brief, project kickoff, kicking off, briefing the team, project intake, design direction, brief the designer, brief the dev, where do we start, how do we start, write a brief, project overview, scope this project, align on direction. Also triggers when the user has a vag
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill creative-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.