Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Build a persistent visual brand identity for image generation. Defines how the brand looks visually — aesthetic, lighting, composition, mood — and writes it to brand/creative-kit.md so /image-gen and other creative skills produce consistent on-brand visuals. Three modes: Extract (from website/URL), Build (interview), Reference (mood board/examples). Use when starting any project that needs images, when the user says "visual style", "brand aesthetic", "image style", "visual identity", "how should our images look", "build visual brand", "define our look", or when /image-gen outputs feel generic because no visual style exists yet.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Every brand has a voice. This skill gives it eyes.
Voice-profile.md defines how the brand sounds. Visual Brand Style defines how it looks — the lighting, the composition, the mood that makes someone see an image and know it's yours before reading a word.
brand/creative-kit.md if it exists. Check for a ## Visual Brand Style section.
creative-kit.md doesn't exist: create it first with mktg init, then proceed.brand/voice-profile.md if it exists — personality informs visual tone (e.g., playful voice = warm/bright visuals, authoritative = clean/precise).brand/positioning.md if it exists — angles inform visual metaphors (e.g., "the simple alternative" = minimalist aesthetic).Use AskUserQuestion:
"How do you want to define your visual brand style?"
The user provides a URL or set of URLs (website, landing page, social profiles).
Fallback: If WebFetch is unavailable, switch to Build mode and tell the user why.
Interview the user. Ask one question at a time via AskUserQuestion.
Question 1: Aesthetic anchor "Pick the closest match to how your brand should look visually:"
Question 2: Lighting and mood "What lighting feels right for your brand's images?"
Question 3: Composition "How should images be composed?"
Question 4: What to avoid "What should your images NEVER look like?" (Free text — the user's avoidances are often more revealing than their preferences)
Question 5: Reference "Name a brand, website, or aesthetic that captures what you're going for — even if it's in a completely different industry."
Optional Question 6: Existing assets "Do you have any images that already feel on-brand? Describe them or share URLs."
Synthesize answers into the Visual Brand Style format.
The user provides mood boards, image URLs, or descriptions of their ideal visual style.
Write the ## Visual Brand Style section into brand/creative-kit.md. Preserve all existing sections (Brand Colors, Typography, Visual Style). Only add/update the Visual Brand Style section.
## Visual Brand Style
- **Primary Aesthetic:** [derived aesthetic, e.g., "warm tech minimalism with editorial photography"]
- **Lighting:** [specific lighting direction, e.g., "soft diffused with rim lighting accents, warm color temperature"]
- **Backgrounds:** [background treatment, e.g., "dark slate (#0F172A) with warm accent gradients"]
- **Composition:** [layout approach, e.g., "single focal point, generous negative space for text overlay"]
- **Mood:** [emotional tone, e.g., "calm empowerment — powerful but approachable, like a quiet expert"]
- **Avoid:** [explicit exclusions, e.g., "generic stock photos, cold blue tech grids, floating 3D cubes, busy compositions"]
- **Reference Prompts:**
1. [A proven prompt that captures the brand look — ready to paste into image gen]
2. [A second prompt showing a different use case in the same style]
3. [Optional third prompt for edge cases]
Reference Prompts are critical. These are the style anchors that /image-gen uses when generating on-brand images. They should be complete, narrative prompts (not keywords) that produce images distinctly this brand.
When ## Visual Brand Style already exists:
| Level | Context | Output quality |
|---|---|---|
| L0 | No brand files | Generic but functional — asks user directly, writes style from scratch |
| L1 | voice-profile.md exists | Personality-aligned — playful voice gets warm visuals |
| L2 | + creative-kit.md colors/typography | Color-constrained — prompts incorporate brand palette |
| L3 | + positioning.md | Full alignment — visual metaphors match positioning angles |
| Anti-pattern | Why it fails | Instead |
|---|---|---|
| Locking into one rigid style | Brands need versatility — a blog header and an error page shouldn't look identical | Define the core aesthetic but include "also works for: [alternative moods]" in reference prompts |
| Ignoring existing creative-kit.md sections | Overwriting colors/typography the user already defined breaks trust and loses work | Read and preserve existing sections, only add/update Visual Brand Style |
| Generic descriptions like "modern and clean" | Every brand says this — it gives image-gen nothing to work with | Be specific: "warm rim lighting on dark backgrounds, single subject, f/2.0 bokeh" |
| Skipping the Avoid list | What to avoid is often more distinctive than what to include — it prevents the generic | Always ask what the brand should NEVER look like |
| Writing keyword prompts instead of narrative | Image gen models produce better results from flowing descriptions than comma-separated terms | Reference prompts should read like a scene description, not a tag list |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add a new expert to the Remotion experts page
日本語の概要は準備中です。原文の説明を表示しています。
Add a new sound effect to @remotion/sfx
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a secure email inbox for any AI agent — configuring inbound email via Resend, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks. Also use when someone mentions 'agent email', 'bot inbox', 'receive emails for agent', 'agent webhook', 'email security for AI', 'prompt injection via email', 'inbound email for bot', or wants their AI agent to receive and respond to emails securely.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, measures, and improves an Answer Engine Optimization program across ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, and Copilot. Use for AEO, GEO, LLMO, AI search visibility, AI citations, brand mentions, answer-engine monitoring, llms.txt, AI crawler audits, or questions like 'what does AI say about us?' and 'why are competitors cited instead of us?'. Produces a durable evidence report and prioritized gameplan, not a one-shot content checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Apple App Store screenshot pages as a Next.js app with html-to-image export at required resolutions. Screenshots are advertisements, not documentation — every screenshot sells one idea. Use when building App Store screenshots, generating exportable marketing screenshots for iOS apps, or creating programmatic screenshot generators. Triggers on 'app store screenshots', 'App Store', 'screenshot generator', 'iOS screenshots', 'marketing screenshots', 'phone mockup', 'ASO screenshots', 'app store assets', 'app listing', 'app store page', or 'app preview images'. Also use when someone is about to submit an app and needs store assets, or when they say 'make my app store page look good'. Includes iPhone and iPad mockup components with pre-measured dimensions.
日本語の概要は準備中です。原文の説明を表示しています。
Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.
日本語の概要は準備中です。原文の説明を表示しています。