sidebar-generator
The sidebar-generator skill guides strategic sidebar design for content sites like blogs and documentation, offering placement recommendations (left for navigation, right for secondary content), widget prioritization, and mobile responsiveness strategies. Use it when optimizing sidebar layout, deciding what content to include, or troubleshooting conversion performance, particularly when data suggests sidebar CTAs underperform compared to in-content or sticky alternatives.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/sidebar-generator && cp -r /tmp/sidebar-generator/skills/components/navigation/sidebar ~/.claude/skills/sidebar-generatorSKILL.md
# Components: Sidebar Guides sidebar design for content sites (blogs, docs). ~80% of users focus on the left; sidebars influence flow but can hurt conversion if overused. Posts without sidebars show 3.1x higher conversion; bottom-right sticky CTAs outperform sidebars (5.62% vs 0.58% CTR). **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 content structure and conversion goals. Identify: 1. **Content type**: Blog, docs, e-commerce 2. **Primary goal**: Navigation, CTA, related content 3. **Mobile**: Collapse to hamburger or hide on small screens ## Best Practices ### Placement - **Left sidebar**: Prime for nav; 80% of users focus left - **Right sidebar**: Secondary content, ads, related posts - **Static vs sticky**: Static for content-focused; sticky for persistent CTA (subscription, cart) ### Conversion Reality | Approach | Typical result | |----------|----------------| | **Sidebar CTA** | <1% opt-in for blog sidebars | | **In-content CTA** | 3x+ higher conversion | | **Bottom-right sticky** | 5.62% CTR vs 0.58% sidebar | | **No sidebar** | 3.1x higher conversion vs with sidebar | **Recommendation**: Prefer in-content CTAs or bottom-right sticky over sidebar CTAs. Use sidebar for nav and discovery, not primary conversion. ### Widget Guidelines - **One high-value CTA** max; avoid clutter - **Social proof**: Testimonials, logos - **Popular/related posts**: Discovery, internal linking - **Avoid**: Too many ads, affiliate links; reduces trust and speed ### Mobile - **Collapse**: Hamburger or off-canvas drawer - **57%+ mobile traffic**: Responsive design non-negotiable - **Reduce clutter**: Hide or simplify sidebar on small screens ## Output Format - **Placement** (left/right, static/sticky) - **Widget** list (nav, CTA, related, social proof) - **Mobile** behavior - **Conversion** note (in-content vs sidebar CTA) ## Related Skills - **toc-generator**: TOC often in sidebar for long content - **cta-generator**: Sidebar CTA (use sparingly) - **newsletter-signup-generator**: Sidebar signup; consider in-content instead - **internal-links**: Related posts in sidebar
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.