agentleFS
Sign inStart free
FracteraFractera/Agent-Engineering-Infrastructure/.claude/skills/design-and-settings-of-elements/SKILL.md

design-and-settings-of-elements

Skill61 starsChanged 58 days agoMITView on GitHub

Both natures. Where the look (colours, fonts, shapes) and the site settings (name, description, menu, footer, cookie banner, feature switches) of an element are changed: in the shared Design and CONFIG of the node, or on the element's own pages. Load it when the person asks to change the colours, a font, the title, the menu, «hide sign-in», «turn on the footer» of an element, or asks where its design or settings are.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run npm run look -- <id> — it reads the element's links to the shared Design and CONFIG and prints the page for each:

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Design and settings of elements

Process: both — you change nothing yourself; you tell the person where to change it, in two or three lines.

A hint, not a law: models of late 2026 work worse under rigid step-by-step instructions.

Run npm run look -- <id> — it reads the element's links to the shared Design and CONFIG and prints the page for each:

  • link on (a single project): the shared Design or CONFIG in the core changes it for every element that follows it;
  • link off (an app factory, or an element set apart): the element's own pages — <its site>/<lang>/admin/design (fonts, colours, type, shapes) and <its site>/<lang>/admin/site-settings (with the sections features, header, footer, cookie banner). In the core they open from «Build → Design» and «Build → Site settings» of a custom element, and of root.

A saved value redraws the pages with no build; only languages need a deploy of the element. A native element has no pages of its own: its look and settings come from the shared Design and CONFIG. A look the settings cannot express (a new token, a new setting) is code — hand it to the element's agent (route-to-element). Turning a link on or off is the person's choice, on the element's «Settings → Danger zone».

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.

Check your setup, free