agentleFS
petecurranpetecurran/sorted/.claude/skills/rebrand/SKILL.md

rebrand

Skill0 starsChanged 47 days agoMITView on GitHub

Rebrand Sorted for another council (name, colours, case prefix and an optional crest), then check every page at desktop and phone sizes. Use when asked to rebrand or re-skin it, or to make it look like another council's.

4 other projects use a version of this.

Adopted by

Most recently taken up by

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

    If a crest is wanted, draw it as static/shared/marks/<short-name>.svg: viewBox="0 0 64 64", drawn in currentColor so it takes the header's …

    line 9
  2. Very specific:

    Make sure the app is running on 8800 (curl -s http://localhost:8800/api/health).

    line 10

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

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

Rebrand to: $ARGUMENTS

  1. Read content/brand.json, including its _about note: it sets the rules. colour is the header and button colour and must take white text at 4.5:1 or better; accent highlights the Demo badge and focus rings; place is the short name used in sentences; case_prefix starts every case reference. Never reuse "Mersey Vale" or "MVCC" inside the new name.
  2. If a crest is wanted, draw it as static/shared/marks/<short-name>.svg: viewBox="0 0 64 64", drawn in currentColor so it takes the header's text colour. humpington-pirate.svg is a worked example. Put its file name in mark, or leave mark empty for the standard gull and waves.
  3. Make sure the app is running on 8800 (curl -s http://localhost:8800/api/health). If it isn't, start it with scripts/start_server.sh, without FT_RESET.
  4. Save content/brand.json. Both sites change on the next page load, and screens opened with ?live=1 reload by themselves. To preview a brand without saving it, write it to a temporary file and pass that file to the check below with --try.
  5. Run uv run --with playwright python scripts/brand_check.py. It uses the installed Google Chrome, in its own profile. If any view fails (the old name still showing, a broken logo, low contrast, a page wider than the screen, a console error), fix the cause and run it again until every view passes.
  6. Report the new brand, the contact sheet at http://localhost:8800/dev/brand-check/, and how to undo it: git restore content/brand.json, and delete the crest file if you made one.

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.