card

Solid

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.

Web & Frontend 562 stars 84 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
92
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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...

Details

Author
kostja94
Repository
kostja94/marketing-skills
Created
3 months ago
Last Updated
today
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

grid

When the user wants to design, optimize, or audit grid layouts for content display. Also use when the user mentions "grid layout," "grid design," "multi-column grid," "CSS grid," "responsive grid," "card grid," "product grid," or "feature grid." For cards layout, use card.

562 Updated today
kostja94
Web & Frontend Solid

carousel

When the user wants to design, optimize, or audit carousel/slider layouts for content display. Also use when the user mentions "carousel," "slider," "carousel layout," "testimonial carousel," "gallery carousel," "quote carousel," "image slider," or "carousel accessibility." For hero-area patterns, use hero-generator.

562 Updated today
kostja94
Web & Frontend Solid

masonry

When the user wants to design, optimize, or audit masonry (Pinterest-style) layouts for content display. Also use when the user mentions "masonry layout," "masonry grid," "Pinterest layout," "waterfall layout," "brick layout," "varying height grid," "gallery layout," or "masonry SEO." For crawl and scroll UX, use site-crawlability.

562 Updated today
kostja94
AI & Automation Listed

card-schema

Card schema reference — required/optional fields, status/stage/contribution/human_gate enums, canonical tags with predicates, DoD detection, relationship invariants, title naming convention. AUTO-INVOKE when other deck skills need schema context, or when user asks about field semantics, status lifecycle, DoD format, canonical tags, decision-gate body contract, or how to title a card. XP system metaphor — shared vocabulary makes the deck a contract, not a chat thread.

2 Updated today
zauberzeug
Web & Frontend Listed

frontend-codex

Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.

9 Updated yesterday
ControlNet