Individual skill
ux-cards
Design or critique UI cards — one-topic, scannable cards with clear hierarchy, the right container style (elevated, outlined, flat), and restrained shadows. Trigger when the user asks to design or review cards, card layouts, card grids, content tiles, user/profile cards, or a browse view built from cards.
ux/components/cards/SKILL.md
Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 40
- Repository last updated
- Jul 2, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-skills Repository topic
- claude-skills Repository topic
- design-skills Repository topic
- figma-skill Repository topic
- pm-skills Repository topic
- ux-skill Repository topic
- design Derived category
- writing Derived category
- devops Derived category
- design-interface Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,706 bytes
Read excerpt
# Cards Skill
## How this skill behaves (read first)
This is a **generative** skill. The default failure modes: **card stuffing** (multiple topics, long text, every detail crammed into one card), **shadow soup** (shadows on the card *and* its image *and* its buttons), and **cards-for-everything** (card grids where users need ranked, comparable results). A card is *one digestible topic in one container, inviting exploration* — and card layouts fit browsing, not searching. This skill gates:
1. **Establish what's being carded and how users consume it** — browsing vs. searching decides whether cards are even right.
2. **Apply the always-true core** — one topic per card, internal hierarchy, progressive disclosure, restraint.
3. **Surface the container-style and interaction decisions** (elevated/outlined/flat, full-card click, media) with trade-offs.
Then it **hands off to `ux-heuristics-audit`, `ux-accessibility-audit`, `ux-aesthetics-audit`, and `ux-microcopy-audit`** for validation.
---
