rampstackco/claude-skills / skills/creative-direction
creative-direction
VerifiedWalk 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 359 B |
| SKILL.md | skill md | 11.4 KB |
| references/axes-explained.md | markdown | 12.7 KB |
| references/brief-template.md | markdown | 2.0 KB |
| references/example-aesthetic-brief.md | markdown | 6.2 KB |
references/example-aesthetic-brief.md
View on GitHub# Example Aesthetic Brief
A representative completed brief, modeled on a realistic project. Showing how the abstract axes translate into concrete creative direction.
> The brief below is a worked example for "Conversational + Editorial Restrained + Peer + Considered" applied to a developer-tool marketing site. Compare it against any rendered marketing site that hits these axis positions to see how the abstract axes translate into concrete decisions: copy register, typographic restraint, image treatment, page density, and rejection list.
---
# Observatory Marketing Site Brief
## Project
**Name:** Observatory marketing site redesign
**Description:** Rebuild the marketing site for an open-source observability tool aimed at senior infrastructure engineers. The current site reads like every other developer SaaS site (gradient hero, "trusted by" logo wall, three-column feature grid, code snippet, testimonials, signup CTA). The new site needs to feel like the team behind it actually understands the problem space, not like a marketing team built a site about a tool they have not used.
**Target audience:** Senior platform engineers, infrastructure leads, and SRE managers at companies with 50 to 500 engineers. They evaluate observability tools for their team. They are skeptical of marketing claims and value technical depth. They will read documentation before they evaluate the product.
**Business goal:** Increase qualified evaluation requests from engineering decision-makers, where "qualified" means the requester has authority to influence vendor selection and is in active evaluation. Volume of low-intent signups is not the goal. Quality and intent are.
---
## The four axes
### Tone Register: Conversational
The audience is fatigued by both stiff vendor copy ("enterprise-grade reliability") and aggressive performance copy ("10x your observability"). Conversational treats the reader as a peer engineer who can read between the lines.
### Aesthetic Philosophy: Editorial Restrained
The category is visually loud. Dashboards, gradient heroes, neon accents, animated charts. The differentiation is opposite: low color count, generous white space, considered typography, single definitive image instead of dashboard screenshots above the fold. The site reads like documentation that decided to be a marketing site, not the other way around.
### Audience Relationship: Peer
These engineers do not need to be educated on observability. They need to be respected as practitioners. Authority voice would be condescending. Companion voice would be saccharine. Peer voice acknowledges that we and they are figuring out the same hard problems.
### Sensory Ambition: Considered
Functional would underdeliver; the audience expects a marketing site to be more than a feature list. Resonant is too much; this is not a brand campaign, it is a tool evaluation. Considered means the craft is visible (typography, restraint, the right photograph in the right place) without the site asking for an emotional response.
---
## Synthesis
This brief produces a marketing site that reads like a thoughtful engineering blog post the team happened to design well. Body copy is in first-person plural, contractions are fine, and technical terms appear without quotation marks (the audience uses them naturally, the site should too). Visual density is intentionally low, with a single hero image instead of a product screenshot grid, and pages that breathe rather than fill. There is no logo wall above the fold. There are no testimonials styled as ad copy. The product makes its case through clear documentation links, an honest comparison page, and a "how this differs from what you are already using" section that is willing to say what the tool is not for.
The site refuses several conventions of the category. No animated dashboard hero. No "trusted by" logos as the second module. No three-column feature grid with checkmarks. No popup. No newsletter modal. The site assumes the reader will find the product if it is genuinely useful, and that the marketing's job is to be clear, not to be loud.
---
## Inspiration references
- **Linear's marketing site (linear.app)** - Demonstrates Conversational + Polished Standard + Peer well. The Observatory site borrows the calm density and the willingness to write in first person, but pushes further toward Editorial Restrained on the aesthetic axis.
- **Vercel's marketing pages** - Useful for how they handle technical depth without overwhelming. The product surfaces in code, not in dashboard mockups.
- **Stripe's documentation** - The reference for how documentation can be a marketing asset. Observatory's marketing site borrows the sense that good docs are a brand decision, not just a product decision.
- **The Economist's editorial design** - Aesthetic reference for restraint, considered typography, and the use of a single editorial photograph as a hero treatment instead of a dashboard screenshot.
---
## Rejection list
This brief explicitly says no to:
- No "trusted by" logo wall, especially above the fold
- No gradient hero. Solid color or a single restrained photograph instead
- No three-column feature grid with checkmark icons
- No product dashboard mockup as the hero image
- No animated chart components scattered through the page
- No exit-intent modal, newsletter popup, or any popup of any kind
- No testimonials with headshots arranged in a grid
- No marketing-speak: "enterprise-grade," "blazing fast," "world-class," "industry-leading"
- No "AI-powered" framing. The product uses ML; that is not the lead
- No corporate stock photography of people in offices
- No vague "join the future" CTAs. Specific verbs only
---
## Open questions
- The comparison page is committed to but the comparators are not yet selected. Decision needed before `landing-page-copy` runs on that page.
- The hero image needs custom photography or commissioned illustration. Considered Restrained does not support stock. Budget question for the team.
- The pricing page is not yet scoped. Brief should be confirmed before that page is built; pricing pages have their own conventions.
- Author bylines are part of the documentation but not the marketing site yet. Worth deciding whether marketing pieces carry author attribution.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |