agentleFS
automagik-devautomagik-dev/omni/.claude/skills/automagik-brand/SKILL.md

automagik-brand

Skill70 starsChanged 7 days 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, 4 of them edited.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 1

    1. automagik-si/omni★ 70100% same

    Edited · 4

    1. automagik-dev/genie★ 35383% same
    2. automagik-si/genie★ 35383% same
    3. namastexlabs/automagik-genie★ 35383% same
    4. automagik-si/arca★ 277% 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 repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. 3 are common, 0 are distinctive, and 3 are very specific to this project.

  • 3

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    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
  1. Very specific:

    When a file named SOURCE.json is beside this file, read it.

    line 17
  2. Common:

    Every path below is inside that folder.

    line 20
  3. Common:

    Read README.md, all of it.

    line 24
  4. Common:

    Never redraw a mark, the letters or Genie: no moving, reshaping, slimming, recolouring or outlining.

    line 46
  5. Very specific:

    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 …

    line 48
  6. Very specific:

    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 …

    line 64

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.json is beside this file, read it. Its into names the folder, from the repository's root (brand, for example).

Every path below is inside that folder.

Before you draw, style or write markup

  1. 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.
  2. For a page, a screen or a component, use tokens/tokens.css as it is: link it, or copy its declarations without changing a value. tokens/tokens.json is the record of the same values, with a note on each (README, "Tokens"). Then look in components/ for the component before you make one (README, "Components").
  3. 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 mark is always the triskle, for Automagik, Genie and Omni. There is no other logo (rule 1).
  • The 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 (rule 3).
  • 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-pink and triskle-violet are 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-warn and st-work, with st-okdot and st-warndot for 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").

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.