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 create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
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 create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
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 create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.