Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

Added

• Docs site: each deploy tells search engines that support IndexNow (Bing, Yandex and others) which pages changed, so they recrawl them sooner. Only the deploy build submits, and only pages whose HTML changed since the last deploy (the first deploy submits all). The key is served once for every site at https://jeffallan.github.io/17c975f34bbe97c32cf68c4f58503478.txt
• Docs site: the build fails on a broken internal link (starlight-links-validator)
• CI: docs-site.yml lints and builds the docs site on every pull request and push to main, so a broken link or lint error shows up in review instead of at release. The workflow is shared with the other docs sites and kept in step from the same private repo as the site code
• Docs site: every page has a 1200×630 preview image (og:image) for links shared on social sites: the site’s name beside the monogram, the page title, and the page description cut to the whole sentences that fit in 260 characters. The cards are generated at build time (site/src/pages/og/) with astro-og-canvas
• Docs site: every page carries a JSON-LD graph naming its author. Skill and doc pages are a TechArticle and the home page a WebPage about the repo (SoftwareSourceCode), each pointing at one Person (https://jeffallan.github.io/#person) declared on the author’s site. It is added through Starlight’s route middleware (site/src/routeData.ts), so Starlight’s own title, description and Open Graph tags stay as they are
• Docs site: the shared light and dark theme (site/src/components/site-style/), delivered from a private repo that keeps the docs sites in step: the teal palette and fonts (Outfit, Source Sans 3) from the author’s site, a teal-based dark theme, and the monogram before the title, linking to that site. The purple palette is retired (#285)
• Docs site: a shared footer (About the Author and Contact, the docs sites, profile links, credit line, copyright, privacy link) and a Contact call to action that opens the contact form in a dialog: under the home page’s buttons, and before the first heading on skill, workflow, guide, Getting Started and Skills Guide pages. README, Changelog, Contributing, Roadmap and Privacy have none. The privacy page lists Formspree (#285)
• Docs site: the header has a Sites menu linking the author’s site and both docs sites, with the current one marked. The menu (site/src/components/site-nav/) is shared code from the same private repo, delivered with Copier (.copier-answers.yml), and handbook-update.yml opens a PR when it changes (#283)
• CI: skill-linter runs as a report-only job, configured in pyproject.toml, and make skill-lint runs it locally. It will replace validate-skills.py, validate-markdown.py and update-docs.py once its current findings are fixed (#279)

Changed

• Docs site: skill page titles lead with the skill’s name, as “Game Developer Agent Skill for Claude Code | Claude Skills” (was “Agent Skills for Claude Code | Game Developer | Claude Skills”), so search results show what the page is about first
• Dependabot skips the workflows the handbook delivers (handbook-update.yml, docs-site.yml, docs-deploy.yml); the handbook bumps their actions and sends them with each release
• The shared site packages (Astro, Starlight and the others listed in CLAUDE.md) take their versions from the handbook, which sends them with each release. handbook-update.yml sets up Node and runs copier update --trust for that step
• CI: skill-linter is the blocking check. The Validate job runs skill-linter release and skill-linter stamp --check, and make validate runs the same two. scripts/validate-skills.py, validate-markdown.py and update-docs.py are removed, and make skill-lint with them. CLAUDE.md and CONTRIBUTING.md describe the skill-linter commands, which make a missing “Use when” clause or Reference Guide an error (closing #288)
• Plugin: plugin.json lists the ten commands in an object map instead of scanning ./commands/, which Claude Code documents for flat command files only. The commands keep their names, including project:<phase>:<command> for the nested ones. The marketplace entry no longer lists commands (skill-linter P12)
• CONTRIBUTING.md and CLAUDE.md describe what the validator enforces: the description formula from CLAUDE.md, the section order, a five-step Core Workflow, the Reference Guide table, the Documentation backlink as the last line, and reference files without the old > Reference for: header (#277, closing #273)
• Plugin and marketplace descriptions: the language, backend and frontend counts are stamped by skill-linter, which corrected them to 8 backend frameworks and 7 frontend/mobile (they said 10 and 6) (#303)
• QUICKSTART: the language, backend and frontend counts are stamped by skill-linter (SKILL_COUNT:<domain> markers), so stamp --check reports a stale count (#302)
• Docs site: deploys on every push to main (docs-deploy.yml, shared with the other docs sites) instead of with each release, so site changes go live without a plugin release. release.yml now only creates the GitHub release
• Docs site: the content sync is shared code, delivered from a private repo that keeps the docs sites in step (site/src/components/site-sync/). site/scripts/sync-content.mjs keeps only this site’s settings, and the skills folder, domains, docs URL and credit come from the skill-linter settings in pyproject.toml ([tool.skill-linter]). llms.txt is now written by astro-seo-graph’s seoGraph(), and lists llms-full.txt under Optional (#295)
• Docs site: skill page meta descriptions are the skill’s description as written, without the “Claude Skills |