design-stack-picker
Skill3 starsChanged 49 days agoMITView on GitHub
Use when building or restyling frontend UI and choosing building blocks — icon sets, fonts, component/block libraries, accessible primitives, imagery sources, color systems, motion, shadows, spacing, and image optimization. For landing pages, ecommerce, dashboards, web apps, emails, and single components.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- slilbudget/knowledge-delta-skillsword for word, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 1
- slilbudget/knowledge-delta-skills★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository17 other files it gives its agents.
- measurement-experimentation-opsSkill
- senior-buyer-opsSkill
- tracker-opsSkill
- deep-researchSkill
- knowledge-delta-skill-architectSkill
- web-scrapingSkill
- normcore-webSkill
- responsive-adapterSkill
- google-adsSkill
- google-feed-opsSkill
- google-grey-opsSkill
- meta-adsSkill
- meta-grey-opsSkill
- js-obfuscationSkill
- secure-codingSkill
- tiktok-adsSkill
- tiktok-opsSkill
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 19
Add a library only when there is no good local solution.
- Distinctive: line 37
No dependency for: a single icon when an icon system exists.
- Distinctive: line 39
Add one when it removes real implementation risk: complex accessible widgets, broad consistent icon coverage, image optimization at scale, …
- Distinctive: line 55
Never hand-draw generic SVG icons — use the icon set (supplied brand logos excepted).
- Distinctive: line 61
Verify in a browser from phone to wide desktop: no horizontal overflow, key images load at natural dimensions.
≈ “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
design-stack-picker
A selection layer, not a mandate to replace the project's design system.
Decision order
Audit first: framework and rendering model, existing icons/fonts/tokens/components/image pipeline/breakpoints, current dependencies, visual style. Then:
- Reuse the existing project system if it works.
- Extend it with the smallest compatible building block.
- Add a library only when there is no good local solution.
- Hand-craft only for brand assets, tiny static pieces, or where a dependency outweighs the implementation.
Defaults
Starting points, not requirements.
| Axis | Default |
| Icons | Iconify + Solar; Simple Icons for brand marks |
| Fonts | Unbounded display + Onest body via Fontsource |
| Components | Project components first; HyperUI/Preline for static sections; shadcn/Radix for React primitives |
| Color | Semantic CSS variables; one dominant brand color + one accent |
| Motion | CSS-first restrained reveal; Motion for React; GSAP only for complex timelines |
| Imagery | Real product/user/stock/CMS assets; AVIF/WebP where practical |
Dependency budget
No dependency for: a single icon when an icon system exists; one static section existing primitives can handle; a basic disclosure/dropdown in Astro or plain HTML where scoped JS is smaller and verifiable; a visual effect existing CSS covers; anything duplicating a current dependency.
Add one when it removes real implementation risk: complex accessible widgets, broad consistent icon coverage, image optimization at scale, multi-screen design systems.
Context routing
| Context | Bias |
| Astro/static | Local .astro components, scoped CSS, progressive JS, astro:assets; avoid React-only primitives unless already used |
| React/Next | Current UI layer first; shadcn/Radix for missing complex primitives |
| Admin/dashboard | Dense scannable forms/tables/filters, minimal decoration |
| Ecommerce | Real product photos, neutral placeholders, stable card dimensions with object-fit: contain; price/stock/spec/action hierarchy over decorative labels; reachable category nav, autocomplete, dismissible mobile filters; test long names, missing images, sale/stock states, uneven counts |
| Marketing | Stronger typography, imagery/video, section blocks, restrained motion |
| Prototype | Smallest working choice; no full design system unless it will continue |
Hard rules
- One family per axis: one icon set, one illustration style, one color system, one type pairing.
- Never hand-draw generic SVG icons — use the icon set (supplied brand logos excepted).
- Choose and load type intentionally; never ship default fonts on brand-facing UI.
- Tokens for colors, spacing, radii, shadows, type, and states — no scattered inline magic values.
- Accessible primitives for dialogs, comboboxes, tabs, menus, tooltips, switches — with real keyboard/focus behavior.
- Respect
prefers-reduced-motion, visible focus, AA contrast. - Optimize important images, set dimensions, eager-load only the LCP image.
- Verify in a browser from phone to wide desktop: no horizontal overflow, key images load at natural dimensions.
Where a hard rule conflicts with a mature existing convention, keep the convention and improve incrementally.
Resources
Load only what the task needs, never both by default.
resources.md— the catalog: libraries, fonts, icon sets, imagery, components, motion, color systems. §12 first for vague "make it look better" tasks, to fix concrete references before touching UI.patterns.md— implementation snippets: tokens, reset, icons, fonts, cards, image markup, motion, CSS.
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.

