agentleFS
LockeZeRoLockeZeRo/site-builder/CLAUDE.md

site-builder

CLAUDE.md0 starsChanged 3 months agoMITView on GitHub

A hand-written WordPress lead-generation site — theme, catalogue plugin and deploy tooling — driven from Claude Code and configured from one file. First run? This repo ships untrained. Run /train (or paste TRAINING.md) before touching a page. Until then the templates carry [PLACEHOLDER] copy and no business details. 1. Never publish to production without explicit approval. Staging is free; a wrong phone number on a live site is not. 2. Load site-dna before writing or editing any page or site…

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Every business detail comes from site.config.php: No template ever hardcodes a phone number, address, email or licence.

    line 15
  2. Distinctive:

    Escape on output, sanitise on input: Every time.

    line 25
  3. Distinctive:

    All three should be silent.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
CLAUDE.md

Site Builder

A hand-written WordPress lead-generation site — theme, catalogue plugin and deploy tooling — driven from Claude Code and configured from one file.

First run? This repo ships untrained. Run /train (or paste TRAINING.md) before touching a page. Until then the templates carry [PLACEHOLDER] copy and no business details.

Rules

  1. Never publish to production without explicit approval. Staging is free; a wrong phone number on a live site is not.
  2. Load site-dna before writing or editing any page or site copy.
  3. Every business detail comes from site.config.php. No template ever hardcodes a phone number, address, email or licence. If a value is missing, add the constant — do not inline it.
  4. Never commit site.config.php, credentials, or real customer data. Subscriber and lead exports are gitignored deliberately: deleting such a file later does not remove it from git history.
  5. Never display a third-party brand mark without authorisation. Being a reseller is not automatically permission.
  6. No page builders, no CSS frameworks, no jQuery. Hand-written and mobile-first, on purpose.
  7. Escape on output, sanitise on input. Every time.

(/train appends your own never-list here.)

Skills

SkillTriggers
train"train", "onboard", "set up my site"
site-dnaloaded before any page or copy work
page-builder"new page", "add a section", "change the hero"
seo-schema"schema", "structured data", "SEO", "meta description"
lead-forms"form", "lead", "form not sending", "spam"
deploy"deploy", "staging", "maintenance mode", "import listings"

Layout

site.config.example.php   the single source of business truth
theme/                    the WordPress theme
  inc/                    helpers, schema, lead form, menus, enqueue
  template-parts/         reusable sections
  page-<slug>.php         resolved automatically by page slug
plugin-listings/          catalogue custom post type, meta, shortcode
deploy/                   maintenance mode, catalogue importer

Checks before calling anything done

find . -name "*.php" -exec php -l {} \; | grep -v "No syntax errors"
grep -rn "\[[A-Z][A-Za-z ]*\]" theme/
grep -rnE "[0-9]{3}-[0-9]{3}-[0-9]{4}" theme/ plugin-listings/

All three should be silent. The second is the one that catches real mistakes.

Companion repo

Social Autoposter and Creator runs the same brand's social content. Its voice-dna and this repo's site-dna should agree — they describe one company.

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.