agentleFS
NicholasFlemmerNicholasFlemmer/styx-app/.claude/skills/port-screen/SKILL.md

port-screen

Skill31 starsChanged 2 months agoApache-2.0View on GitHub

Port one prototype screen from Styx.dc.html into apps/desktop/src/renderer/screens with pixel fidelity. Locates the artboard by data-screen-label, extracts inline-style recipes, maps them to @styx/ui components, implements over fixture data, runs the visual diff.

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

    Run the design-fidelity-reviewer subagent.

    line 18

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

Port a screen: $ARGUMENTS

  1. Locate: grep -n 'data-screen-label="$0"' design/handoff/Styx.dc.html; slice to the next label. Note which second-strip toggles affect it (empty, error, toast, popout, audit…).
  2. Inventory: list every element top-to-bottom with its inline recipe (font, size, colour var, padding, borders, data-inv/data-on, style-hover). Keep it in a scratch note; do not commit it.
  3. Map each element to an existing @styx/ui component + variant (spec §8 via /spec-lookup 8). Missing component → stop and run /ui-component first. Never inline a one-off.
  4. Data: list the selectors needed (packages/core/src/selectors); add missing ones with tests. Screens read via useModel/useUi hooks and send commands.*; no fetching in components.
  5. Implement screens/<Screen>/<Screen>.tsx + .module.css using layout vars (--w-*, --h-*). Copy strings from @styx/core/copy.
  6. Keyboard: register screen shortcuts in keys/bindings.ts (spec §6); Esc via the overlay stack.
  7. States: implement every state the strip shows, driven by fixture variants (STYX_FIXTURE=<name>), not toggles.
  8. Verify: pnpm typecheck && pnpm test -F @styx/desktop, then /visual-diff $0 for dark+light × mac+win. Iterate until under threshold.
  9. Run the design-fidelity-reviewer subagent; fix findings.

Checklist: every element mapped to a §8 component · no raw hex · all --w-* widths used · copy verbatim · a11y per §9 (live regions, focus order, hit targets) · 4 visual variants pass · fixture states covered.

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.