30 Claude Prompts for Brand Guidelines

You are a brand design lead. <context> Designers, agencies, and non-designers keep placing the logo incorrectly, on the wrong backgrounds, or below a readable size. </context> <inputs> - Brand name: [BRAND_NAME] - Logo description: [LOGO_DESCRIPTION, e.g. wordmark plus icon lockup] - Minimum size in px: [MIN_SIZE_PX] - Available color variants: [COLOR_VARIANTS, e.g. full color, white, black] - One misuse example you've seen: [MISUSE_EXAMPLE] </inputs> <task> Write logo usage rules covering clear space, minimum size, acceptable backgrounds, and when to use each color variant, then list common mistakes including the misuse example supplied. </task> <constraints> - State clear space as a multiple of the logo's own height or icon width. - Cover at least 3 background scenarios (light, dark, photo). - The mistakes list must include the specific misuse example given, not a generic one. </constraints> <format> Return a live HTML artifact formatted as a one-page rules sheet with clear section headers and a highlighted "Common Mistakes" callout box. </format>

You are a brand designer. <context> The brand's colors are only documented as a handful of hex codes with no guidance on how much of each to use or where they pass accessibility checks. </context> <inputs> - Primary color hex: [PRIMARY_HEX] - Secondary color hex: [SECONDARY_HEX] - Accent color hex: [ACCENT_HEX] - Neutral or background hex: [NEUTRAL_HEX] - Preferred use case per color: [USE_CASES, e.g. primary for CTAs] </inputs> <task> Build a color usage guide listing each color's hex and RGB values, a recommended usage percentage across a typical layout, and a plain-language note on text contrast against white and black. </task> <constraints> - Usage percentages across all 4 colors must add up to 100. - Flag any color that would fail WCAG AA contrast for body text on white, with a suggested darker or lighter alternate hex. - Keep notes under 25 words each. </constraints> <format> Return a live HTML artifact showing each color as a labeled swatch with its hex, RGB, usage percentage, and contrast note beneath it. </format>

You are a brand designer. <context> Writers and designers use inconsistent font sizes and weights for headings across the website, decks, and one-pagers. </context> <inputs> - Heading font name: [HEADING_FONT] - Body font name: [BODY_FONT] - Fallback web-safe font: [FALLBACK_FONT] - Brand tone: [BRAND_TONE, e.g. modern, traditional] - Primary use cases: [USE_CASES, e.g. web, print, slides] </inputs> <task> Define a type hierarchy from H1 through H4 plus body text and captions, specifying font, weight, size, and line height for each level, with one example line of text set at that level. </task> <constraints> - Sizes must step down consistently from H1 to caption, no level can be larger than the level above it. - Include the fallback font explicitly for at least the body level. - Example text must be realistic for the stated use cases, not "sample heading here". </constraints> <format> Return a table with columns: Level, Font, Weight, Size, Line Height, Example Text. </format>

You are a brand creative director. <context> Stock photo choices and social image style vary by whoever is picking them that week, so the brand looks different from post to post. </context> <inputs> - Brand name: [BRAND_NAME] - Industry: [INDUSTRY] - 3 mood adjectives for photography: [MOOD_ADJECTIVES] - One example image style to avoid: [STYLE_TO_AVOID] - Primary use case: [USE_CASE, e.g. website, social, ads] </inputs> <task> Write imagery guidelines covering lighting, color grading, subject framing, and composition, ending with a do and don't list that explicitly rules out the style to avoid. </task> <constraints> - Tie every guideline back to at least one of the 3 mood adjectives. - Include specific technical notes: aspect ratios for the stated use case and a color grading direction (warm, cool, desaturated, etc). - Don't describe an actual photo, describe the rule that would produce it. </constraints> <format> Return a structured doc with sections: Mood, Do, Don't, Technical Notes. </format>

You are a brand design lead. <context> A partnership or sponsorship requires our logo to appear alongside a partner's logo, and there's no existing rule for how that should look. </context> <inputs> - Our brand name: [BRAND_NAME] - Partner brand name (example): [PARTNER_NAME] - Minimum spacing rule: [SPACING_RULE, e.g. 1x logo height] - Preferred lockup order: [LOCKUP_ORDER, e.g. ours first, alphabetical, equal size] - Approval contact: [APPROVAL_CONTACT] </inputs> <task> Define rules for how the two logos combine: spacing, relative sizing ratio, separator style (line, dot, or space), and a numbered approval checklist that must be completed before any co-branded asset ships. </task> <constraints> - Sizing ratio must guarantee neither logo appears dominant unless the lockup order explicitly says otherwise. - Approval checklist must include a named or role-based sign-off step, using the approval contact given. - State what to do when the partner has their own conflicting co-branding rules. </constraints> <format> Return a doc with a rules section followed by a numbered pre-launch approval checklist. </format>

You are a positioning strategist. <context> The team has a strong product but can't agree on a single sentence that explains why it exists and who it's for. </context> <inputs> - Brand name: [BRAND_NAME] - Category: [CATEGORY] - Target audience: [TARGET_AUDIENCE] - Key benefit: [KEY_BENEFIT] - Top competitor: [TOP_COMPETITOR] - Proof point (data or feature): [PROOF_POINT] </inputs> <task> Write a positioning statement using the structure "For [audience], [brand] is the [category] that [benefit], because [proof point]", then write 2 alternate phrasings of the same positioning. </task> <constraints> - The primary statement must fit in one sentence. - Each alternate must lead with a different element (audience, benefit, or proof) while keeping the same underlying claim. - Do not mention the competitor by name inside the statement itself. </constraints> <format> Return a doc with the primary statement bolded, followed by the 2 alternates, each with a one-line rationale for when to use it. </format>

You are a messaging strategist. <context> A founder or salesperson needs to explain the brand in wildly different amounts of time depending on the setting. </context> <inputs> - Brand name: [BRAND_NAME] - What we do in plain language: [WHAT_WE_DO] - Target audience: [TARGET_AUDIENCE] - Key differentiator: [DIFFERENTIATOR] - Setting: [SETTING, e.g. investor pitch, customer intro, conference booth] </inputs> <task> Write 3 pitch lengths, 15 seconds, 30 seconds, and 60 seconds, each written for the stated setting and each explicitly stating the differentiator, not just what the product does. </task> <constraints> - Estimate word count assuming a natural speaking pace of about 130 words per minute. - The 15-second version must still name the audience and the differentiator, not just the category. - No pitch may open with "We are a company that...". </constraints> <format> Return a table with columns: Length, Pitch Text, Word Count. </format>

You are a product marketer. <context> The same product is sold to multiple audience segments, but the sales and marketing teams are using one generic pitch for everyone. </context> <inputs> - Brand name: [BRAND_NAME] - 3 audience segments: [AUDIENCE_SEGMENTS] - Top pain point per segment: [PAIN_POINTS] - Core product benefit: [CORE_BENEFIT] - Proof point or stat: [PROOF_POINT] </inputs> <task> Build a matrix mapping each of the 3 audience segments to its specific pain point and a value proposition message that connects the core benefit to that pain point, backed by the proof point where relevant. </task> <constraints> - Each segment's value proposition wording must differ meaningfully, not just swap the segment name into the same sentence. - Use the proof point in at least 2 of the 3 rows. - Keep each value proposition to one sentence. </constraints> <format> Return a table with columns: Segment, Pain Point, Value Proposition, Supporting Proof. </format>

You are a brand copywriter. <context> The brand's current tagline feels stale and the team wants fresh options to test, grouped by style so they can pick a direction first. </context> <inputs> - Brand name: [BRAND_NAME] - Category: [CATEGORY] - Key benefit: [KEY_BENEFIT] - Desired feeling: [DESIRED_FEELING, e.g. trust, energy, calm] - 2 taglines we've used before: [PAST_TAGLINES] </inputs> <task> Generate 8 new tagline options grouped into 3 tone groups (direct, clever, aspirational), each with a one-line rationale, and note how each differs from the 2 past taglines supplied. </task> <constraints> - No tagline may exceed 6 words. - At least 2 options per tone group. - Do not reuse more than one word from either past tagline. </constraints> <format> Return a table with columns: Tagline, Tone Group, Rationale. </format>

You are a brand strategist. <context> Marketing, sales, and product keep writing about the brand from 3 different angles because there's no shared list of core messages. </context> <inputs> - Brand name: [BRAND_NAME] - Mission in one sentence: [MISSION_SENTENCE] - Target audience: [TARGET_AUDIENCE] - 3 core product benefits: [CORE_BENEFITS] - Top competitor's main message: [COMPETITOR_MESSAGE] </inputs> <task> Define 3 to 4 messaging pillars, each with a pillar name, a one-sentence description, and 2 supporting proof points, making sure at least one pillar clearly differs from the competitor's main message. </task> <constraints> - Pillar names must be short enough to use as section headers, under 5 words each. - Every core benefit supplied must map to at least one pillar. - Proof points must be concrete (a number, a feature, or a named outcome), not adjectives. </constraints> <format> Return a structured doc, one section per pillar with Name, Description, Proof Points. </format>

You are a brand strategist. <context> A team is starting a brand guidelines document from scratch and needs a complete structure before writing any section. </context> <inputs> - Brand name: [BRAND_NAME] - Industry: [INDUSTRY] - Audience for the document: [DOCUMENT_AUDIENCE, e.g. internal team, agencies] - Visual assets that already exist: [EXISTING_ASSETS, e.g. logo, colors, fonts] - Target document length: [LENGTH_TARGET, e.g. 10-15 pages] </inputs> <task> Build a full table of contents for a brand guidelines document sized to the target length, with a one-sentence summary of what each section will cover, ordering sections so existing assets are documented before assets that still need to be created. </task> <constraints> - Number of top-level sections must roughly match the target length (about 1 section per 1 to 2 pages). - Flag any section that depends on an asset not listed as existing. - Include a section for governance or approval process, not just visuals and voice. </constraints> <format> Return a numbered outline with section titles and one-line summaries. </format>

You are a brand strategist. <context> Most employees will never read the full guidelines document, they need a single page they can screenshot and keep open while writing. </context> <inputs> - Brand name: [BRAND_NAME] - Top 3 voice adjectives: [VOICE_ADJECTIVES] - Primary color hex codes: [PRIMARY_HEX_CODES] - Font names: [FONT_NAMES] - One example on-brand sentence: [ON_BRAND_SENTENCE] </inputs> <task> Condense the brand's voice, colors, and fonts into a single quick-reference page that anyone on the team can scan in under 30 seconds and immediately apply. </task> <constraints> - No more than 6 total sections on the page. - Every color must show its hex code visibly next to the swatch. - Include the example on-brand sentence as a live illustration, not just a rule. </constraints> <format> Return a live HTML artifact styled as a compact one-page reference card. </format>

You are a brand strategist. <context> The finished guidelines document needs to be presented live to a group instead of just shared as a PDF. </context> <inputs> - Brand name: [BRAND_NAME] - Audience for the deck: [DECK_AUDIENCE, e.g. new hires, agency, leadership] - Target number of slides: [SLIDE_COUNT] - Key sections to cover: [KEY_SECTIONS] </inputs> <task> Write slide-by-slide content for a brand guidelines presentation sized to the target slide count, giving each slide a title and 2 to 3 bullet points, covering every key section listed. </task> <constraints> - Open with a slide stating why the guidelines exist, not the logo itself. - Bullet points must be spoken-language phrases, not full paragraphs. - Close with a slide naming where to find the full document and who to ask questions. </constraints> <format> Return a table with columns: Slide #, Slide Title, Bullet Points. </format>

You are a brand manager. <context> An external agency or freelancer is about to start producing brand content and has never seen the internal guidelines. </context> <inputs> - Brand name: [BRAND_NAME] - Agency or vendor name: [VENDOR_NAME] - Scope of work they'll produce: [SCOPE_OF_WORK] - Required approvals before publishing: [APPROVAL_STEPS] - Key assets to share: [ASSETS_TO_SHARE] </inputs> <task> Write an onboarding document that briefs the vendor on brand voice, the core visual rules, and the exact approval process required before anything they produce goes live. </task> <constraints> - Approval process must be a numbered sequence with named responsible parties or roles. - Voice summary must be condensed to no more than 5 bullet points. - Explicitly state what the vendor should do if a rule isn't covered in this doc. </constraints> <format> Return a structured doc with sections: Overview, Voice Summary, Visual Rules Summary, Approval Process, Assets Provided. </format>

You are a brand manager. <context> Every new vendor asks the same handful of questions about logo files, color usage, and tone, and answering them one-off wastes time. </context> <inputs> - Brand name: [BRAND_NAME] - 5 questions vendors commonly ask: [COMMON_QUESTIONS] - Approval contact and turnaround time: [APPROVAL_CONTACT_AND_TURNAROUND] - Where to find brand assets: [ASSET_LOCATION] </inputs> <task> Write a Q&A document answering the 5 supplied questions plus 5 additional questions vendors typically ask about logo files, colors, and tone, for a total of 10 questions. </task> <constraints> - Every answer must be usable as-is without further editing, no "insert here" placeholders in the answers. - At least one answer must state the approval contact and turnaround time explicitly. - Group the 10 questions under 3 subheadings (Assets, Voice, Process). </constraints> <format> Return a Q&A doc, grouped under subheadings, one question and answer per entry. </format>

You are a brand manager. <context> The brand has grown across multiple channels faster than anyone has checked whether they still follow the guidelines. </context> <inputs> - Brand name: [BRAND_NAME] - Channels to audit: [CHANNELS, e.g. website, social profiles, email, sales decks] - Current brand guideline version: [GUIDELINE_VERSION] - Known problem areas: [KNOWN_PROBLEMS] </inputs> <task> Build a channel-by-channel checklist scoring each asset against voice, color, logo, and typography rules, with the known problem areas called out as specific checklist items. </task> <constraints> - Each channel must get at least 4 checklist items. - Every known problem area supplied must appear as its own checklist item. - Group items under their channel, not one flat list. </constraints> <format> Return a live HTML artifact with a checkbox-style checklist grouped by channel. </format>

You are a brand manager. <context> Different people on the team disagree about what counts as "off-brand", so violations get argued about instead of fixed quickly. </context> <inputs> - Brand name: [BRAND_NAME] - 3 examples of content that went off-brand: [OFF_BRAND_EXAMPLES] - Voice rules currently being violated: [VOICE_RULES] - Who should review flagged content: [REVIEWER_ROLE] </inputs> <task> Define clear criteria for what counts as off-brand across voice, visual, and messaging, then classify each of the 3 supplied examples against those criteria with a severity rating and a suggested fix. </task> <constraints> - Severity must use a 3-level scale (minor, moderate, major) with a one-line definition for each level. - Every example must get a concrete fix, not just a flag. - Name the reviewer role responsible for each severity level. </constraints> <format> Return a table with columns: Example, Rule Violated, Severity, Fix. </format>

You are a brand manager. <context> Social profiles were set up at different times by different people and no one has checked whether they still match the current brand. </context> <inputs> - Brand name: [BRAND_NAME] - Social platforms in use: [PLATFORMS] - Current bio text per platform: [CURRENT_BIOS] - Current profile image or cover description: [PROFILE_IMAGE_DESCRIPTION] - Target voice adjectives: [VOICE_ADJECTIVES] </inputs> <task> Audit each platform's bio and profile image against the target voice and visual rules, flag the specific issue with each, and rewrite the bio where it's off-brand. </task> <constraints> - Rewritten bios must respect each platform's typical character limit (for example, keep X/Twitter-style bios under 160 characters). - If a bio already matches the brand, state that explicitly instead of rewriting it unnecessarily. - Flag image issues separately from copy issues even when both exist on the same platform. </constraints> <format> Return a table with columns: Platform, Current Bio, Issue, Rewritten Bio. </format>

You are a brand manager. <context> The brand guidelines have changed and teams using the old version need to know exactly what's different and what they must update. </context> <inputs> - Brand name: [BRAND_NAME] - Previous version number and date: [PREVIOUS_VERSION_AND_DATE] - What changed: [WHAT_CHANGED, e.g. colors, voice, logo] - Reason for the change: [REASON_FOR_CHANGE] - New version number: [NEW_VERSION] </inputs> <task> Write a version changelog entry documenting exactly what changed and why, and a specific action-required list of what existing materials teams need to update because of this change. </task> <constraints> - Action-required items must be concrete tasks ("replace hex #1A2B3C with #2D3E4F on all templates"), not vague reminders. - State a deadline placeholder for when the old version stops being valid. - Keep the reason section to 2 sentences maximum. </constraints> <format> Return a structured changelog entry with fields: Version, Date, Changes, Reason, Action Required. </format>

You are a brand strategist. <context> The company has launched sub-brands or product lines and no one has defined which brand elements they share versus which they can set independently. </context> <inputs> - Parent brand name: [PARENT_BRAND] - Sub-brand or product line names: [SUB_BRAND_NAMES] - Elements that could be shared or unique: [ELEMENTS, e.g. logo, colors, voice, fonts] - Audience differences between sub-brands: [AUDIENCE_DIFFERENCES] </inputs> <task> Build a matrix showing, for each listed element, whether the parent brand and each sub-brand share it exactly or are allowed to differ, and explain the reasoning where they're allowed to differ. </task> <constraints> - At least the core logo mark and one primary color must remain shared across all sub-brands unless a stated reason justifies otherwise. - Reasoning for any "unique" designation must reference the audience differences supplied. - Flag any element left ambiguous as needing a decision, don't default it to either shared or unique silently. </constraints> <format> Return a table with columns: Element, Parent Brand, Sub-Brand 1, Sub-Brand 2, Shared or Unique, Reasoning. </format>

You are an internal comms lead. <context> An updated brand guidelines document is ready and the whole company needs to know it exists and what changed. </context> <inputs> - Brand name: [BRAND_NAME] - What's new or updated: [WHATS_NEW] - Link or location where the doc lives: [DOC_LOCATION] - Deadline for teams to adopt it: [ADOPTION_DEADLINE] </inputs> <task> Write an internal announcement email introducing the updated brand guidelines, summarizing what changed, and telling recipients exactly what they need to do before the deadline. </task> <constraints> - Subject line must be under 60 characters. - Body must state the deadline explicitly, not "soon" or "shortly". - Include one clear call to action (view the doc, ask questions in a named channel). </constraints> <format> Return an email with a Subject line and body. </format>

You are a brand manager. <context> The team read the guidelines once but retention is low, so a short quiz is being used to reinforce the key rules. </context> <inputs> - Brand name: [BRAND_NAME] - 5 key voice or visual rules to test: [KEY_RULES] - Audience: [AUDIENCE, e.g. new hires, whole company] - Format preference: [FORMAT, e.g. multiple choice] </inputs> <task> Write a 10-question multiple choice quiz testing knowledge of the brand's voice and visual rules, covering all 5 key rules supplied, with an answer key at the end. </task> <constraints> - Each question needs exactly 4 answer options with only one correct answer. - Wrong options must be plausible mistakes, not obviously silly. - Distribute the 5 key rules across at least 2 questions each. </constraints> <format> Return numbered quiz questions with 4 lettered options each, followed by a separate answer key. </format>

You are a brand operations manager. <context> Employees and agencies keep asking for logo files and templates through scattered Slack messages and emails, with no consistent information to process the request. </context> <inputs> - Brand name: [BRAND_NAME] - Types of assets people request: [ASSET_TYPES, e.g. logos, templates, photos] - Turnaround time: [TURNAROUND_TIME] - Approval steps required: [APPROVAL_STEPS] </inputs> <task> Build a structured intake form for anyone requesting brand assets, listing every field needed to process the request without back-and-forth, and note the turnaround time and approval steps on the form itself. </task> <constraints> - Include a required field capturing the intended use case for the asset. - Mark exactly which fields are required versus optional. - Include a field for deadline so operations can prioritize. </constraints> <format> Return a form field list with columns: Field Name, Field Type, Required (Y/N), Notes. </format>

You are a brand manager. <context> Leadership wants to spend a few minutes at the company all-hands introducing the updated brand, and needs speaker notes, not a full deck. </context> <inputs> - Brand name: [BRAND_NAME] - Reason for the brand update: [REASON_FOR_UPDATE] - Key changes to highlight: [KEY_CHANGES] - Time allotted: [TIME_ALLOTTED, e.g. 5 minutes] </inputs> <task> Write speaker talking points for presenting the brand update at an all-hands meeting, broken into timed segments that fit the allotted time, covering the reason for the change and the key changes. </task> <constraints> - Segments must add up to roughly the allotted time, assuming about 130 spoken words per minute. - Open with why the change matters to the business, not with visual details. - End with where people can find the full guidelines and who to contact with questions. </constraints> <format> Return a talking points doc broken into timed segments, each with a headline and 2 to 3 speaking points. </format>

You are a brand manager. <context> A new hire is joining a role that touches the brand and needs to get oriented fast without reading the entire guidelines document on day one. </context> <inputs> - Brand name: [BRAND_NAME] - Role the new hire is joining: [ROLE, e.g. content, design, sales] - Top 3 things they must know in week one: [WEEK_ONE_PRIORITIES] - Where to find full guidelines: [GUIDELINES_LOCATION] </inputs> <task> Write a short welcome guide orienting the new hire to the brand voice and visual basics that matter most for their specific role, prioritizing the 3 week-one items given. </task> <constraints> - Keep the total guide short enough to read in under 5 minutes. - Tailor examples to the stated role, a designer's week-one guide should look different from a salesperson's. - End with a clear pointer to the full guidelines location for anything not covered. </constraints> <format> Return a structured doc with sections: Welcome, What You Need to Know This Week, Where to Go for More. </format>