static-site-forge
Skill0 starsChanged 15 days agoNo licenceView on GitHub
Build a static client site from one Python generator file as the single source of truth, and verify every page in a real browser on every build — screenshots, axe, JS errors, overflow. Use when starting or rebuilding a static site, when pages have drifted out of sync with each other, when a palette or site-wide token change is needed, or when live third-party data has to be exercised without network access. Triggers on "build the site", "new client site", "site generator", "single source of truth", "the pages don't match", "that's wrong on one page but right on another", "flip the palette", "make it light", "dark mode", "design tokens", "verify every page", "axe every page", "screenshot every page", "check it in a browser", "test the feed offline", "mock the API", "is the contrast ok", "stop asking me questions", "just decide", "it keeps asking me things", "don't ask, just build". For the client delivery pipeline — scope preflight, ship check, client artifact — see client-site; this is the engineering layer beneath it. For auditing a site someone else built, see web-accessibility.
- Installs packages
In this repository22 other files it gives its agents.
- analyticsSkill
- avoid-ai-writingSkill
- core-web-vitalsSkill
- factory-floorSkill
- marketing-ai-seoSkill
- marketing-copy-editingSkill
- owasp-securitySkill
- refactoring-uiSkill
- resend-formsSkill
- s4h-decision-premortem-analysisSkill
- search-consoleSkill
- session-hygieneSkill
- site-ingestSkill
- skill-forgeSkill
- skill-scoutSkill
- storybrand-messagingSkill
- top-designSkill
- ux-heuristicsSkill
- video-briefSkill
- watchSkill
- web-accessibilitySkill
- web-typographySkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.