ux-cards

Design and critique UI cards with hierarchy, container styles, and restrained shadows.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-cards-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-cards
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/ux/components/cards
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-cards-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Card UIs often fail through card stuffing (multiple topics crammed into one container), shadow soup (shadows on the card, its image, and its buttons), and cards-for-everything (card grids where users need ranked, comparable results). This Skill applies practitioner judgment so cards stay one-topic, scannable, and appropriate to the browsing context. ## Core Features & Use Cases - Context gating: Determines whether cards are even the right pattern by distinguishing browsing from searching, content type (text, rich media, user cards), and action count before designing. - Always-apply core rules: Enforces one topic per card, internal visual hierarchy, progressive disclosure with truncated teasers, one shadow maximum, and consistent padding. - Context-dependent decisions: Surfaces trade-offs for elevated vs. outlined vs. flat containers, full-card clickability, media usage, and card grids vs. lists/tables. - Use Case: When asked to design a product listing grid, the Skill checks whether users browse or search, recommends rich media cards with one clear action, then hands off to heuristics, accessibility, aesthetics, and microcopy audit skills for validation. ## Quick Start Ask the assistant to design or review a card layout for your content, such as a product grid or user profile cards, and it will apply these card design rules.

Frequently Asked Questions about ux-cards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a good UI card layout?▼

Keep one topic per card, establish a clear internal hierarchy with title over preview, use a short truncated teaser instead of full content, and limit the design to one shadow. Differentiate primary from secondary actions and place overflow menus in the top-right corner.

When should I use cards vs lists or tables?▼

Use cards for browsing heterogeneous, visual content like feeds, galleries, and dashboards where every item carries equal rank. Use lists or tables for ranked search results, spec-by-spec comparison, or when users hunt for a specific known item.

Should a card be elevated, outlined, or flat?▼

Elevated cards with a single soft shadow suit clickable cards needing affordance. Outlined cards group content quietly without depth. Flat cards need a distinct background color plus a hover cue, otherwise users miss them entirely.

Can I make the entire card clickable?▼

Make the whole card clickable when it has a single primary action, with a pointer cursor and hover effect. Avoid full-card clickability when multiple competing actions exist inside, since nested click targets create interaction traps.

Why does text over card images fail accessibility checks?▼

Text placed directly over busy images often falls below the 4.5:1 contrast ratio required for readability. Apply a translucent dark overlay behind the text to restore contrast, and avoid shadowing media inside an already-elevated card.