Design
Skill yigityildiz0/universal-ai-skill-library/skills/common/design
Route broad or mixed visual-design requests into a coherent workflow spanning brand, design systems, UI/UX, interface styling, banners, presentations, logos, icons, and campaign assets. Use when a request crosses multiple design disciplines or the correct specialist skill is unclear; prefer the specialist skill directly for narrow tasks.From its SKILL.md
npx -y skills add yigityildiz0/universal-ai-skill-library --skill designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, 379 tokens by cl100k_base, as published. Nobody here has run it
Design Router
Coordinate the design family without duplicating specialist instructions.
Route by deliverable
| Need | Primary skill |
|---|---|
| Brand strategy, voice, identity governance | brand |
| Tokens, components, themes, state architecture | design-system |
| Product direction, UX evidence, stack guidance | ui-ux-pro-max |
| Tailwind, component styling, responsive implementation | ui-styling |
| Campaign banner, cover, ad, hero image | banner-design |
| Pitch deck or HTML presentation | slides |
For logos, icons, illustration, or photography, use the active host's native design or image-generation capability and the brand/design-system constraints. Do not require a fixed provider or model.
Mixed-deliverable workflow
- Define the shared brief: audience, objective, message, brand, platforms, required assets, deadlines, and acceptance criteria.
- Establish dependencies. Brand decisions precede token and asset decisions; tokens precede UI and presentation implementation.
- Invoke only the specialist skills required for the deliverables.
- Keep one owner for shared tokens, copy, logos, and source assets.
- Reconcile specialist outputs into one visual language.
- Validate consistency, accessibility, responsiveness, production dimensions, and export completeness.
Deliverable map
Before production, list each artifact with:
- owner or specialist workflow;
- source inputs;
- dimensions or platform;
- file format;
- dependencies;
- validation method;
- approval status.
Guardrails
- Do not activate every design skill for a narrow request.
- Do not let independent workstreams invent different brand tokens.
- Do not mix unrelated visual directions to appear more creative.
- Do not assume an image or browser tool is available; use the host's exposed capabilities and provide a fallback specification.
- Do not include provider/model names unless selected by the user.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.