- Home
- Skills
- Frontend & Web Apps
- UI Library Router
Works with the AI Agents you already use
UI Library Router
Reuse before generation: route frontend component choices through your design system, installed primitives and approved sources before considering external libraries or custom code, with a read-only handoff.
$19
UI Library Router
Example session with this skill installed
We need an accessible date-range picker that fits our design tokens. Build or buy? Read the project requirements, existing design system, installed dependencies and configured registries first. Compare plausible sources for range behavior, keyboard and screen-reader requirements, responsive behavior, dependency impact, provenance/license and maintenance. Do not install or implement. Return the nine-field routing output and mark unavailable evidence UNVERIFIED or BLOCKED.
- Read your context and instructions
- Compiled the ui library router
Illustrative example (synthetic). No project was inspected, and no component, dependency, license, or accessibility behavior was verified.
REQUIRED BEHAVIOR: Date-range selection, keyboard operation, screen-reader labeling, internationalization, and fit with project design tokens.
SELECTED: UNVERIFIED. No project component or dependency evidence was supplied in this example.
SOURCE: UNVERIFIED. The project design system, installed primitives, configured registries, and approved sources have not been inspected.
WHY: The router checks those project sources in order before considering an external candidate or custom implementation.
ACCESSIBILITY: The requirements are identified for review; no candidate behavior was tested.
DEPENDENCY IMPACT: UNVERIFIED. Package presence and runtime cost were not measured.
LICENSE / PROVENANCE: UNVERIFIED. No source or license evidence was reviewed.
INSTALL REQUIRED: No. This example stops at routing and does not install a package.
FALLBACK / CUSTOM JUSTIFICATION: Inspect project components, installed primitives, configured registries, approved sources, and proven existing dependencies first. Consider external candidates only with explicit provenance and license review. Use a custom path only if earlier sources do not meet the requirements. No installation or implementation is reported.
Connects securely to your tools. The creator never sees your data.
About this skill
UI Library Router applies reuse before generation to frontend component and dependency choices: it checks your design system, installed primitives and approved sources before considering an external candidate or custom path. It routes the decision; it does not install or implement the chosen component.
Start by defining required behavior and accessibility. Read project authority, the existing design system, installed dependencies and configured registries before searching external candidates. Resolve in order: an existing project component or design system; already-installed primitives and configured registries; a project-approved registry or source; a proven primitive already in dependencies; an external candidate with explicit provenance and license review; then custom implementation only if earlier options do not meet the need.
Compare only plausible candidates for design-token fit, keyboard and accessibility behavior, responsive behavior, dependency and runtime cost, adaptation effort, provenance and license, and maintenance risk. Do not choose a library because it is fashionable or visually close in a screenshot.
The handoff records required behavior, selected source, why it fits, accessibility, dependency impact, license and provenance, whether installation is required, and any fallback or custom justification. It keeps unknowns visible as UNVERIFIED or BLOCKED.
Discovery and comparison are read-only. Package installation, registry import, code changes, commits, pushes, merges and deployments require separate authority. The workflow does not guarantee model output or replace project-specific rules; it stops at the routing decision.
The routing decision depends on available project requirements, governance, design-system, dependency, registry, accessibility, and provenance evidence. It does not install or implement components. If a required source, capability, or authority is unavailable, the result is marked UNVERIFIED or BLOCKED; the package does not guarantee model output or host-specific execution.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 17 days ago
Permissions
Read Files is required to inspect project authority and component/dependency evidence. Terminal/Shell, Write Files, Browser, Network Access, MCP, environment variables, and connected services are not assumed or required. If project, registry, external provenance, or license evidence is unavailable, mark it UNVERIFIED or BLOCKED.