/card
When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card
$ npx -y skills add kostja94/marketing-skills --skill card --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/card
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card
SKILL.md
card.SKILL.mdname: card
description: When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card design." For grids, use grid.
metadata:
version: 1.1.1
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
Read more
name: card description: When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card design." For grids, use grid. metadata: version: 1.1.1
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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill