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
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
For each changed page, verify:
Alignment with website/README.md, website/specification.md, and website/architecture.md
Link/navigation sanity
Accessibility basics
If a shared authored source changed, verify representative consuming pages in website/dist/.
If issues are found, fix them or record them with a clear plan.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: website-quality-check3description: Run a lightweight, repeatable quality checklist for the website (including style guide adherence). Use when this capability is needed.4---56# Skill Instructions78## Purpose9Provide a lightweight, repeatable quality checklist for website changes in the Eleventy site under `website/`.1011## Hard Rules12### Must13- [ ] Verify the change follows `website/README.md`, `website/specification.md`, and `website/architecture.md`.14- [ ] If the change touches examples or authoring structure, read the relevant website ADRs before finalizing the change.15- [ ] If files under `website/` changed, run `scripts/website-verify.sh --all` and fix failures.16- [ ] 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.17- [ ] Do quick link/navigation sanity checks on changed pages.18- [ ] Do basic accessibility spot checks (headings, landmarks, labels, keyboard navigation where relevant).19- [ ] 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.2021### Must Not22- [ ] Do not hand off or claim completion without completing the checklist for the changed pages and any affected shared building blocks.2324## Golden Example2526```text27Checklist (per changed page):28- Shared docs: README/specification/architecture still match the implementation29- Content model: page entrypoints, _data modules, includes, and examples are updated in the correct source files30- Links: no broken relative links introduced31- Browser preview: verify layout, interaction, and console are clean32```3334## Actions351. Identify which authored sources changed under `website/`:36 - `website/src/pages/` for page entrypoints37 - `website/src/_data/` for structured page content and navigation38 - `website/src/_includes/` for shared layouts, components, and partials39 - `website/src/examples/` for interactive example fragments40 - `website/src/styles/`, `website/src/style.css`, and `website/src/site-assets/` for shared presentation and behavior412. For each changed page, verify:42 - Alignment with `website/README.md`, `website/specification.md`, and `website/architecture.md`43 - Link/navigation sanity44 - Accessibility basics453. If a shared authored source changed, verify representative consuming pages in `website/dist/`.464. If issues are found, fix them or record them with a clear plan.4748---49> Converted and distributed by [TomeVault](https://tomevault.io/claim/oocx) — claim your Tome and manage your conversions.50<!-- tomevault:4.0:skill_md:2026-04-11 -->
Run npx skillmds@latest add tomevault-io/website-quality-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Run a lightweight, repeatable quality checklist for the website (including style guide adherence). Use when this capability is needed. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io