ordinus-ui-system
Skill111 starsChanged 5 months agoMITView on GitHub
Build Ordinus renderer UI in the intended product style. Use when changing React UI, layout, Tailwind styling, shadcn-style components, status panels, navigation, empty states, forms, tables, task views, or user-facing product text.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- lavishSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- documentation-and-adrsSkill
- electron-secure-boundarySkill
- grill-meSkill
- idea-discoverySkill
- ipc-contract-designSkill
- provider-runtime-adapterSkill
- shadcn-project-workflowSkill
- sqlite-minimal-persistenceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. About 0 are common, 17 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read DESIGN.md before changing renderer UI, layout, Tailwind styling, shadcn-style components, status surfaces, empty states, forms, task …
- Very specific: line 16
Treat DESIGN.md as the canonical source for visual tokens, component vocabulary, status language, density, and copy guidance.
- Distinctive: line 24
Avoid turning the app into a generic chat page.
- Distinctive: line 29
Do not default to generic assistant layouts, oversized prompt boxes, purple gradients, vague glowing panels, or decorative AI-themed …
- Distinctive: line 32
Use typography, spacing, color, and motion deliberately.
- Distinctive: line 33
Prefer subtle useful motion for state transitions, loading, reveal, and feedback.
- Distinctive: line 39
Use shadcn-style components and local reusable primitives.
- Distinctive: line 40
Prefer restrained cards for individual panels, not nested card-heavy layouts.
- Distinctive: line 41
Use lucide icons for recognizable actions.
- Distinctive: line 42
Keep typography readable and proportional to the UI surface.
- Distinctive: line 43
Avoid decorative gradients, orbs, bokeh, and oversized hero sections.
- Distinctive: line 45
Avoid one-note palettes. Use a restrained base with purposeful accent colors for state and hierarchy.
- Very specific: line 50
Read DESIGN.md and identify the workflow the UI supports.
- Distinctive: line 52
Put the primary state and next action above secondary details.
- Distinctive: line 53
Use existing components before creating new primitives.
- Distinctive: line 54
Keep labels concise and user-centered.
- Distinctive: line 55
Check mobile/narrow and desktop layouts for overflow.
- Distinctive: line 56
Run typecheck, lint, and build.
- Very specific: line 61
Avoid references to browser/session/localStorage/Electron internals unless the screen is explicitly diagnostic.
- Distinctive: line 62
Prefer "Workspace ready" over "IPC bridge initialized".
- Distinctive: line 63
Prefer "No work items yet" over "No database rows".
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Ordinus UI System
Objective
Make Ordinus feel like a calm, practical command center for AI-assisted work.
Design System Source
Read DESIGN.md before changing renderer UI, layout, Tailwind styling, shadcn-style components, status surfaces, empty states, forms, task views, provider views, or user-facing product copy.
Treat DESIGN.md as the canonical source for visual tokens, component vocabulary, status language, density, and copy guidance. If it conflicts with AGENTS.md, the secure Electron boundary and product principles in AGENTS.md win.
Product Feel
- Work-focused, not marketing-focused.
- Clear status over decorative flourish.
- Dense enough for repeated use, but not crowded.
- User-facing text should describe product state and next actions, not internal implementation.
- Avoid turning the app into a generic chat page.
- Distinctive but calm. Ordinus should feel intentionally designed without becoming loud or theatrical.
Avoid Generic AI UI
- Do not default to generic assistant layouts, oversized prompt boxes, purple gradients, vague glowing panels, or decorative AI-themed backgrounds.
- Choose a clear product direction before styling: desktop command center, operational workspace, project cockpit, or agent control surface.
- Let the product context drive visual choices. Agent status, work progress, outputs, and attention states matter more than visual novelty.
- Use typography, spacing, color, and motion deliberately. The interface should feel polished because details are consistent, not because effects are abundant.
- Prefer subtle useful motion for state transitions, loading, reveal, and feedback. Avoid animations that distract from work.
- Make empty states, status labels, and action hierarchy feel designed, not placeholder-like.
UI Rules
- Align colors, typography, spacing, radius, status labels, and component naming with
DESIGN.md. - Use shadcn-style components and local reusable primitives.
- Prefer restrained cards for individual panels, not nested card-heavy layouts.
- Use lucide icons for recognizable actions.
- Keep typography readable and proportional to the UI surface.
- Avoid decorative gradients, orbs, bokeh, and oversized hero sections.
- Make status visible: planned, running, blocked, completed, needs attention.
- Avoid one-note palettes. Use a restrained base with purposeful accent colors for state and hierarchy.
- Match component density to the workflow: dashboards and work boards should be scan-friendly, not spacious landing pages.
Workflow
- Read
DESIGN.mdand identify the workflow the UI supports. - Choose the smallest design-system component vocabulary that fits that workflow.
- Put the primary state and next action above secondary details.
- Use existing components before creating new primitives.
- Keep labels concise and user-centered.
- Check mobile/narrow and desktop layouts for overflow.
- Run typecheck, lint, and build.
Copy Guidelines
- Say what the user can understand now.
- Avoid references to browser/session/localStorage/Electron internals unless the screen is explicitly diagnostic.
- Prefer "Workspace ready" over "IPC bridge initialized".
- Prefer "No work items yet" over "No database rows".
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.

