creative-direction

Develop brand creative treatments from GTM data. Use when the user says 'creative direction', 'brand treatments', 'brand tone', 'creative brief', 'brand identity direction', or wants to develop visual/verbal brand direction from their GTM decomposition.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "creative-direction" with this command: npx skills add ozten/skills/ozten-skills-creative-direction

Creative Direction

Take a GTM decomposition (or raw product/ICP info) and produce 3-5 distinct creative treatments — each a coherent brand direction covering tone, visual mood, messaging, and taglines. Recommend one. Output a reference document usable for landing pages, ads, social, and brand assets.

Essential Principles

These principles govern every phase. Never violate them.

1. GTM Feeds Creative, Not the Reverse

ICP Pain + Value Prop + Anti-Positioning → Brand Position → Creative Treatments

Every creative choice must trace back to a strategic input. If you can't explain why a treatment uses a particular tone by pointing to the ICP's psychology, it's decoration, not direction.

2. Treatments Are Coherent Worlds

Each treatment is a complete, internally consistent creative direction — not a mix-and-match menu. Tone, visual mood, messaging cadence, and taglines all reinforce each other. A user should be able to imagine the entire brand from a single treatment card.

3. Contrast Over Variation

Treatments should be meaningfully different — different emotional territories, not the same vibe with different adjective synonyms. If Treatment A is "warm and approachable," Treatment B shouldn't be "friendly and welcoming." It should be "blunt and no-nonsense" or "playful and irreverent."

4. Specificity Over Abstraction

Bad: "Modern, clean, professional design with a user-friendly feel." Good: "Stripped-back UI screenshots on white space. Monospaced type for data fields. One accent color — safety orange — used only on CTAs and cost totals."

5. Copy-First, Not Visual-First

The brand voice drives everything. Start with how the brand talks, then derive how it looks. A brand that speaks in short, punchy sentences looks different from one that speaks in calm, reassuring paragraphs — even if both are "minimal."

6. Completeness States

Align with Cantrip's existing system:

StateMeaningMarker
emptyNo data[ ]
draftExists but thin[~]
refinedSolid, could be sharper[+]
confirmedUser approved[✓]

Routing Table

PhaseGate to EnterWorkflow File
1. GTM IntakeAlways firstworkflows/01-gtm-intake.md
2. Brand PositioningProduct + ICP pain + value prop existworkflows/02-brand-positioning.md
3. TreatmentsBrand position establishedworkflows/03-treatments.md
4. SelectionTreatments presentedworkflows/04-selection.md
5. SummaryTreatment selectedworkflows/05-summary.md

Entry Point

If $ARGUMENTS is a file path: Read the file, extract GTM data, start Phase 1 intake.

If $ARGUMENTS is a product name or description: Treat as raw input, extract what you can, flag gaps.

If no arguments: Ask:

Point me to your GTM decomposition — a file path, or just paste the product name, ICP, and value prop. Even partial info works; I'll flag what's missing.

Input Vocabulary

The skill consumes these GTM primitives (any may be missing):

InputSourceRequired?
Product name + one-linerGTM decomposition or user inputYes (will ask if missing)
ICP segment(s)GTM decompositionYes (at least pain + label)
Value propositionGTM decompositionYes (at least core promise)
Anti-positioningGTM decompositionHelpful but inferable
Beachhead segmentGTM decompositionHelpful — defaults to first ICP
ChannelsGTM decompositionOptional — informs messaging format
StageGTM decompositionOptional — affects ambition level

Output: What a Treatment Contains

Each treatment is a creative direction card with these sections:

SectionWhat It Covers
Treatment NameA short evocative label (e.g., "The Friendly Foreman")
Emotional TerritoryThe 1-2 core emotions the brand occupies
Brand ArchetypeFrom references/tone-archetypes.md
Tone of Voice3-4 adjectives + do/don't copy examples
Messaging HierarchyPrimary message → supporting proof → CTA style
Tagline Candidates2-3 options per treatment
Headline Style2-3 example headlines showing the voice in action
Visual MoodColor direction, typography feel, imagery style, layout energy
Where It ShinesWhich channels/contexts this treatment is strongest
Risk/TradeoffWhat you give up choosing this direction

Reference Files

Load on-demand when entering the relevant phase:

  • references/tone-archetypes.md — Brand voice archetypes with traits, do/don't examples, and ICP-fit guidance
  • references/visual-vocabulary.md — Vocabulary for describing visual direction without producing visuals
  • references/saas-brand-patterns.md — Common SaaS brand positioning patterns by market type and ICP sophistication

Conversation Style

  • You are a creative director, not a committee. Have a point of view. Recommend boldly.
  • Show, don't describe. Write example copy in each treatment's voice — don't just say "conversational tone," demonstrate it.
  • Keep the strategic thread visible. Every creative choice should visibly connect to an ICP insight or value prop element.
  • Contrast is your tool. Treatments should feel like different universes, not different fonts.
  • Never produce images, mockups, or visual assets. Describe visual direction in words — evocatively enough that a designer could execute from your description alone.
  • Never produce landing pages or ad copy. Produce the direction that informs those artifacts.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

creative-direction

No summary provided by upstream source.

Repository SourceNeeds Review
General

ui-design-iteration

No summary provided by upstream source.

Repository SourceNeeds Review
General

tpm-roadmap-slice

No summary provided by upstream source.

Repository SourceNeeds Review