ClaudeSuperPower
SubmitLog in

creative-direction

Skill

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 `cre

0Writing

Install

git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/creative-direction

What is 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, aesthetic direction, set the aesthetic, define the visual direction, what's the vibe, what's the tone, the four axes. Does NOT fire for a general kickoff brief (use `creative-brief`), tactical single-piece work, already-documented direction, purely functional output, or locked production-stage work.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~225 tokens of context used while enabled, before you invoke anything

Documentation

README · ~7 min read

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

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

agent-sdk-verifier-ts

Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.

32.8K stars

comment-analyzer

Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes (1) after generating large documentation comments or docstrings, (2) before finalizing a pull request that adds or modifies comments, (3) when reviewing existing comments fo

32.8K stars

agent-sdk-verifier-py

Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.

32.8K stars