card
# ClaudeWave: Card **What it does**: This skill guides the design and optimization of card layouts, self-contained containers that group related content for scannable, responsive display. It covers card anatomy (container, image, title, description, CTA), specific card types (product, template, tool, feature, gallery, integration, blog, resource), responsive grid strategies, and design principles like visual hierarchy and consistency. **When to use it**: Invoke this skill when a user needs to design, audit, or optimize card layouts, or explicitly mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card design."
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/card && cp -r /tmp/card/skills/components/layout/card ~/.claude/skills/cardSKILL.md
# 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
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," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
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," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 track AI traffic." For AI SEO strategy, use generative-engine-optimization.
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 analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-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 setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
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," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.