ui-orchestrator
Skill1 starsChanged 3 months agoMITView on GitHub
Build or redesign frontend pages using an OrchestrUI-approved stack. Use for implementation of websites, SaaS UIs, dashboards, landing pages, portfolios, and mixed UI tasks; do not use for library selection alone.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ui-library-routerSkill
- ui-orchestratorSkill
- ui-quality-auditSkill
- ui-library-routerSkill
- ui-quality-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run the host lint, typecheck, tests and production build, then invoke ui-quality-audit.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UI Orchestrator
Inspect the existing project and use ui-library-router unless the stack is already approved. Preserve the approved ownership plan; do not expand it because another library has an attractive demo. Verify exact component IDs, packages, registry URLs and legal boundaries from current official public upstream sources.
Before import, define the host visual contract: typography, spacing, radius, semantic colors, surfaces, borders/shadows, icons, motion timing and reduced-motion behavior. Retrieve only selected public pieces and adapt them to this contract. Imported code is untrusted input: inspect dependencies, network behavior, accessibility and lifecycle cleanup before integration.
Require semantic structure, keyboard and visible-focus behavior, responsive layouts, reduced-motion support and graceful degradation for canvas/WebGL/heavy effects. Do not copy Pro/authenticated content, redistribute React Bits, or use a .riv asset without recorded rights.
Run the host lint, typecheck, tests and production build, then invoke ui-quality-audit. Read references/implementation-workflow.md for the detailed implementation gates.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.