ui-build
Skill0 starsChanged 4 months agoMITView on GitHub
Routes UI implementation to original skills for websites, dashboards, CRM, and administrative applications.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to select a design or implementation provider.
- Very specific: line 11
Read the complete original SKILL.md and required references from the current-session catalog.
- Very specific: line 45
Use an existing design system or verified current screen as the visual target when it fits the task.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UI Build Router
Use this skill to select a design or implementation provider. For a clear task, select the leaf directly; an established route remains valid on follow-up turns.
Read the complete original SKILL.md and required references from the
current-session catalog. Keep reviewed upstream and native plugin ownership;
installed files alone do not prove exposure. A missing provider needs its
official setup or reviewed dependency, never a local workflow replacement.
Routing
- Working screens for dashboards, CRM, ERP, admin tools or other business apps
->
ui-business-apps; its owner policy chooses the author design provider. - Clear dense-interface design or system-consistency task ->
interface.interface-design. - Pattern, chart, typography or stack guidance for a specific UI ->
uipro.ui-ux-pro-max. - UX shape, targeted refinement or hardening ->
impeccable.impeccable, using the author's command/reference for that request and Operate mode for app UI. - Major new visual direction with no sufficient reference ->
ui-concept-first. - Extracting implementation constraints from a visual reference ->
design-system-extractor - Figma frame/selection/component implementation ->
figma-to-code - Frontend pages, components, app or dashboard implementation ->
build-web-apps:frontend-app-builder - Analytics, data storytelling, chart choice or visualization implementation
->
build-web-data-visualization:data-visualization - Image-based alternatives or mobile concepts ->
product-design:ideate - Translate a selected visual into code ->
product-design:image-to-code - Implement from a live URL reference ->
product-design:url-to-code - Build a complete Sites website ->
sites:sites-building - shadcn/component composition ->
build-web-apps:shadcn - React/Next.js implementation performance ->
build-web-apps:react-best-practices - Strong style constraints -> an exposed author design skill matching the brief; preserve the original provider and the user's selected visual direction.
Rule
Use an existing design system or verified current screen as the visual target
when it fits the task. Do not force image generation or a fresh concept approval
for ordinary changes. Select ui-qa only for the evidence the implementation
needs; use playwright-visual-qa when visual fidelity is material.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- wlsdks/ontology-atlas★ 146same name
- LiriRaid/waymark★ 2same name
- TucsenRoman/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository62 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-ui-reviewSkill
- agent-retrospectiveSkill
- agents-md-retrospectiveSkill
- agent-squadSkill
- architecture-mapSkill
- architecture-normalizerSkill
- architecture-principlesSkill
- authz-boundary-reviewSkill
- c-cppSkill
- code-qualitySkill
- code-reviewSkill
- code-to-figmaSkill
- code-wiki-ruSkill
- context-packSkill
- core-engineeringSkill
- debuggingSkill
- dependency-advisory-auditSkill
- deserialization-parser-reviewSkill
- design-system-extractorSkill
- documentationSkill
- engineering-standardsSkill
- esp32Skill
- esphomeSkill
- external-agent-pack-auditSkill
- fastSkill
- figma-to-codeSkill
- fix-security-findingSkill
- goSkill
- homeassistantSkill
- mcp-tool-routerSkill
- migration-plannerSkill
- mobile-qaSkill
- multi-agent-pr-reviewSkill
- performanceSkill
- playwright-visual-qaSkill
- pythonSkill
- quality-gatesSkill
- refactoringSkill
- responsive-breakpoint-checkSkill
- review-routerSkill
- rustSkill
- secrets-and-config-reviewSkill
- security-diff-reviewSkill
- security-routerSkill
- securitySkill
- session-memorySkill
- specialist-dispatchSkill
- subagent-result-mergeSkill
- supply-chain-reviewSkill
- tdd-guardSkill
- testing-tddSkill
- threat-modelSkill
- typescriptSkill
- ui-business-appsSkill
- ui-concept-firstSkill
- ui-figmaSkill
- ui-qaSkill
- ui-researchSkill
- ui-routerSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.