agentleFS
Sign inStart free
bherbruckbherbruck/solidcraft/skills/solidcraft-ui/SKILL.md

solidcraft-ui

Skill15k starsChanged 18 days agoApache-2.0View on GitHub

Use when adding or changing a SolidCraft dialog, panel, menu, overlay, canvas, camera input, slider, icon or colour in crates/ui-egui. Covers the single UI container, the UI kit, navigation::handle, theme tokens, command icons and UI scenarios.

1 other project uses a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about bherbruck/solidcraft

The biggest 5 of 75 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 75

Talked about on GitHub, YouTube, Bluesky and Hacker News (75 times).

On GitHub · 46

41 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On Hacker News · 1

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    All panels, floating sheets, menus, overlays and platform UI windows use ui_kit::Container, directly or through Panel, Window, Confirm and …

    line 11
  2. Distinctive:

    Do not construct raw egui hosts, outer popup or window frames, or shadows in feature modules.

    line 13
  3. Very specific:

    Every page or canvas with a camera (viewport, Render preview, a flat pattern or drawing page) calls navigation::handle …

    line 22
  4. Very specific:

    Every label, tooltip and message goes through the catalogs: skills/solidcraft-ui-text/SKILL.md.

    line 28
  5. Very specific:

    Run the app, drive it and read the screenshot: skills/solidcraft-agent-tools/SKILL.md.

    line 31

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

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

Dialogs and UI

The UI is thin: it reads engine state and acts through app.run(id, params) or app.start(id). A dialog is a form that builds the parameters of a command (skills/solidcraft-commands/SKILL.md). The full control list is docs/ui-kit.md.

One outer container

  • All panels, floating sheets, menus, overlays and platform UI windows use ui_kit::Container, directly or through Panel, Window, Confirm and Menu. Declare the semantic Surface; workspace panels use its shared layout policy and chrome.
  • System and report windows use ui_kit::Window; its low-level host builder is kit-private.
  • Do not construct raw egui hosts, outer popup or window frames, or shadows in feature modules.
  • cargo xtask ui-containers checks source and examples in all current and future crates and apps, recursively. It runs in the fast repository CI job and in cargo xtask ci, with no caller allowances. The inventory and the legitimate content and native exceptions are in docs/ui-container-audit.md.

Controls and colour

  • Colours, typography, dimensions and spacing come from theme::Tokens (crates/ui-egui/src/theme.rs). No literal colours in feature code.
  • Sliders only through ui_kit::slider. Form rows use row, expr_row, text_row, choice_row and count_row from crate::ui_kit (crates/ui-egui/src/ui_kit/).
  • Confirmations use ui_kit::Confirm; the old Prompt element is gone.

One set of camera controls

Every page or canvas with a camera (viewport, Render preview, a flat pattern or drawing page) calls navigation::handle (crates/ui-egui/src/navigation.rs) with its NavCaps (orbit off for flat 2D pages). Never hand-roll camera input from drags, the wheel or pinch; hand_rolled_camera_input_is_rejected fails if a page does.

Icons

Command icons are original SVG masters compiled through crates/ui-egui/src/icon_svg.rs. Read assets/AGENTS.md, assets/icons/ui/AGENTS.md and assets/icons/ui/STYLE_GUIDE.md first, add the ATTRIBUTION.md row, and run cargo xtask icons and cargo xtask assets. See skills/solidcraft-ground-rules/SKILL.md.

Text

Every label, tooltip and message goes through the catalogs: skills/solidcraft-ui-text/SKILL.md. A new behaviour that is on by default: skills/solidcraft-preferences/SKILL.md.

Look at the result

Run the app, drive it and read the screenshot: skills/solidcraft-agent-tools/SKILL.md. A UI scenario (crates/ui-egui/tests/scenarios/*.json) covers the clicks; see skills/solidcraft-tests/SKILL.md. Work that takes long must not block the window: skills/solidcraft-performance/SKILL.md.

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.

Check your setup, free