list
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.
Works with
0
total installs
0
this week
304
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
304
stars
Installation Guide
How to use list on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
list
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches list from kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate list. Access via /list in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
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 |
| Table-like | Columns for metadata (date, status) |
| With thumbnail | Small image + text |
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
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
google-search-console
41kostja94/marketing-skills
grill-me
388mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
99pproenca/dot-skills
write-a-prd
91mattpocock/skills
Reviews
- DDev Jackson★★★★★Dec 28, 2024
list reduced setup friction for our internal harness; good balance of opinion and flexibility.
- AAmina Johnson★★★★★Dec 28, 2024
Useful defaults in list — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- PPratham Ware★★★★★Dec 24, 2024
We added list from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- RRen Robinson★★★★★Dec 24, 2024
Keeps context tight: list is the kind of skill you can hand to a new teammate without a long onboarding doc.
- SSakura Okafor★★★★★Dec 12, 2024
list has been reliable in day-to-day use. Documentation quality is above average for community skills.
- DDev Desai★★★★★Nov 19, 2024
Registry listing for list matched our evaluation — installs cleanly and behaves as described in the markdown.
- SSoo Chen★★★★★Nov 19, 2024
list has been reliable in day-to-day use. Documentation quality is above average for community skills.
- KKofi Patel★★★★★Nov 15, 2024
list is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- NNia Dixit★★★★★Nov 7, 2024
Solid pick for teams standardizing on skills: list is focused, and the summary matches what you get after install.
- KKofi Rao★★★★★Nov 3, 2024
Useful defaults in list — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 57
Discussion
Comments — not star reviews- No comments yet — start the thread.