Card
Design or audit responsive card layouts for blogs, products, tools, and integrations so marketing pages stay scannable on solo-builder sites.
Overview
Card is an agent skill most often used in Build (also Launch, Grow) that guides card layout design for scannable, responsive content blocks on marketing and product pages.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill cardWhat is this skill?
- Card anatomy table: container, image, title, description/metadata, CTA
- Card types mapped to use cases: product, template, tool, feature, gallery, integration
- One card equals one topic principle for scannable grids
- Triggers cover card layout, card grid, product cards, template cards, tool cards, feature cards
- Version 1.1.1 metadata; defers full page grids to the grid skill
- 5 card anatomy elements in reference table
- skill metadata version 1.1.1
- 6+ card use-case types listed (product, template, tool, feature, gallery, integration)
Adoption & trust: 738 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your template or product page is a wall of text and uneven tiles that visitors cannot scan on mobile.
Who is it for?
Indie marketers and dev-builders polishing SaaS marketing sites, directories, or ecommerce listing components.
Skip if: Projects that only need page-level grid systems without card component rules—use the grid skill instead per this skill’s guidance.
When should I use this skill?
User mentions card layout, card component, card grid, product cards, template cards, tool cards, feature cards, gallery cards, integration cards, or card design.
What do I get? / Deliverables
You get a consistent card anatomy and type-specific guidance so each topic reads clearly with image, title, metadata, and CTA before you wire the wider grid.
- Card structure recommendations with anatomy and CTA pattern
- Audit notes for existing card grids by use-case type
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Card UI is implemented in the frontend layer; the same patterns recur on launch-facing pages and growth content hubs. Card anatomy, grids, and CTAs are component-level frontend work—pair with grid skill when layout spans the full page.
Where it fits
Spec thumbnail aspect ratios and CTA labels for a tools directory grid in React or static HTML.
Refactor launch page feature cards so each integration has one clear Connect action.
Audit blog post cards for consistent title and metadata before a content SEO pass.
How it compares
Component-level card design playbook, not a CSS framework install or automated Figma export.
Common Questions / FAQ
Who is card for?
Solo builders and small teams designing or auditing marketing UI—product cards, tool cards, integration cards—without a dedicated product designer.
When should I use card?
Use it in Build while implementing frontend card components, at Launch when tightening distribution landing pages, and in Grow when refreshing content or feature galleries.
Is card safe to install?
It is documentation-style guidance with no implied shell access; still review the Security Audits panel on this Prism page before adding any skill to your agent.
SKILL.md
READMESKILL.md - Card
# 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 - **showca