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.
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 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.
| 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) |
| 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 |
| 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 |
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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/list · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/list"
cp -r "skills/components/layout/list" ".claude/skills/list"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.