List
Install when you are designing or auditing stacked list UIs for blogs, docs, or search results—not marketing landing hero sections.
Overview
list is an agent skill for the Build phase that designs and audits vertical stacked list layouts for text-heavy content indexes and search results.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill listWhat is this skill?
- When to use list versus grid versus card (text-heavy scan, density, F-pattern)
- List structure: items, title, metadata, excerpt, spacing and dividers
- Suited for blog indexes, documentation, search results, infinite scroll
- Points to grid and card skills for alternate layouts; blog index may use blog-page-generator
- Versioned marketing-skills component skill (1.1.1)
- list versus grid decision table
- five core list structure elements (items, title, metadata, excerpt, spacing)
Adoption & trust: 717 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a scannable index page but your layout reads like a mismatched grid or bloated cards.
Who is it for?
Blog indexes, documentation hubs, and search result pages where titles and metadata drive clicks.
Skip if: Product galleries, template marketplaces, or full blog index builds—use grid/card or blog-page-generator instead.
When should I use this skill?
When the user wants to design, optimize, or audit list layouts; mentions list layout, vertical list, blog list, documentation list, search results layout, or infinite scroll list.
What do I get? / Deliverables
You get a clear list structure, spacing rules, and list-versus-grid decision criteria aligned to F-pattern scanning.
- List layout specification
- List versus grid recommendation
- Per-item field checklist (title, metadata, excerpt)
Recommended Skills
Journey fit
List layout decisions happen while composing product and marketing surfaces in code or design specs during the build phase. Frontend implementation and information architecture for index and results pages is where list versus grid tradeoffs matter.
How it compares
Layout methodology for linear stacks—not a grid gallery skill or automated blog generator.
Common Questions / FAQ
Who is list for?
Solo builders and marketers shipping content-heavy SaaS or sites who want consistent list UX without redesigning from scratch.
When should I use list?
During Build frontend when designing blog lists, docs navigation, or search results; before Launch SEO when index crawl paths depend on clear title links.
Is list safe to install?
It is documentation-style guidance with no privileged tools listed—still review the Security Audits panel on this Prism page for the package source.
SKILL.md
READMESKILL.md - List
# 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