kostja94/card
skills/components/layout/card/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add kostja94/marketing-skills cardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 6:31 PM96.0s1 file scanned
SKILL.md
- name:
- card
- description:
- 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.
- version:
- 1.1.1
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
kostja94/xml-sitemap
testing
VerifiedTrustedCommunity
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
588SKILL.mdUpdated Apr 24, 2026
kostja94/robots-txt
development
VerifiedTrustedCommunity
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
588SKILL.mdUpdated Apr 24, 2026
kostja94/programmatic-seo
testing
VerifiedTrustedCommunity
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
588SKILL.mdUpdated Apr 24, 2026
kostja94/twitter-cards
data-ai
VerifiedTrustedCommunity
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
571SKILL.mdUpdated Apr 24, 2026