product-ui-craft
Skill1 starsChanged 3 months agoMITView on GitHub
Raise product UI craft — spacing, hierarchy, density, radii, states, and restrained motion so chrome feels designed. Use only when polishing already structured UI ("works but feels off"), not as the default for any UI task. Prefer product-design when multi-step product UX/craft is unclear (it routes here). Prefer frontend-design for full FE feature implementation pipelines. Not for brand invention, marketing landings, design-system token definition (design-system), mobile sticky/sheet systems (mobile-product-ux), or ship/e2e proof (quality-check / browser-verify).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- BarganConstantin/ccdecktheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- BarganConstantin/ccdeck★ 33same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- data-apache-lakehouseSkill
- data-apiSkill
- dataSkill
- data-duckdbSkill
- data-identity-resolutionSkill
- data-pipeline-operationsSkill
- data-pokemon-tcg-foundationsSkill
- data-product-evalSkill
- data-reelsSkill
- data-semantic-qualitySkill
- data-table-lifecycleSkill
- html-designSkill
- ebay-listingSkill
- flutter-pro-ux-reviewSkill
- flutterSkill
- browser-testing-with-devtoolsSkill
- browser-verifySkill
- design-systemSkill
- frontend-designSkill
- mobile-app-echarts-visualSkill
- mobile-blog-chart-visualSkill
- mobile-chart-visualSkill
- mobile-product-uxSkill
- mockup-implementSkill
- product-designSkill
- prototypeSkill
- react-performanceSkill
- ui-exploreSkill
- visual-verifySkill
- web-qualitySkill
- high-retention-insight-reels-instagramSkill
- instagramSkill
- instagram-virality-insightsSkill
- marketing-cashvertisingSkill
- marketing-contagiousSkill
- marketing-going-viralSkill
- marketingSkill
- marketing-offersSkill
- marketing-storybrandSkill
- quality-checkSkill
- elements-of-styleSkill
- style-clarity-graceSkill
- writer-styleSkill
- writing-docsSkill
- writing-proseSkill
- writingSkill
- writing-technicalSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
After design-system constraints are clear
- Distinctive: line 49
Prefer a single scale (4/8 or project tokens)
- Distinctive: line 63
Prefer progressive disclosure over walls of equal-weight controls
- Distinctive: line 84
Prefer one orchestrated moment over many micro-wiggles
- Distinctive: line 91
Use as self-instructions when iterating:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product UI craft
Job: Turn working UI into refined product UI without changing brand identity.
Sources (attribution)
- Product-mode craft ideas aligned with community skills such as
Impeccable (Paul Bakaus) — especially separating
product density from brand/marketing maximalism, and directional
polish passes (
quieter/boldermental model). - Micro-detail checklists in the spirit of Make Interfaces Feel Better (jakub.kr / UI polish principles): spacing, type, alignment, hierarchy, radii, subtle motion.
- Classic product design craft (scanability, grouping, consistent rhythm) — applied as agent checklists, not a redesign brief.
This skill is original synthesis for agents; it is not a vendor dump of those repos.
When to load
- “Looks fine but cheap / uneven / sparse / noisy”
- Chat shells, toolbars, filter bars, tables, empty states
- After design-system constraints are clear
Craft pass (run in order)
1. Hierarchy
- One primary action per region
- Type steps: page title → section → body → meta (mono for numbers if system says so)
- Don’t bold everything; don’t mute the primary metric
2. Spacing rhythm
- Prefer a single scale (4/8 or project tokens)
- Related items: tighter; unrelated groups: looser
- Kill accidental 1-off gaps that break the grid
3. Alignment
- Columns share edges; icons and labels share baselines
- Trailing numbers/tabular figures when comparing prices
- Sticky headers align with scroll body, not “almost”
4. Density
- Product data surfaces: prefer information density over marketing whitespace
- Collapse chrome before shrinking type below readable
- Prefer progressive disclosure over walls of equal-weight controls
5. Surfaces & radii
- Consistent elevation language (flat panels vs glossy controls if defined)
- One radius family; don’t mix pill + sharp + random 10px
- Borders: prefer token borders over heavy shadows for data UI
6. States
For each interactive/async region:
| State | Must have |
| Loading | Skeleton/spinner + aria-busy on container |
| Empty | What & next action |
| Error | Recoverable message + retry if applicable |
| Success | Stable layout (no jump) |
7. Motion
- Prefer one orchestrated moment over many micro-wiggles
- 150–300ms transitions for UI chrome
- Honor
prefers-reduced-motion - Don’t animate layout of dense tables unless essential
8. Directional polish (optional pass names)
Use as self-instructions when iterating:
| Pass | Do |
| Quieter | Reduce borders, shadows, competing accents |
| Bolder | Strengthen primary CTA/metric only |
| Tighter | Reduce vertical waste in lists/toolbars |
| Clearer | Labels, contrast, grouping |
Anti-patterns
- “Polish” that changes brand fonts/colors
- Decorating every card with gradients and glow
- Equal visual weight on 8 actions
- Hover-only affordances on mobile-critical controls
Hand off
| Need | Next skill |
| Tokens/components wrong | design-system |
| Phone sticky/gestures | mobile-product-ux |
| A11y/focus | web-quality |
| Prove pixels | browser-verify |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

