logo-generator
The logo-generator skill provides guidance on optimal logo placement, sizing, linking, and implementation for websites to maximize brand recall and user navigation. It advises placing logos in the top-left corner where users show 89 percent higher brand recall, ensures proper linking to the homepage, defines clear space requirements, and offers responsive sizing strategies across devices. Use this skill when users ask about logo positioning, alt text, favicon implementation, sizing guidelines, or branding placement on web pages.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/logo-generator && cp -r /tmp/logo-generator/skills/components/branding/logo ~/.claude/skills/logo-generatorSKILL.md
# Components: Logo Guides logo placement and implementation for brand recall and navigation. Logo placement affects user orientation and conversion. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand guidelines and visual identity. **Brand guidelines source**: Logo usage rules (clear space, minimum sizes, variants) come from **branding** (strategy), **brand-visual-generator** (visual specs), or media kit. Ensure alignment before implementation. Identify: 1. **Context**: Header, footer, standalone 2. **Platform**: Web, mobile, both 3. **Brand guidelines**: Size, clear space, variants (from brand-visual-generator or media kit) ## Placement Best Practices ### Optimal: Top-Left - **Brand recall**: Users are 89% more likely to remember logos in top-left vs. right - **Left-aligned**: ~39% brand recall vs. 21% for right-aligned - **Navigation anchor**: Users expect logo to link to homepage; left placement is intuitive - **Scan pattern**: Aligns with left-to-right reading flow ### Avoid - **Centered logos**: Users navigating home from centered logos are ~6x more likely to fail - **Right-aligned**: Violates conventions; harms brand recognition ### When Center May Work - Minimal headers with few elements - Brand-heavy landing pages where logo is focal point - Ensure logo still links to homepage and is clearly clickable ## Implementation ### Linking - **Always link to homepage** from logo - Use `<a href="/">` wrapping logo image - Expected behavior; don't break convention ### Image - Use appropriate format (SVG preferred for scalability) - Provide `alt` text: company/product name, not "logo" - Example: `alt="Acme Inc."` not `alt="Logo"` ### Size & Clear Space - **Minimum size**: Document in brand guide; prevent illegibility at small sizes (favicon, mobile header). - **Clear space**: Minimum space around logo; no text or graphics within this zone. Defined in brand-visual-generator. - **Responsive**: Ensure readability on mobile; test at 375px, 768px, 1024px. - **Variants**: Primary, secondary, monogram; light/dark backgrounds per brand guidelines. ## AI Product Logo Design (Optional) For AI/SaaS products, [Alignify AI Logo Guide](https://alignify.co/insights/ai-logo-design) offers industry-specific guidance. ### Design Trends *Examples are illustrative; no endorsement implied.* | Style | Use Case | Examples | |-------|----------|----------| | **Hexagon** | Technical platforms, enterprise AI | Common in AI logos (e.g. OpenAI) | | **Rotation/swirl** | Generative AI, creative tools | E.g. DeepMind, Stability AI | | **Minimalist robot** | Assistants, chatbots | E.g. Jasper, Replika | | **Emoji/symbol** | Consumer, friendly AI | E.g. Hugging Face, Zoom AI | ### Design Process 1. **Positioning**: B2B (professional, trustworthy) vs B2C (friendly, approachable) 2. **Core element**: Choose hexagon, rotation, robot, or emoji per product type 3. **Color**: Tech blue, blue-to-purple gradients, monochrome; consider dark mode 4. **Test sizes**: Favicon, mobile, header; ensure recognition at small sizes 5. **Trademark check**: Avoid conflicts with existing marks ### Avoid - Overly complex; modern AI logos favor minimalism - Too similar to competitors; balance industry recognition with uniqueness - Overly technical symbols for B2C; use friendlier designs - Ignoring mobile display; test at multiple sizes - Frequent rebranding; choose a long-term design ## SEO - Alt text supports accessibility and image SEO - Logo link contributes to internal linking (homepage) ## Accessibility | Requirement | Practice | |-------------|----------| | **Alt text** | Descriptive; company name | | **Contrast** | Logo visible against background | | **Focus** | Link receives visible focus state | | **Touch targets** | Adequate size on mobile (>=44x44px) | ## Output Format - **Placement** recommendation - **Implementation** notes (HTML, alt, link) - **Accessibility** checklist - **AI products** (optional): Design trend and archetype suggestions per positioning ## Related Skills - **branding**: Brand strategy; logo rules defined in brand guidelines - **navigation-menu-generator**: Logo typically sits in header with nav - **hero-generator**: Logo appears in hero context on landing pages - **media-kit-page-generator**: Logo assets, brand guidelines, usage rules - **favicon-generator**: Favicon derived from logo; consistent brand in browser tabs - **brand-visual-generator**: Typography, colors, spacing; logo clear space and variants
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.