agentleFS
muratgurmuratgur/ordinus/.claude/skills/ordinus-ui-system/SKILL.md

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.

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
  1. Very specific:

    Read DESIGN.md before changing renderer UI, layout, Tailwind styling, shadcn-style components, status surfaces, empty states, forms, task …

    line 14
  2. Very specific:

    Treat DESIGN.md as the canonical source for visual tokens, component vocabulary, status language, density, and copy guidance.

    line 16
  3. Distinctive:

    Avoid turning the app into a generic chat page.

    line 24
  4. Distinctive:

    Do not default to generic assistant layouts, oversized prompt boxes, purple gradients, vague glowing panels, or decorative AI-themed …

    line 29
  5. Distinctive:

    Use typography, spacing, color, and motion deliberately.

    line 32
  6. Distinctive:

    Prefer subtle useful motion for state transitions, loading, reveal, and feedback.

    line 33
  7. Distinctive:

    Use shadcn-style components and local reusable primitives.

    line 39
  8. Distinctive:

    Prefer restrained cards for individual panels, not nested card-heavy layouts.

    line 40
  9. Distinctive:

    Use lucide icons for recognizable actions.

    line 41
  10. Distinctive:

    Keep typography readable and proportional to the UI surface.

    line 42
  11. Distinctive:

    Avoid decorative gradients, orbs, bokeh, and oversized hero sections.

    line 43
  12. Distinctive:

    Avoid one-note palettes. Use a restrained base with purposeful accent colors for state and hierarchy.

    line 45
  13. Very specific:

    Read DESIGN.md and identify the workflow the UI supports.

    line 50
  14. Distinctive:

    Put the primary state and next action above secondary details.

    line 52
  15. Distinctive:

    Use existing components before creating new primitives.

    line 53
  16. Distinctive:

    Keep labels concise and user-centered.

    line 54
  17. Distinctive:

    Check mobile/narrow and desktop layouts for overflow.

    line 55
  18. Distinctive:

    Run typecheck, lint, and build.

    line 56
  19. Very specific:

    Avoid references to browser/session/localStorage/Electron internals unless the screen is explicitly diagnostic.

    line 61
  20. Distinctive:

    Prefer "Workspace ready" over "IPC bridge initialized".

    line 62
  21. Distinctive:

    Prefer "No work items yet" over "No database rows".

    line 63

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read DESIGN.md and identify the workflow the UI supports.
  2. Choose the smallest design-system component vocabulary that fits that workflow.
  3. Put the primary state and next action above secondary details.
  4. Use existing components before creating new primitives.
  5. Keep labels concise and user-centered.
  6. Check mobile/narrow and desktop layouts for overflow.
  7. 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".

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.