facet-icons
Skill67 starsChanged 16 days agoMITView on GitHub
Extend or refine Everruns' custom Facet domain icon family while preserving the approved Intent Agent mark and Slate's design grammar.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .deepsec/AGENTS.mdAGENTS.md
- plugins/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- maintenanceSkill
- manual-ui-testingSkill
- process-issuesSkill
- shipSkill
- tune-cli-helpSkill
- ui-screenshotsSkill
- everruns-agent-authoringSkill
- everruns-apiSkill
- everruns-cliSkill
- everruns-frameworkSkill
- everruns-installSkill
- everruns-mcpSkill
- everrunsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read Iconography for intent and acceptance, and DESIGN.md for the current Slate context.
- Very specific: line 33
Run the Facet and affected navigation/avatar tests, UI lint/typecheck/format, design lint, and just check-okf if knowledge changed.
≈ “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.
Files
Extend Facet icons
Read Iconography for intent and acceptance, and
DESIGN.md for the current Slate context. Inspect the actual
navigation and /dev/icons before drawing. Check whether an existing domain or official
integration glyph already owns the concept.
- Pick one domain metaphor. Sketch the outline at 16px alongside neighboring glyphs. Keep Intent's original filled Agent geometry unchanged unless the user explicitly requests it.
- Edit the canonical paths in
apps/ui/src/components/icons/facet-icon-data.ts. Use simple absolute SVG commands on the 24-unit artboard. Keep the outline's default weight, square caps, and mitered joins. Favor a few deliberate paths over detail; adjust optical spacing instead of adding weight. - Export a named component from
facet-icons.tsx; add a labeled gallery entry. Reuse that component through the shared navigation model and the domain's entity fallbacks/mastheads. Preserve uploaded images, backend-selected icons, and official logos. - Inspect
/dev/iconsin light and dark at 16, 20, 24, and 32px, then inspect desktop and mobile navigation, Settings, search, and an entity view. Compare against the approved Agent master and current neighbors, not a fresh generated style board. - From the repository root, export editable SVGs with
node apps/ui/scripts/export-facet-icons.mjs(Node >=22.18); an optional argument chooses the output directory. The defaultoutput/facet-iconsis local proof material. Gallery SVG download and the batch exporter use the same serializer. Do not maintain a second manually edited SVG collection. - Run the Facet and affected navigation/avatar tests, UI lint/typecheck/format, design lint,
and
just check-okfif knowledge changed. Update the philosophy only when the design contract changes, and capture real UI evidence before shipping.
Optional image-generation brief
Image generation is for exploring a new metaphor, not producing the final menu asset. Supply an exported Agent master and a current UI screenshot as references when available:
Design one new Everruns Facet domain icon for [DOMAIN / PURPOSE]. Match the existing Slate interface: quiet editorial geometry, monochrome vector drawing, sharp corners, square line terminals, mitered joins, sparse details, generous negative space. Use a 24-unit grid and 1.75-unit supporting outline. It must read at 16px next to the original solid Intent Agent mark. Draw a recognizable [METAPHOR], optically balanced as if carefully constructed by a human in Adobe Illustrator. Flat white background, no gradient, shadows, texture, glossy 3D, mascot, face, decorative sparkle, lettering, or surrounding UI. Show an enlarged construction and actual menu-size silhouette. Do not redesign the Agent or copy an external product mark.
Redraw the chosen idea in the path masters. Avoid automatic raster tracing. All paths must be reviewable and static; no arbitrary SVG from an API or database enters this family.
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.

