agentleFS
LockeZeRoLockeZeRo/site-builder/.claude/skills/train/SKILL.md

train

Skill0 starsChanged 3 months agoMITView on GitHub

Interview the user about their business and write site.config.php plus the site DNA. Run this first, before any page work. Triggers on "train", "onboard", "set up my site", "/train".

8 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

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    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:

    Read TRAINING.md at the repo root and follow it.

    line 8
  2. Distinctive:

    If either says it is already trained, do not overwrite silently.

    line 17
  3. Very specific:

    Verify it parses: php -l site.config.php

    line 31
  4. Distinctive:

    Check nothing was missed:

    line 35
  5. Very specific:

    If they run Social Autoposter and Creator, its voice-dna covers the same ground as site-dna §1–3.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 8 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

/train — teach the agent this business

Read TRAINING.md at the repo root and follow it. This file covers how to run it.

Before you start

test -f site.config.php && echo "ALREADY CONFIGURED" || echo "untrained"
grep -l "UNTRAINED" .claude/skills/*/SKILL.md 2>/dev/null

If either says it is already trained, do not overwrite silently. Report what exists and ask whether to revise a section or start over.

Running it

  • Two or three questions at a time, conversationally. Never dump the list.
  • Reflect each answer back in one sentence and check it landed.
  • Push once on vague answers — ask for an example, a number, or a rule.
  • Never invent a business fact. A guessed licence number or service area ends up on a live page in front of that company's customers.

Writing the files

  1. cp site.config.example.php site.config.php and fill in every constant. Verify it parses: php -l site.config.php
  2. Fill .claude/skills/site-dna/SKILL.md, removing the UNTRAINED banner.
  3. Set the palette in theme/assets/css/tokens.css.
  4. Append the never-list to CLAUDE.md.
  5. Check nothing was missed:

    grep -rn "\[[A-Z][A-Za-z ]*\]" theme/ site.config.php .claude/skills/site-dna/SKILL.md

    Placeholders left in template copy are the single most common way a half-configured site goes live saying [Your positioning line].

Already trained the social repo?

If they run Social Autoposter and Creator, its voice-dna covers the same ground as site-dna §1–3. Offer to copy it across rather than re-interviewing. One brand, one voice, two surfaces.

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.