card▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides card layout design for scannable, responsive content display. Cards are self-contained containers that group related content; used in grids for blog posts, products, templates, tools, features, galleries, and integrations.
Components: Card Layout
Guides card layout design for scannable, responsive content display. Cards are self-contained containers that group related content; used in grids for blog posts, products, templates, tools, features, galleries, and integrations.
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.
Card Anatomy
| Element | Purpose |
|---|---|
| Container | Border, background, shadow; consistent padding |
| Image / Thumbnail | Visual anchor; consistent aspect ratio (1:1, 4:3 common) |
| Title | Clear; keyword-rich where relevant |
| Description / Metadata | Supporting text; date, author, category |
| CTA | Action button or link; "View," "Use," "Connect," etc. |
Principle: One card = one topic. Keep each card focused for scannability.
Card Types by Use Case
| Type | Typical Elements | Page Skill |
|---|---|---|
| Product card | Image, name, price, CTA (Add to cart, View) | products-page-generator |
| Template card | Thumbnail, name, short description, "Use" or "Preview" CTA | template-page-generator |
| Tool card | Name, one-line benefit, CTA to tool page | tools-page-generator |
| Feature card | Name, benefit, optional screenshot | features-page-generator |
| Gallery / Showcase item | Thumbnail, title, creator, link | showcase-page-generator |
| Integration card | Logo, name, short description, "Connect" or "Install" | integrations-page-generator |
| Blog / Article card | Cover image, title, excerpt, date, author | blog-page-generator, article-page-generator |
| Resource card | Thumbnail, title, format (guide, webinar), CTA | resources-page-generator |
Layout & Responsiveness
- Grid: CSS Grid
repeat(auto-fill, minmax())or Flexbox; columns adapt to viewport - Mobile: Single column on small screens; 2–4 columns on desktop
- Consistency: Same padding, spacing, and aspect ratios across cards
- Hover: Subtle elevation (shadow, translate-y); avoid scale that causes layout shift (CLS)
Design Principles
| Principle | Practice |
|---|---|
| Visual hierarchy | Title > description > CTA; clear flow |
| Scannability | Minimal text; benefit-led copy |
| Consistency | Same structure across all cards in a grid |
| Action clarity | One primary CTA per card; avoid choice overload |
SEO & Schema
- Cards themselves: No specific schema; layout is UI
- Content in cards: Use appropriate schema for the page (Product, Article, ItemList, etc.); see schema-markup
- Images: Alt text on thumbnails; see image-optimization
- Links: Descriptive anchor text; internal linking; see internal-links
Grid vs List vs Masonry vs Carousel
| Layout | Best for | Skill |
|---|---|---|
| Grid | Visual content (products, templates, gallery); equal emphasis | grid |
| List | Text-heavy (blog index, docs); compact; scan by title | list |
| Masonry | Varying heights; image gallery, portfolio | masonry |
| Carousel | Limited space; testimonials, logos, featured rotation | carousel |
Related Skills
- products-page-generator: Product cards, grid layout, category pages
- template-page-generator: Template cards, gallery structure
- tools-page-generator: Tool cards, toolkit hub
- features-page-generator: Feature grid/list
- showcase-page-generator: Gallery grid, per-item format
- integrations-page-generator: Catalog grid, integration cards
- category-page-generator: Product grid, consistent layout
- grid: Grid layout for card display; when to use grid
- list: List layout; cards in list format
- masonry: Masonry for varying-height cards (gallery)
- carousel: Carousel for card slides (testimonials, featured)
- hero-generator: Hero vs card—hero is single above-fold; cards are repeated units
- brand-visual-generator: Typography, spacing, visual consistency
- image-optimization: Card thumbnail optimization, alt text, LCP
How to use card 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 development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add card
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches card from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate card. Access the skill through slash commands (e.g., /card) or your agent's skill management interface.
Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
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
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share 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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★67 reviews- ★★★★★Charlotte Srinivasan· Dec 28, 2024
card reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Aditi Mensah· Dec 24, 2024
I recommend card for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Dhruvi Jain· Dec 16, 2024
Solid pick for teams standardizing on skills: card is focused, and the summary matches what you get after install.
- ★★★★★Charlotte Rao· Dec 16, 2024
Registry listing for card matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Pratham Ware· Dec 12, 2024
Keeps context tight: card is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Layla Liu· Dec 8, 2024
card reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Nikhil Mehta· Nov 27, 2024
I recommend card for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Henry Li· Nov 19, 2024
I recommend card for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sakura Sanchez· Nov 15, 2024
card reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Oshnikdeep· Nov 7, 2024
We added card from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 67