systems
Skill2 starsChanged 31 days agoApache-2.0View on GitHub
Turn a selected visual direction into versioned tokens, reusable components, and an inspectable handoff. Use for design-system implementation, not to choose the creative direction by checklist.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- skyf0xx/gambittheir own version, first seen Sep 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- skyf0xx/gambit★ 29same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- canonSkill
- colorSkill
- formSkill
- graphicsSkill
- layoutSkill
- motionSkill
- pilotSkill
- typeSkill
- holdfastSkill
- aegisSkill
- assaySkill
- flightlineSkill
- gaugeSkill
- groundworkSkill
- gungnirSkill
- husbandrySkill
- load-bearingSkill
- pilotSkill
- plumbSkill
- stationkeepingSkill
- crucibleSkill
- envoySkill
- forgeSkill
- ledgerSkill
- prospectSkill
- reckoningSkill
- forageSkill
- touchstoneSkill
- bearingsSkill
- bulwarkSkill
- keelSkill
- liverySkill
- lookoutSkill
- pilotSkill
- seaworthySkill
- trialsSkill
- wellspringSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 41
When this stage is fulfilled: checklist advance contract --run "$RUN".
- Very specific: line 73
If an input or permission is missing, name the blocker and leave the relevant item pending.
- Very specific: line 79
After all required work and stage closures is recorded, use checklist done --run "$RUN".
≈ “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.
Files
<!--
Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0.
See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0
-->systems
Turn a selected visual direction into versioned tokens, reusable components, and an inspectable handoff. Use for design-system implementation, not to choose the creative direction by checklist.
Inputs
Selected direction or existing design language; target platforms; real component use cases; token and ownership constraints.
Run record
Use checklist 0.5 or newer for this SOP. Reading or reloading the skill must not reset work. For a new task, run checklist init "${CLAUDE_SKILL_DIR}" --new --path "/absolute/project"; retain its returned ID as RUN. For existing work, use checklist resume "$RUN", then checklist show --run "$RUN". Outside Claude, replace the skill-directory variable with this directory’s actual path.
Commands below record work after it is done. Replace evidence placeholders with concise artifact locations and observations. Manual confirmations are not independent proof; a sensor pass covers only the command and inputs it observed. verify does not close a stage; advance checks that its required readings are fulfilled. Use report --run "$RUN" for the retained history.
Procedure
contract
Inventory the selected decisions and actual consumers. Define primitive/semantic token roles, component responsibilities, and the source that owns each value; keep exceptions explicit.
Record these artifacts after doing the work:
- Token roles and representative component use cases are specified.
checklist check contract roles --run "$RUN" --evidence "<artifact and observation>" - Sources of truth, consumers, and exceptions are named.
checklist check contract ownership --run "$RUN" --evidence "<artifact and observation>"
When this stage is fulfilled: checklist advance contract --run "$RUN".
implement
Implement tokens and representative components, including important states and themes. Build living examples and exercise the actual consuming code; avoid parallel hand-maintained copies.
Record these artifacts after doing the work:
- Tokens and representative components exist as reusable artifacts.
checklist check implement artifacts --run "$RUN" --evidence "<artifact and observation>" - Live examples cover relevant states, themes, and consumer integration.
checklist check implement examples --run "$RUN" --evidence "<artifact and observation>"
When this stage is fulfilled: checklist advance implement --run "$RUN".
handoff
Compare the implemented examples with the chosen direction and measure the requirements that apply. Record versioning, migration, and contribution rules sized to the project.
Record these artifacts after doing the work:
- Implementation and relevant accessibility/visual checks are recorded.
checklist check handoff validation --run "$RUN" --evidence "<artifact and observation>" - Usage, ownership, and version/migration guidance are documented.
checklist check handoff adoption --run "$RUN" --evidence "<artifact and observation>"
When this stage is fulfilled: checklist advance handoff --run "$RUN".
Branches
A small product may need a token file and a few examples, not a platform. If creative direction is still open, use canon or another heuristic lens without demanding an upstream approval certificate.
If an input or permission is missing, name the blocker and leave the relevant item pending. A changed requirement may need a new run; an accepted checklist edit uses resume "$RUN" --refresh and requires fresh readings. To abandon work, use checklist reset --run "$RUN" --reason "<reason>"; history is retained.
Completion
An inspectable token/component package and adoption guidance. Surface bulwark can maintain its code boundaries after adoption.
After all required work and stage closures is recorded, use checklist done --run "$RUN". This archives the result without deleting its history; it does not authorise any external action.
Reference shelf
Open the technique relevant to the current step. These notes provide concrete methods and examples, not additional phases; this entrypoint defines the run's completion conditions.
- Hand off a selected visual direction as inspectable artifacts
- Examples that exercise real reusable components
- Semantic tokens with explicit ownership
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.