carousel
The carousel skill guides sequential content display design for limited-space layouts where users navigate through items one or few at a time via clicks or swipes. Use it for testimonials, quotes, logos, gallery highlights, and other rotating content that benefits from focused, space-efficient presentation rather than full-catalog visibility, ensuring accessibility through keyboard navigation, screen reader support, and performance optimization like lazy loading and content preservation in the DOM for SEO.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/carousel && cp -r /tmp/carousel/skills/components/layout/carousel ~/.claude/skills/carouselSKILL.md
# Components: Carousel Layout Guides carousel (slider) layout design for sequential content display. Carousels show one or few items at a time; users swipe or click to advance. Best when space is limited and multiple items need rotation—testimonials, quotes, logos, gallery highlights. **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. ## When to Use Carousel | Use carousel when | Use grid/list when | |-------------------|---------------------| | **Limited space** | Full catalog visible | | One focus at a time; rotation desired | Browse, compare many items | | Testimonials, quotes, logos, featured gallery | Products, templates, blog index | | Above fold; hero or section highlight | Full listing; discovery | See **grid** for equal-hierarchy display; **list** for text-heavy scan; **masonry** for varying-height gallery. ## Carousel vs Grid vs List vs Masonry | Layout | Structure | Best for | |--------|-----------|----------| | **Grid** | Equal rows and columns; all visible | Products, templates, features | | **List** | Single column; stacked | Blog index, docs, search results | | **Masonry** | Columns; varying heights | Pinterest-style gallery | | **Carousel** | Slides; one/few visible; swipe/click | Testimonials, logos, featured items | ## Best Practices ### Accessibility - **Keyboard navigation**: Arrow keys to move; Enter/Space to activate; focus visible - **User control**: Don't auto-advance too fast; allow pause; avoid auto-advance if `prefers-reduced-motion` is set - **Announcements**: Screen reader users need to know current slide and total (e.g., "Slide 2 of 5") - **Touch targets**: ≥44×44px for prev/next buttons on mobile ### Performance - **Lazy load**: Load off-screen slides on demand; avoid loading all images upfront - **Reserve space**: Reserve space for slides to avoid layout shift (CLS) ### SEO - **Content in DOM**: All carousel content must be in the initial HTML at page load. Google does not simulate clicks; content loaded via AJAX on slide change is not discoverable. Same as **tab-accordion**. - **Recommendation**: Server-render all slides in HTML; use CSS/JS only to show/hide. See **rendering-strategies**. ## Use Cases | Use case | Format | Page Skill | |----------|--------|------------| | **Testimonials** | Quote carousel; multiple testimonials | **testimonials-generator** | | **Showcase / Gallery** | Featured items; rotation | **showcase-page-generator** | | **Press logos** | "As Seen In" logo strip or quote carousel | **press-coverage-page-generator** | | **Community** | Banner carousel below hero | **community-forum** | ## Related Skills - **grid**: Grid for full catalog; when carousel is too restrictive - **list**: List for text-heavy scan - **masonry**: Masonry for varying-height gallery - **card**: Card structure within carousel slides - **testimonials-generator**: Testimonial carousel; testimonials as content - **showcase-page-generator**: Gallery format options (grid, masonry, carousel) - **tab-accordion**: Similar SEO requirement—content in DOM at load - **rendering-strategies**: SSR, SSG; content in initial HTML for crawlers
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.