lonja-verdict-and-status
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Enforces the CatchLaw result surface — the letterpress verdict stamp struck between 4dp double rules 48dp beneath the engraved plate, the four categories meets, below-minimum, closed-season and protected, three non-colour signals per category so glyph and word survive greyscale and glare, protected separated from below-minimum by mark and wording because both take oxblood 7A2320, the non-blocking ochre StaleRuleBar under the app bar, a citation footnote carrying instrument, article, published and checked dates, and a permanent non-dismissable disclaimer. Use when building the result screen, adding a VerdictCategory, styling LonjaVerdictPanel or CitationFootnote or LonjaDisclaimer, wiring rule-pack expiry, tuning sunlight mode where every grey is deleted, auditing colour-only status encoding, checking app_ar.arb for imperative verdict strings, or reviewing verdict_panel.dart in a diff.
In this repository49 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- catchlaw-content-pipelineSkill
- catchlaw-conventions-indexSkill
- catchlaw-measurement-rulerSkill
- catchlaw-offline-guaranteeSkill
- catchlaw-reference-databaseSkill
- catchlaw-rule-engineSkill
- catchlaw-verdict-contractSkill
- accessibility-as-codeSkill
- adaptive-layoutSkill
- app-startup-and-bootstrapSkill
- async-safetySkill
- ci-pipeline-and-gatesSkill
- codegen-and-toolchainSkill
- custom-canvas-and-gesturesSkill
- dart3-idioms-and-coding-standardsSkill
- dartdoc-conventionsSkill
- dependency-hygieneSkill
- design-review-workflowSkill
- design-system-structureSkill
- error-handling-typed-resultsSkill
- flutter-architectureSkill
- flutter-conventions-indexSkill
- flutter-performanceSkill
- forms-and-inputSkill
- i18n-rtl-l10nSkill
- lint-and-style-configSkill
- local-notifications-schedulerSkill
- naming-conventionsSkill
- navigation-and-routingSkill
- persistence-driftSkill
- project-structure-and-packagesSkill
- run-codegenSkill
- run-migrationSkill
- scaffold-feature-moduleSkill
- service-boundary-and-nativeSkill
- state-management-riverpodSkill
- testing-strategySkill
- value-objects-money-and-unitsSkill
- widget-compositionSkill
- widget-golden-and-a11y-testingSkill
- lonja-buttonsSkill
- lonja-design-tokensSkill
- lonja-dialogs-and-surfacesSkill
- lonja-forms-and-controlsSkill
- lonja-icons-and-platesSkill
- lonja-lists-and-tablesSkill
- lonja-navigation-chromeSkill
- lonja-typographySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
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
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.

