Card
- 764 installs
- 787 repo stars
- Updated June 9, 2026
- kostja94/marketing-skills
card is an agent skill at version 1.1.1 that designs, optimizes, and audits responsive card layouts for developers who need scannable product, feature, blog, and integration card grids on marketing pages.
About
card from kostja94/marketing-skills (version 1.1.1) guides design, optimization, and audit of responsive card layouts for scannable content display on marketing sites. Cards are self-contained containers grouping related content; the skill covers product cards, template cards, tool cards, feature cards, gallery cards, and integration cards used inside grids for blog posts, product listings, and feature showcases. Developers invoke card when users mention card layout, card component, card grid, product cards, or card design, and the skill pairs with the separate grid skill for full grid systems. The skill walks through layout hierarchy, spacing, responsive breakpoints, and accessibility considerations so card UIs stay consistent across pages. With 750 catalog installs, developers reach for card when building or refactoring marketing card components in React, HTML, or design-system docs—not when the task is full-page navigation, form design, or backend catalog APIs alone.
- Defines complete card anatomy including container, thumbnail, title, metadata, and CTA
- Provides card type matrix by use case (product, feature, gallery, integration, tool)
- Delivers responsive grid guidance and scannability principles
- Includes invocation protocol: introductory explanation on first use, direct output on repeat
- Supports audit and optimization of existing card implementations
Card by the numbers
- 764 all-time installs (skills.sh)
- +6 installs in the week ending Jul 25, 2026 (Skillselion tracking)
- Ranked #491 of 1,888 Design & UI/UX skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kostja94/marketing-skills --skill cardAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 764 |
|---|---|
| repo stars | ★ 787 |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 9, 2026 |
| Repository | kostja94/marketing-skills ↗ |
How do you design responsive marketing card grids?
Generate, optimize, or audit clean, responsive card layouts for product pages, feature showcases, blog grids, and marketing templates.
Who is it for?
Frontend developers and designers building scannable card grids for product listings, feature showcases, blog indexes, or integration directories on marketing sites.
Skip if: Teams laying out full-page dashboards, data tables, or navigation shells where cards are not the primary content container pattern.
When should I use this skill?
User mentions card layout, card component, card grid, product cards, feature cards, gallery cards, integration cards, or asks to audit marketing card UI.
What you get
Card layout recommendations, responsive grid structure, spacing and hierarchy fixes, and audit notes for product, feature, and blog card components.
- Card layout recommendations
- Responsive grid structure
- Card UI audit notes
By the numbers
- Skill version 1.1.1 in kostja94/marketing-skills metadata
- 750 catalog installs
- Covers 6 card use cases: product, template, tool, feature, gallery, integration
Files
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
Related skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.698k164k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.486k29.4k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst382k15.8k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k470
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.284k66.9k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.282k109kHow it compares
Pick card for individual card component design and audits; use the grid skill when the primary task is multi-column grid layout architecture.
FAQ
What card types does the card skill cover?
card at version 1.1.1 guides product cards, template cards, tool cards, feature cards, gallery cards, and integration cards—self-contained containers grouped in grids for blog posts, products, and showcases.
When should I use card versus the grid skill?
card focuses on individual card layout, hierarchy, and responsive behavior; kostja94/marketing-skills directs full grid systems to the separate grid skill when the task spans multi-column grid structure beyond single cards.
What triggers activate the card skill?
card activates on mentions of card layout, card component, card grid, product cards, template cards, feature cards, gallery cards, integration cards, or explicit card design audit requests.
Is Card safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.