form
Skill2 starsChanged 31 days agoApache-2.0View on GitHub
Explore shape, depth, light, texture, and material metaphors for an interface. Use to generate visual form, not to enforce universal radius or shadow formulas.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- MohammadShehadeh/agent-skillstheir own version, first seen Nov 1, 2026
- lilly-builds/ads-cookingtheir own version, first seen Oct 20, 2026
- build-dezineer/skills-nuxt4-tw-webapptheir own version, first seen Oct 13, 2026
- gabriellst/codmtheir own version, first seen Aug 26, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- gabriellst/codm★ 4same name
- MohammadShehadeh/agent-skills★ 2same name
- build-dezineer/skills-nuxt4-tw-webapp★ 0same name
- lilly-builds/ads-cooking★ 0same 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
- graphicsSkill
- layoutSkill
- motionSkill
- pilotSkill
- systemsSkill
- 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
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 46
If the direction becomes a component family, systems can name and implement its tokens.
- Distinctive: line 50
Read selectively when a thread needs another perspective or a concrete technique.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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
-->form
Explore shape, depth, light, texture, and material metaphors for an interface. Use to generate visual form, not to enforce universal radius or shadow formulas.
Starting point
Form suggests how an interface can be touched, layered, or inhabited—even when it is only pixels. A material metaphor is useful when it creates relationships, not when it adds realistic decoration everywhere.
Bring a question, fragment, reference, or tension. Follow whichever association becomes useful; these invitations are not a sequence to complete. Speculation should remain distinguishable from an observed fact.
Thought experiments
Change the imagined material
Render the same interaction as folded paper, machined metal, ink, or frosted glass. Transfer one property such as layering, precision, absorption, or diffusion.
Flatten, then exaggerate
Imagine no depth at all, then an exaggerated relief. Find which distinction actually needs depth and which is better carried by spacing or colour.
Give the light a story
Try direct illumination, ambient haze, or backlit marks. Explore how light could organise hierarchy without requiring literal physical simulation.
A possible turn
A nested panel could be an inset tray, a stack of sheets, or simply a typographic section. Each implies different edges and shadows. Choosing “no object here” may be the most expressive form decision.
Leave the space open
Offer a few genuinely different possibilities, a sketch, an analogy, or a sharper question when useful. Do not turn every prompt into a scored diagnostic, a completion gate, or a demand for an action plan. The human may choose a direction, combine them, or leave the question open.
If the direction becomes a component family, systems can name and implement its tokens. Optical exceptions are allowed; references are techniques, not universal laws.
Optional references
Read selectively when a thread needs another perspective or a concrete technique. The notes supply possibilities, examples, and limits; none is a prerequisite or a requirement to close the exploration.
- Constructing a material relationship
- Edges, shadows, and separation
- A family of shapes and intentional exceptions
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.