creative-direction
Walk the user through four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition) and produce a structured aesthetic brief that downstream content, copy, design, and art-direction skills consume as required input. The aesthetic depth layer, distinct from `creative-brief` (operational kickoff: scope, audience, deliverables, constraints). Use when a project needs aesthetic coherence across many small decisions and the user has only a vague feeling, or when multiple downstream aesthetic-producing skills need a shared brief. Triggers on creative direction,
Profile →npx skills add rampstackco/claude-skills --skill creative-direction --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 Direction Frameworks produce competent output. Coherent output requires a brief. This skill turns vague creative intent into a structured brief that downstream skills can reference. It does not generate taste. It captures direction, so the dozens of small decisions a project requires (word choice, image selection, white space, sequencing, what to leave out) all answer to the same question. --- > Worked examples for each axis position can be assembled from any reference brand library that documents tone, aesthetic, audience relationship, and sensory ambition consistently. The framework below describes the four axes; the user's own reference set positions each example along the axes during the brief workflow. --- ## When to use - The start of a multi-touchpoint project (website, brand, campaign, product launch) where aesthetic coherence matters - Before running multiple downstream skills that need to share a unified voice and look - When inheriting a project that has competent execution but feels generic or incoherent - Recalibrating an existing project that has drifted aesthetically over time - When the user is a non-curator who knows what feeling they want but cannot art
- When to use
- When NOT to use
- Required inputs
- The framework: 4 directional axes
- 1. Tone Register
- 2. Aesthetic Philosophy
- 3. Audience Relationship
- 4. Sensory Ambition
- Workflow
- Failure patterns
- Output format
- Reference files
What does the creative-direction skill do?
Walk the user through four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition) and produce a structured aesthetic brief that downstream content, copy, design, and art-direction skills consume as required input. The aesthetic depth layer, distinct from `creative-brief` (operational kickoff: scope, audience, deliverables, constraints). Use when a project needs aesthetic coherence across many small decisions and the user has only a vague feeling, or when multiple downstream aesthetic-producing skills need a shared brief. Triggers on creative direction,
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill creative-direction --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.