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.
Use list whenUse grid whenText-heavy; scan by titleVisual content; equal emphasisMany items; compact displayFewer items; browsingBlog index, docs, search resultsProducts, templates, galleryF-pattern reading (top-left, left column)Discovery, exploration
See grid for grid layout; card for card structure.
ElementPurposeItemsSingle column; stacked verticallyPer itemTitle, optional metadata (date, author), excerpt, linkSpacingConsistent gaps; dividers or alternating backgroundDensityCompact (docs) vs relaxed (blog)
VariantUseSimple listTitle + link; minimal (nav, TOC)Rich listTitle, excerpt, date, authorTable-likeColumns for metadata (date, status)With thumbnailSmall image + text
PrinciplePracticeScannableClear titles; consistent hierarchyCompactLess vertical space than gridLink areaFull row or title clickableMetadataDate, author, category; secondary styling
Users read top-left first, then scan left column. Place primary content (titles) left-aligned; metadata secondary.
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.