MCP HubMCP Hub
SKILL·870343

art-direction

rampstackco
更新日 27 days ago
1 閲覧
953
132
953
GitHubで表示
メタaidesign

について

このスキルは、承認されたブランドアイデンティティに基づき、写真、イラストレーション、動画といった具体的な視覚的成果物の制作を指揮します。ユーザーがクリエイティブ担当者へのブリーフィング、キャンペーンコンセプトの開発、またはクリエイティブ作品の適合性評価を必要とする際に発動します。高次のブランド美学を具体的なアセットへと展開するために使用し、プロジェクト全体の美的指針は`creative-direction`スキルが担当します。

クイックインストール

Claude Code

推奨
メイン
npx skills add rampstackco/claude-skills -a claude-code
プラグインコマンド代替
/plugin add https://github.com/rampstackco/claude-skills
Git クローン代替
git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/art-direction

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

Art Direction

Direct creative work that extends the brand into specific deliverables. Photography, illustration, video, motion, campaigns, environmental design.

This skill assumes brand identity is approved (brand-identity complete). Art direction is about applying and extending it, not defining it.


When to use

  • Briefing photographers, illustrators, videographers
  • Developing campaign creative concepts
  • Directing in-house creative teams
  • Writing creative direction documents for vendors
  • Evaluating creative deliverables for brand fit
  • Adapting brand visual identity to a new format or context

When NOT to use

  • Setting project-wide aesthetic direction across multiple downstream skills (use creative-direction instead). This skill briefs specific creative deliverables; creative-direction produces the structured aesthetic brief that this skill consumes.
  • Defining brand visual identity from scratch (use brand-identity)
  • Day-to-day component design (use design-standards)
  • Writing copy for creative work (use content-and-copy or landing-page-copy)
  • Building a design system (use design-system)

Required inputs

  • The deliverable (photo shoot, illustration set, video, campaign)
  • The brand identity (visual system, voice, imagery direction)
  • The audience for this specific work
  • The goal (brand awareness, conversion, education, emotional connection)
  • Budget and timeline
  • Distribution context (where it will be seen)

The framework: 5 layers

A creative brief covers five layers. Each must be clear before the brief leaves your hands.

1. The story

What this creative work is fundamentally about.

  • The premise. The core idea in one sentence.
  • The emotional through-line. What the audience feels.
  • The role of the brand. How the brand shows up in the story.
  • The takeaway. What the audience walks away with.

A weak premise produces work that's pretty but says nothing. Spend time here.

2. The look

The visual treatment.

For photography:

  • Subject and composition (close-up, environmental, candid, posed)
  • Lighting (natural, studio, dramatic, soft)
  • Color palette (true color, treated, monochrome)
  • Locations (specific or general direction)
  • Wardrobe and props
  • Mood references (the photo brief template sets how many)

For illustration:

  • Style (flat, dimensional, hand-drawn, geometric, abstract)
  • Color use (full palette, restricted, brand-only)
  • Line treatment
  • Composition style
  • Detail level
  • Reference artists or works, with explicit "we want like X but NOT like Y" (the illustration brief template sets how many)

For video / motion:

  • Pacing (slow, medium, fast cuts)
  • Camera movement (static, handheld, sweeping)
  • Color grading
  • Transitions and effects
  • Audio direction (music, voiceover, ambient)
  • Reference work (3 to 5 examples; no template covers motion, so this count is the one to use)

3. The execution

Production-level direction.

Specifications:

  • Deliverable formats and sizes (web hero, social square, print full-page)
  • Required shots or frames
  • Optional shots if budget allows
  • Wardrobe and prop list (for live action)
  • Color and asset specs (RGB, CMYK, hex codes for matching)

Constraints:

  • Things to avoid (specific cliches, forbidden treatments, regulatory)
  • Brand-system requirements (logo placement, color use, type rules)

4. The variants

How this creative scales across distribution.

Most creative needs to live in multiple places. Plan the variants up front.

Common variant set for a campaign:

  • Hero web image (16:9 or wider)
  • Mobile web hero (4:5 or 1:1)
  • Social square (1:1)
  • Social vertical (9:16)
  • Email banner (3:1 typical)
  • Display ad sizes (300x250, 728x90, etc.)
  • Print sizes if applicable

For each variant, note: how the composition adapts, what gets cropped or repositioned, what assets are required.

5. The standards

The quality bar.

Technical:

  • Resolution and format requirements
  • Color profile
  • File naming conventions
  • Delivery format (raw + edited, layered files, exported variants)

Creative:

  • What "approved" looks like (specific examples of acceptable work)
  • What "not approved" looks like (specific examples to avoid)
  • Number of revision rounds budgeted

Workflow

For briefing external creative

  1. Confirm the inputs. Brand identity locked. Audience and goal clear. Budget and timeline known.
  2. Develop the concept. Premise, emotional through-line, takeaway.
  3. Build the look. Mood references. Specific direction on style elements.
  4. Write the spec. Production-level direction. Variants. Constraints. Licensing and usage rights, agreed before the shoot or the first sketch, not after: both brief templates make licensing a pre-production section for the reason that renegotiating it against finished work costs more.
  5. Brief the vendor. In writing. Walk through it live. Allow questions.
  6. Review milestones. Treatment review, halfway review, final review. Don't skip the early reviews; corrections compound.
  7. Approve and document. What was produced, and confirmation that it shipped under the licensing agreed at step 4.

For directing in-house creative

  1. Same brief, lighter format. In-house direction can be more iterative. Still document the brief.
  2. Co-create. In-house teams know the brand. Use their judgment. Don't over-direct.
  3. Establish review rhythm. Daily check-ins for fast work, weekly for longer projects.

For evaluating existing creative

  1. Score against the brief. Did the work hit the brief? Where did it deviate?
  2. Score against the brand. Does this look like the brand? Could this be confused with a competitor?
  3. Score against the goal. Will this drive the intended outcome?
  4. Identify fixes. What can be improved? What's a deal-breaker vs. acceptable?

Failure patterns

  • "Modern, clean, minimal" briefs. Means nothing. Force specificity. Use specific reference brands, named artists, or visual examples.
  • No "what to avoid" direction. Vendors interpret broadly. Tell them what's out of bounds explicitly.
  • Reference imagery that's actually competitor work. You'll get something that looks like the competitor. Never use direct competitors as references.
  • Skipping early reviews. Every revision late in the process is 5x more expensive than catching issues at treatment stage.
  • Too many cooks. 6 stakeholders all giving creative feedback produces incoherent work. Concentrate creative authority.
  • Ignoring distribution. Creative that doesn't work in the actual contexts where it will live is failed creative.
  • No variant planning. Discovering at delivery that you need a square crop and the photographer composed for 16:9 only.
  • Approving creative that's "fine." Fine is the enemy of distinctive. If it doesn't move you, it won't move the audience.

Output format

Default output is a creative brief at creative-brief-[project].md, written against one of the brief templates in references/. The template you pick is the structure: use references/photo-shoot-brief.md for photography, references/illustration-brief.md for illustration, and references/creative-brief-template.md for anything else or for a mixed production. Each template owns its own section list, section order, and reference-image count. Do not write to the five-layer outline below and hope it maps; the templates carry sections the layers do not, licensing and usage rights among them, and those sections are load-bearing before production starts, not after it.

The five layers are the thinking. Every template covers all five, in its own order:

  1. The story (premise, through-line, role of brand, takeaway)
  2. The look (visual treatment with references)
  3. The execution (specs, variants, constraints)
  4. The standards (quality bar, examples of acceptable and unacceptable)
  5. The logistics (timeline, milestones, budget, deliverables, licensing and usage rights)

Plus a separate moodboard or visual reference doc with images, at the count the chosen template gives.


Reference files

GitHub リポジトリ

rampstackco/claude-skills
パス: dist/codex/.agents/skills/art-direction
0
agent-skillsai-agentsanthropicclaudeclaude-aiclaude-code
FAQ

よくある質問

art-direction Skillとは何ですか?

art-direction はrampstackco が作成した Claude Skillです。Skillは、Claudeが必要に応じて読み込む指示とリソースをまとめ、追加の指示なしで art-direction に関連するタスクを実行できるようにします。

art-direction をインストールするには?

このページのインストールコマンドを使用してください。art-direction をプラグインとして Claude Code に追加するか、リポジトリを skills ディレクトリにクローンし、Claudeを再起動してSkillを読み込みます。

art-direction はどのカテゴリに属しますか?

art-direction は メタ カテゴリに属します。

art-direction は無料で利用できますか?

はい。art-direction は AIMCP に掲載されており、無料でインストールできます。

関連スキル

content-collections
メタ

このスキルは、Content Collections(Markdown/MDXファイルを型安全なデータコレクションに変換するTypeScriptファーストのツール)の本番環境でテストされた設定を提供します。Zodバリデーションによる型安全性を実現し、ブログ、ドキュメントサイト、コンテンツ重視のVite + Reactアプリケーション構築時にご利用ください。Viteプラグインの設定、MDXコンパイルから、デプロイ最適化、スキーマバリデーションまで、すべてを網羅しています。

スキルを見る
polymarket
メタ

このスキルは、開発者がPolymarket予測市場プラットフォームを活用したアプリケーション構築を可能にします。API統合による取引や市場データの取得に加え、WebSocketを介したリアルタイムデータストリーミングにより、ライブ取引や市場活動を監視できます。取引戦略の実装や、ライブ市場更新を処理するツールの作成にご利用ください。

スキルを見る
creating-opencode-plugins
メタ

このスキルは、開発者がコマンド、ファイル、LSP操作など25種類以上のイベントタイプにフックするOpenCodeプラグインを作成することを支援します。JavaScript/TypeScriptモジュール向けに、プラグイン構造、イベントAPI仕様、および実装パターンを提供します。カスタムイベント駆動ロジックでOpenCode AIアシスタントのライフサイクルをインターセプト、監視、または拡張する必要がある場合にご利用ください。

スキルを見る
sglang
メタ

SGLangは、高性能なLLMサービングフレームワークであり、RadixAttentionプレフィックスキャッシュを活用したJSON、正規表現、エージェントワークフロー向けの高速で構造化された生成を特長とします。特にプレフィックスが繰り返されるタスクにおいて、大幅に高速な推論を実現し、複雑な構造化出力やマルチターン対話に最適です。制約付きデコードが必要な場合や、広範なプレフィックス共有を伴うアプリケーションを構築する場合は、vLLMなどの代替案ではなくSGLangを選択してください。

スキルを見る