list
The list layout skill guides design of linear, vertically stacked content displays optimized for text-heavy scanning. Use it when designing blog indexes, documentation, search results, or other dense content layouts where users navigate by title and metadata rather than visual discovery. Invoke it when users mention list design, vertical layouts, article indexes, or infinite scroll implementations.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/list && cp -r /tmp/list/skills/components/layout/list ~/.claude/skills/listSKILL.md
# Components: List Layout Guides list layout design for linear, stacked content display. Lists are compact, text-heavy; users scan by title or metadata. Used for blog indexes, documentation, search results, and dense content. **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 List | Use list when | Use grid when | |---------------|---------------| | Text-heavy; scan by title | Visual content; equal emphasis | | Many items; compact display | Fewer items; browsing | | Blog index, docs, search results | Products, templates, gallery | | F-pattern reading (top-left, left column) | Discovery, exploration | See **grid** for grid layout; **card** for card structure. ## List Structure | Element | Purpose | |---------|---------| | **Items** | Single column; stacked vertically | | **Per item** | Title, optional metadata (date, author), excerpt, link | | **Spacing** | Consistent gaps; dividers or alternating background | | **Density** | Compact (docs) vs relaxed (blog) | ## List Variants | Variant | Use | |---------|-----| | **Simple list** | Title + link; minimal (nav, TOC) | | **Rich list** | Title, excerpt, date, author | Blog index | | **Table-like** | Columns for metadata (date, status) | Docs, admin | | **With thumbnail** | Small image + text | Blog with thumbnails | ## Best Practices | Principle | Practice | |-----------|----------| | **Scannable** | Clear titles; consistent hierarchy | | **Compact** | Less vertical space than grid | | **Link area** | Full row or title clickable | | **Metadata** | Date, author, category; secondary styling | ## F-Pattern Users read top-left first, then scan left column. Place primary content (titles) left-aligned; metadata secondary. ## Infinite Scroll If using infinite scroll for list (e.g., blog index, search results): crawlers cannot access content loaded on scroll. Provide paginated component pages or use traditional pagination for SEO-critical content. See **site-crawlability** for search-friendly infinite scroll implementation. ## Responsive - **Mobile**: Single column; full-width items - **Touch targets**: ≥44×44px for touchable rows - **Truncation**: Long titles; ellipsis or wrap by design ## Related Skills - **site-crawlability**: Infinite scroll SEO; paginated component pages; search-friendly implementation - **grid**: Grid vs list; when to use each - **carousel**: Carousel for slides; when list is too long for space - **card**: Card in list (e.g., blog with thumbnail) - **toc-generator**: TOC as list; jump links - **blog-page-generator**: Blog index list - **article-page-generator**: Article list format - **docs-page-generator**: Documentation list
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.