Frontend Slides
zarazhangrui/frontend-slides
Builds animated HTML slide decks that run in the browser with no dependencies, or converts PowerPoint files to the web, starting from visual style previews.
Create or refine a creative brief that bridges discovery and execution.
MITAuto-check passed
Install Creative Brief
$ npx skills add rampstackco/claude-skills --skill creative-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rampstackco/claude-skills creative-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative-brief .claude/skills/creative-brief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "creative-brief" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/creative-brief into .claude/skills/creative-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creative-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rampstackco/claude-skills/tree/main/skills/creative-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rampstackco/claude-skills --skill creative-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rampstackco/claude-skills creative-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/creative-brief .agents/skills/creative-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "creative-brief" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/creative-brief into .agents/skills/creative-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creative-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rampstackco/claude-skills --skill creative-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rampstackco/claude-skills creative-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/creative-brief .cursor/skills/creative-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "creative-brief" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/creative-brief into .cursor/skills/creative-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creative-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rampstackco/claude-skills.git --path skills/creative-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rampstackco/claude-skills --skill creative-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rampstackco/claude-skills creative-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/creative-brief .gemini/skills/creative-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "creative-brief" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/creative-brief into .gemini/skills/creative-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creative-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rampstackco/claude-skills creative-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rampstackco/claude-skills --skill creative-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/creative-brief .github/skills/creative-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "creative-brief" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/creative-brief into .github/skills/creative-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creative-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rampstackco/claude-skills --skill creative-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rampstackco/claude-skills creative-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/creative-brief .opencode/skills/creative-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "creative-brief" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/creative-brief into .opencode/skills/creative-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creative-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
creative-brief- GitHub stars
- 935
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,148 words
- Files
- 5 (incl. references)
- Skills in repo
- 103
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create or refine a creative brief that bridges discovery and execution.
- Works in 10 steps: Snapshot → Audience → Objectives → …
- The user is starting a new project
- SKILL.md covers When to use, When NOT to use, Required inputs and The framework: brief structure, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Creative Brief is an agent skill from rampstackco/claude-skills. 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…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `README.md`, `references/creative-brief-template.md` and `references/example-brief.md`).
The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.
When your agent uses it
- The user is starting a new project
- Kicking off a website
- Beginning a brand build
- Briefing a designer
Example prompts
- “/creative-brief”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 482c9bf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Creative Brief loads about 2.1k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 179 tokens; SKILL.md has 1,148 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 1,148 words, ~2,074 tokens.
Download SKILL.mdSave it as
.claude/skills/creative-brief/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- creative-brief
- description
- 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 vague idea and needs to make it concrete enough to hand off, even if they do not say 'brief' explicitly.
- category
- strategy-and-discovery
- catalog_summary
- Project briefs that align stakeholders before work starts
- display_order
- 2
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-discoveryfirst) - 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-directionfor the structured aesthetic axes)
Required inputs
A brief needs answers to ten questions. Before writing, confirm you have answers (or can elicit them) for:
- What is the project?
- Why does it exist? What problem does it solve?
- Who is the audience?
- What do you want them to do, feel, or know?
- What is the personality? How does it sound?
- What is the visual direction? How does it look?
- What is in scope? What is out?
- What are the constraints (time, budget, technical, brand)?
- What does success look like?
- Who approves?
If you have fewer than five of these, run a quick intake first. See "Eliciting missing info" below.
The framework: brief structure
Output a markdown brief with these ten sections. Keep each section tight. A good brief is two pages, not ten.
1. Snapshot
One paragraph answering: what, who, why, when. The kind of thing you would say at a kickoff in thirty seconds.
2. Audience
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.
3. Objectives
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.
4. Key message
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.
5. Voice and tone
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.
6. Visual direction
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.
7. Scope and deliverables
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.
8. Constraints
Time. Budget. Technical (existing stack, required integrations, hosting). Brand (logo, colors, fonts that must be used). Legal (compliance, accessibility level required).
9. Inspiration and competitors
Three to five sites or brands you want to feel like, three to five you want to feel different from. Note WHY for each.
10. Approval
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.
Eliciting missing info
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
- Who is the single most likely person to land on this site? Walk me through their day.
- If you could pick one type of customer to fill your inbox, who?
- Who do you NOT want to attract?
For objectives
- Pretend it is six months after launch. What number tells you it worked?
- What is the one action you most want a visitor to take?
For voice
- Pick three brands or people whose tone you would want to borrow.
- If your site were a person at a dinner party, what would they sound like?
For visuals
- Show me three sites you love. What do you love about them?
- Show me one site you hate. Why?
For scope
- If you only got one page, which one?
- What would you cut if the budget were halved?
Do not ask all of these. Pick the ones that fill the actual gaps.
Show full SKILL.md (412 more words)Show less
Workflow
- Read the conversation. Pull every fact already given. Do not ask questions you can answer from context.
- Identify gaps. Which of the ten required inputs are missing or thin?
- Run intake. Ask three to five targeted questions to fill the gaps. Group related questions to keep the conversation tight.
- Draft the brief. Use
references/creative-brief-template.mdas the structure. Keep it under 1500 words. - Stress-test. Before delivering, check the brief against the failure patterns below. If any apply, revise before showing the user.
- Deliver. Save as
creative-brief.mdin the project root. Offer to make it a Word doc or PDF if the user wants something to share with stakeholders. - Hand off for aesthetic depth (optional). For projects where sections 5 (voice and tone) and 6 (visual direction) need more rigor than this brief surfaces, run
creative-directionnext. 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.
Failure patterns
When the user's input matches one of these patterns, push back before writing.
- "We want to be the [giant brand] of [our niche]." Ask what specifically about that brand they want to borrow. Probably one or two things, not the whole thing.
- Audience as "men and women 18-65." This is not an audience. Ask for the single most valuable customer type and start there.
- "Increase awareness" with no metric. Awareness of what, by whom, measured how? Push for a number.
- "Modern, clean, minimalist." These words are meaningless. Ask for three specific URLs they think look right.
- Twenty pages of context, no clear ask. Ask: "If a designer reads only one paragraph, what should it be?" Then make that the snapshot.
Output format
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.
Reference files
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.
© rampstackco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/creative-brief of rampstackco/claude-skills.
- SKILL.md
- README.md
- references/creative-brief-template.md
- references/example-brief.md
- references/voice-and-tone-guide.md
Open the folder on GitHubat commit 482c9bf
Compare with similar skills
Creative Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Creative Brief this skillrampstackco/claude-skills | 935 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Frontend Slideszarazhangrui/frontend-slides | 30k | 16 repos | ~7k | Automated safety check: Pass | MIT | |
| Algorithmic Art with p5.jsanthropics/skills | 180k | 37 repos | ~4.9k | Automated safety check: Pass | Apache-2.0 | |
| Canvas Designanthropics/skills | 180k | 51 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 27 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Brand and Design Toolkitnextlevelbuilder/ui-ux-pro-max-skill | 134k | 1 repos | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Algorithmic Art with p5.js
anthropics/skills
Creates original generative art in two steps: a written algorithmic philosophy, then a p5.js sketch with seeded randomness and an interactive viewer for exploring parameters.
- Official
Canvas Design
anthropics/skills
Creates original posters and static art as PNG or PDF by first writing a short design philosophy, then expressing it visually on a canvas.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Brand and Design Toolkit
nextlevelbuilder/ui-ux-pro-max-skill
Bundles design tasks behind one skill: brand identity, tokens, UI styling, logos, corporate identity mockups, slides, banners, icons and social images.
HyperFrames Animation
heygen-com/hyperframes
Collects motion rules, scene blueprints, transitions and runtime adapters for HyperFrames video compositions, with GSAP as the default animation runtime.
More from rampstackco/claude-skills
All 103 skills in this repoAfter Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
Analytics Strategy
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
Brand Style Guide
rampstackco/claude-skills
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.
Brand Voice
rampstackco/claude-skills
Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.
Content And Copy
rampstackco/claude-skills
Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.
Content Strategy
rampstackco/claude-skills
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.
Questions about Creative Brief
What does Creative Brief do?
Create or refine a creative brief that bridges discovery and execution. Creative Brief is an agent skill from rampstackco/claude-skills. Create or refine a creative brief that bridges discovery and execution.
When should I use Creative Brief?
Creative Brief fits situations like: the user is starting a new project; kicking off a website; beginning a brand build; briefing a designer.
How do I install Creative Brief in Claude Code?
Run `npx skills add rampstackco/claude-skills --skill creative-brief -a claude-code`. Or copy the skill folder (skills/creative-brief in rampstackco/claude-skills) into .claude/skills/creative-brief in your project. Claude Code loads it when a task matches its description.
How do I install Creative Brief in Codex?
Run `npx skills add rampstackco/claude-skills --skill creative-brief -a codex`. Or copy the skill folder (skills/creative-brief in rampstackco/claude-skills) into .agents/skills/creative-brief in your project. Codex loads it when a task matches its description.
Can I use Creative Brief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rampstackco/claude-skills --skill creative-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creative-brief, .gemini/skills/creative-brief, .github/skills/creative-brief and .opencode/skills/creative-brief in your project.
What does Creative Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Creative Brief is instructions for the agent only.
Does Creative Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Creative Brief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Creative Brief use?
Creative Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Creative Brief use?
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.7k tokens, read only when the agent opens those files.
What are the alternatives to Creative Brief?
Skills that share tags, products or a category with Creative Brief: Frontend Slides (zarazhangrui/frontend-slides, 30k stars), Algorithmic Art with p5.js (anthropics/skills, 180k stars), Canvas Design (anthropics/skills, 180k stars) and Impeccable (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Creative Brief?
rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 935 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.
Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.