agentleFS
Sign inStart free
oocxoocx/tfplan2md/.claude/skills/website-quality-check/SKILL.md

website-quality-check

Skill174 starsChanged 2 months agoMITView on GitHub

Run a lightweight, repeatable quality checklist for the website (including style guide adherence).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    If a shared authored source changed, verify representative consuming pages in website/dist/.

    line 50
  2. Distinctive:

    If issues are found, fix them or record them with a clear plan.

    line 51

≈ “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

Skill Instructions

Purpose

Provide a lightweight, repeatable quality checklist for website changes in the Eleventy site under website/.

Hard Rules

Must

  • Verify the change follows website/README.md, website/specification.md, and website/architecture.md.
  • If the change touches examples or authoring structure, read the relevant website ADRs before finalizing the change.
  • If files under website/ changed, run scripts/website-verify.sh --all and fix failures.
  • If local preview is available, open the changed pages via the VS Code preview server (http://127.0.0.1:3000/website/dist/) and use the browser/* tools to ensure the rendered page and browser console are sane.
  • Do quick link/navigation sanity checks on changed pages.
  • Do basic accessibility spot checks (headings, landmarks, labels, keyboard navigation where relevant).
  • Validate the authored source, not only the rendered output: when a shared layout, component, partial, _data module, or example directory changes, verify at least one representative page that consumes it.

Must Not

  • Do not hand off or claim completion without completing the checklist for the changed pages and any affected shared building blocks.

Golden Example

Checklist (per changed page):
- Shared docs: README/specification/architecture still match the implementation
- Content model: page entrypoints, _data modules, includes, and examples are updated in the correct source files
- Links: no broken relative links introduced
- Browser preview: verify layout, interaction, and console are clean

Actions

  1. Identify which authored sources changed under website/:
    • website/src/pages/ for page entrypoints
    • website/src/_data/ for structured page content and navigation
    • website/src/_includes/ for shared layouts, components, and partials
    • website/src/examples/ for interactive example fragments
    • website/src/styles/, website/src/style.css, and website/src/site-assets/ for shared presentation and behavior
  2. For each changed page, verify:
    • Alignment with website/README.md, website/specification.md, and website/architecture.md
    • Link/navigation sanity
    • Accessibility basics
  3. If a shared authored source changed, verify representative consuming pages in website/dist/.
  4. If issues are found, fix them or record them with a clear plan.

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