skillboardUpdated every 6 hours
skillboardWhen 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.
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.
| 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.
| 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 |
repeat(auto-fill, minmax()) or Flexbox; columns adapt to viewport| 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 |
| 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 |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/card · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/card"
cp -r "skills/components/layout/card" ".claude/skills/card"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.