list

$npx mdskill add kostja94/marketing-skills/list

Design and audit list layouts for content display.

  • Helps users design or optimize text-heavy list layouts like blog indexes.
  • Relies on layout guidelines and comparison with grid and card skills.
  • Decides based on content type, item count, and reading pattern.
  • Delivers structured recommendations with spacing, dividers, and metadata.

SKILL.md

.github/skills/listView on GitHub ↗
---
name: list
description: When the user wants to design, optimize, or audit list layouts for content display. Also use when the user mentions "list layout," "list design," "vertical list," "stacked list," "blog list," "article list," "documentation list," "search results layout," or "infinite scroll list." For blog index page, use blog-page-generator.
metadata:
  version: 1.1.1
---

# 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

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen 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.
affiliate-marketingWhen 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.
affiliate-page-generatorWhen 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.
ai-traffic-trackingWhen 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.
alternatives-page-generatorWhen 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.
api-page-generatorWhen 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.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen 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.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.