What it does
Selects one opinionated frontend library for component, motion, chart, performance, state or styling tasks. The skill turns decisions around library choice into an agent-readable workflow that can be executed and reviewed.
- Provides focused guidance for library choice work.
- Applies to design systems tasks while keeping design decisions traceable.
- Preserves the original source so teams can inspect, reuse and extend the workflow.
Best for / Not ideal for
Best for
- Projects that need a library choice method or delivery standard.
- Agent-assisted design systems tasks.
- Teams that want inspectable, adaptable design instructions.
Not ideal for
- Work unrelated to design systems.
- Scenarios expecting a tool to replace all human design review.
- Vague tasks with no audience, constraints or expected deliverable.
Installation or invocation
- Open the original repository or source page and confirm the latest instructions.
- Read SKILL.md, README or the source page for installation and license details.
- Add the skill to your agent environment as documented, or reference its instructions directly in the task.
- Invoke it with project context, constraints and the expected deliverable.
Use the “Pick UI Library” skill for [task] Context: [project and audience] Constraints: [brand, technology, time] Expected output: [reviewable deliverable]
FAQ
Does AuraUI host this skill?
No. AuraUI provides an editorial index and summary; the original author maintains the code, documentation and releases.
Can I use it with any agent?
Compatibility depends on the source format and your agent environment. Follow the original repository’s installation guidance first.
Can I use it commercially?
Check the license and terms at the original source. Inclusion in AuraUI does not grant additional rights.
Original source and editorial note
https://github.com/emilkowalski/skills/tree/main/skills/pick-ui-library
AuraUI added this skill on 2026.08.07. This introduction is an editorial summary; if anything differs, the original author’s documentation takes precedence.