Skill LibraryPrompt Skill1 DesignsTop Views

Component Library Fit Intake

Evaluate license, brand voice, stack fit, theming, and maintenance cost before adopting resources such as Radix, shadcn, Headless, Material, Fluent, Carbon, Spectrum, GOV.UK, or USWDS.

Skill Uses0

Recorded selections across prompt workflows.

Public Designs1

Ranked by views, then community favorites.

Prompt Lines9

Reusable instruction lines for generation.

Author@Interface Lab

Asset

Skill Directive

Description

Evaluate license, brand voice, stack fit, theming, and maintenance cost before adopting resources such as Radix, shadcn, Headless, Material, Fluent, Carbon, Spectrum, GOV.UK, or USWDS.

TagsAsset

Skill Prompt

- First read existing components, tokens, CSS variables, Tailwind/shadcn/Radix config, dependency tree, and design-system docs; do not add a second system just because a library looks polished.
- Collect inputs: product domain, target users, frontend framework, SSR/CSR boundary, required component list, brand voice, accessibility level, bundle budget, and license/commercial constraints.
- Classify each candidate first: unstyled primitives, copy-in source components, full design system, Web Components, government service system, or enterprise component suite; these roles are not interchangeable.
- Check licensing item by item: code license, separate font/icon/brand-asset terms, commercial limits, notice requirements, trademark risk, and implied official endorsement.
- Assess technical fit: React/Next/Vue/Lit/Web Components match, SSR/hydration risk, tree shaking, CSS/theming strategy, dark mode, forms, overlays, and focus management.
- Assess visual fit: will the product look like Google, Microsoft, IBM, Adobe, or an official government service? Unaffiliated projects should abstract principles instead of copying brand expression.
- Output a decision matrix: candidate, role, install path, allowed component scope, tokens to map, forbidden uses, main risks, QA checklist, and rollback plan.
- Recommend adoption only when the library removes real complexity, fills accessible interaction gaps, or provides stable system constraints; decorative or single-page needs should use local components first.
- Sources referenced: Radix Primitives, shadcn/ui, Headless UI, Material Web, Fluent UI, Carbon Design System, Spectrum Web Components, GOV.UK Frontend, and USWDS official docs and license notes. The content is rewritten as Interface Lab component-library intake guidance.

Public directive summary shown; Pro unlocks the full prompt.

Layout Info

Designs below are ordered by views. Top items use live previews; the rest stay fast thumbnail cards.

Unlock Pro All Skills

Component Library Fit Intake

More pages using Component Library Fit Intake