agentleFS
zakariafzakariaf/CatchLaw/.claude/skills/lonja-dialogs-and-surfaces/SKILL.md

lonja-dialogs-and-surfaces

Skill0 starsChanged 4 months agoNo licenceView on GitHub

Enforces Lonja modal and transient-surface policy across CATCHLAW dialogs, sheets, snackbars and plates — earning a modal only for a decision that must resolve before the user continues, squaring LonjaPanel and LonjaPlate off as ruled inset paper with no BoxShadow, no BorderRadius, no elevation and no scrim gradient, forcing barrierDismissible false on destructive and ambiguity modals, returning typed results like AmbiguityChoice instead of a bare bool, naming the consequence in the confirm label instead of OK, restoring focus to the opener after showLonjaDialog, and rendering the AmbiguityDialog that prints both conflicting instruments and refuses to choose. Use when adding showDialog or showModalBottomSheet, building lonja_ambiguity_dialog.dart, writing a destructive confirmation, wiring a SnackBar undo window, styling a panel or plate surface, choosing a modal over a route, or reviewing any barrier or dialog result in a diff.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

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.