Design Resources for Developers
Use this skill to find practical design resources before building, redesigning, or polishing frontend interfaces. Prefer it when the task needs third-party resource discovery, asset sourcing, design-tool suggestions, UI-library comparison, or inspiration links.
Source
- Upstream repository:
https://github.com/bradtraversy/design-resources-for-developers - Integrated source commit:
6d9884e7260076e0eced4ac9f3be7665a91a9476 - Local source checkout:
%USERPROFILE%\.design-resources-for-developers\design-resources-for-developers
Workflow
- Start with
references/category-index.mdto choose the relevant category. - Use
scripts/search_design_resources.pyfor targeted lookup without loading the full README. - Load
references/catalog.mdonly when category-level detail is needed. - Load
references/source-readme.mdwhen the exact upstream wording or full list matters. - Check
references/contributing.mdbefore proposing additions back to the upstream list.
Search Helper
Run from this skill directory:
python scripts/search_design_resources.py --query "tailwind" --limit 10 --format md
python scripts/search_design_resources.py --category "React UI Libraries" --limit 20 --format md
python scripts/search_design_resources.py --query "color contrast" --format json
The helper searches resource names, descriptions, URLs, and categories in references/resources.json.
Use Rules
- Recommend resources by category and use case, not as a flat link dump.
- Prefer official, actively maintained, accessible, and production-friendly tools when the user is making implementation choices.
- Treat the mirrored catalogue as a starting point. If freshness matters, verify the resource live before relying on availability, pricing, license, or maintenance status.
- Do not paste the full catalogue into the answer. Cite only the relevant few resources and mention the category used.
- Keep licensing separate from availability: the upstream list focuses on free resources, but individual resources may have their own terms.