automagik-brand
Skill353 starsChanged 8 months agoApache-2.0View on GitHub
The Automagik brand (Automagik, Genie, Omni) as files in this repository's brand folder (docs/brand, unless SOURCE.json beside this skill names another). Use before any work on a logo or mark, a colour, type or fonts, a UI surface (a page, a screen, a form, a component, a sidebar, any HTML or CSS a person will see), a web or landing page, a slide deck, or brand art. Use it even when the request does not name the brand.
5 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- namastexlabs/automagik-genieword for word, first seen Nov 16, 2026
- automagik-si/arcaedited, first seen Nov 16, 2026
- automagik-dev/omniedited, first seen Nov 15, 2026
- automagik-dev/genieword for word, first seen Nov 15, 2026
- automagik-si/omniedited, first seen Nov 15, 2026
Other versions5 projects use a version of this.
Word for word · 2
- automagik-dev/genie★ 353100% same
- namastexlabs/automagik-genie★ 353100% same
Edited · 3
- automagik-dev/omni★ 7096% same
- automagik-si/omni★ 7096% same
- automagik-si/arca★ 286% same
Wrote their own version · 0
None found.
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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- mikro/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/refine/prompts/claude.mdCLAUDE.md
- authoringSkill
- brainstormSkill
- councilSkill
- deslopSkill
- docsSkill
- fixSkill
- genie-hacksSkill
- genieSkill
- mergeSkill
- refineSkill
- reportSkill
- researchSkill
- reviewSkill
- skill-auditSkill
- verifySkill
- wishSkill
- workflySkill
- workSkill
The file
We split this skill into the rules it gives an agent
7 rules. 2 are common, 0 are distinctive, and 5 are very specific to this project.
2
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
When a file named SOURCE.json is beside this file, read it.
- Common: line 20
Every path below is inside that folder.
- Common: line 24
Read README.md, all of it.
- Very specific: line 41
Never put a mark the owner has not approved beside Genie's, Omni's or Mykes's word.
- Very specific: line 52
Never redraw a mark, the letters or Genie: no moving, reshaping, slimming, recolouring or outlining.
- Very specific: line 54
Never invent a colour. Every colour comes from a token, and triskle-cyan, triskle-pink and triskle-violet are never text and never a UI …
- Very specific: line 70
If SOURCE.json is beside this file, the folder is a copy of Automagik's (so is one with a SOURCE.json inside docs/brand/, made by the copy …
“Common” is measured: kept by at least 6 in 10 of the 3 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
Automagik brand
The brand is a folder in this repository. It is the only source. Read the files; do not work from a memory of how the brand looks, and do not look for it anywhere else.
Where the folder is
docs/brand/, from the repository's root: in Automagik's repository, and in a copy unless the next line applies.- When a file named
SOURCE.jsonis beside this file, read it. Itsintonames the folder, from the repository's root (brand, for example).
Every path below is inside that folder.
Before you draw, style or write markup
- Read
README.md, all of it. It holds the rules, the file tables and the notes on colour, type, shape and components. Everything below points into it and adds nothing to it. - For a page, a screen or a component, use
tokens/tokens.cssas it is: link it, or copy its declarations without changing a value.tokens/tokens.jsonis the record of the same values, with a note on each (README, "Tokens"). Then look incomponents/for the component before you make one (README, "Components"). - For a logo, pick the file from the README's "Which logo file" table and use it unchanged.
What the README rules out
Each line names where the README says it. When this file and the README differ, the README is right.
- The triskle is Automagik's mark alone. Genie, Omni and Mykes do not carry it (rule 1).
- The
genie-lockup-*andomni-lockup-*files are RETIRED: they carry the triskle. Never use them (rule 1, "Which logo file"). - Genie, Omni and Mykes each show as their word, from
logo/wordmark/, with no mark beside it, until the owner approves a mark. Under Mykes: "Coming soon." in plain words (rule 10). - Never put a mark the owner has not approved beside Genie's, Omni's or Mykes's word. A product's mark, once approved, is flat and one colour, with its word's sparkle as the only colour (rule 9).
- Automagik's triskle is always in colour. The ink and cream marks are only for places where colour cannot be used (rule 2).
- Pets are never marks. Genie and Omni are characters: never in a header, a favicon or an app icon in the logo's place, and never beside a product's word (rules 3 and 10).
- The only Genie is the full-body one, from
genie/. Never crop to the head (rule 4, "Genie"). - Pick the drawing made for the size you show. Never scale the large drawing down to an icon (rule 6).
- The dot on the i is one sparkle, one colour per product: Automagik violet, Genie pink, Omni cyan. It is in the wordmark and lockup files already; do not draw it (rule 7).
- Never redraw a mark, the letters or Genie: no moving, reshaping, slimming, recolouring or outlining. Use the files (rule 8).
- Never invent a colour. Every colour comes from a token, and
triskle-cyan,triskle-pinkandtriskle-violetare never text and never a UI colour ("Colour"). - A status dot never stands alone: every one has a word or a mark beside it. The status colours
are
st-ok,st-bad,st-warnandst-work, withst-okdotandst-warndotfor dots ("Colour"). - Type is two families: Fredoka for titles, labels and buttons, and DM Sans for running text, used as "Type" says. The logo's letters are a drawing, never set in a font.
When the folder does not have it
The README's "Not here" lists what this folder leaves out on purpose, and for some of it says where it is: motion, the stage gradient and the tile colours are in the component stylesheet. Follow that list. Use the place it names, and do not treat a thing it leaves out as part of this set.
In a repository that carries a copy
If SOURCE.json is beside this file, the folder is a copy of Automagik's (so is one with a
SOURCE.json inside docs/brand/, made by the copy tool before the folder could be chosen). Do not
edit it here (README, "Using this in another repository").
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.

