agentleFS
Sign inStart free
boazsegevboazsegev/omoya/skills/web-build/SKILL.md

web-build

Skill1 starsChanged 6 days agoMITView on GitHub

This skill should be used when building static sites.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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. Distinctive:

    Keep data, content, templates and engine separate.

    line 9
  2. Distinctive:

    Keep the engine generic: no site facts, no per-section code.

    line 10
  3. Distinctive:

    Keep prose in Markdown files referenced from data.

    line 12
  4. Distinctive:

    Use explicit slugs, never derived from titles.

    line 13
  5. Distinctive:

    Keep templates logic-less.

    line 16
  6. Very specific:

    Add generic derivations (position flags, has_<list>, dates) instead of per-collection code.

    line 17
  7. Distinctive:

    Add asset processing only when measured need justifies it.

    line 25

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

Static Site Builds

Layers

  • Keep data, content, templates and engine separate; each fact lives in one place.
  • Keep the engine generic: no site facts, no per-section code.
  • Declare every output, including 404, robots.txt and sitemap.xml, as a template in data.
  • Keep prose in Markdown files referenced from data; keep labels inline.
  • Use explicit slugs, never derived from titles.

Templates

  • Keep templates logic-less; shape data so they render trivially.
  • Add generic derivations (position flags, has_<list>, dates) instead of per-collection code.
  • Let Mustache context climbing reach parent values; copy only when names shadow.
  • Escape by output type; emit raw HTML only from trusted sources.

Builds

  • Build from sources in one pass; never edit output.
  • Render everything before replacing the previous output.
  • Fail loudly on missing or unknown inputs.
  • Add asset processing only when measured need justifies it.

Resource

build.js implements these rules. Copy it into the project and change the config, not the code. Run bun build.js --help for the schema. It requires marked and mustache and replaces the output directory.

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