feat(#165): skills reference page + changelog link on the landing site#167
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #165. Two small landing-site additions:
site/skills.html— public, browseable index of every apexyard slash command. 39 entries today, grouped into 10 categories, each entry showing the command, its argument hint, and the description (taken verbatim fromSKILL.mdfrontmatter so the page matches the runtime). Same brutalist-terminal design as the homepage; no JS, no build step.skills→./skills.htmlchangelog →→https://github.com/me2resh/apexyard/releases(auto-resolves to the latest tagged release; v1.2.0 lands and the link's already pointing at it)Refs #160 (the release-and-site-refresh ticket) — this is the second site-side deliverable; the release tag follows once #159 (testing) closes.
Why now
With v1.2.0 about to ship, the framework's surface jumped to 39 skills + 24 hooks. The CLAUDE.md "Available skills" table covers them but lives behind a GitHub UI an adopter has to dig for. A standalone page on the landing site means an evaluator who lands on apexyard.dev can answer "what does this thing actually do?" in one click without leaving the marketing surface.
The CHANGELOG link is the cheap-but-meaningful piece — visitors hitting the site on launch day go straight to the release notes.
Implementation notes
SKILL.mdfrontmatter verbatim today, but it'll need updates when frontmatter changes. A small generator script (walk.claude/skills/*/SKILL.md, parse YAML, emit the section HTML) is the obvious follow-up; out of scope for v1.2.0.index.html's:root. Cheap to keep in sync; sharing a file would force a build step the static-only convention deliberately avoids. If a future page makes that trade-off worth revisiting, file a ticket.max-width: 720px; non-CTA titlebar items hide on narrow viewports (thehomelink stays via.always).Testing
nodescript:index.html102/102 divs, 22/22 anchors;skills.html2/2 divs, 23/23 anchors.<script>tags; index.html script count unchanged.SKILL.mdfrontmatter via a one-liner (awkoverdescription:/argument-hint:lines) and pasted verbatim.ls -d .claude/skills/*/ | wc -l= 39 ✓; skills.html has 39.skillblocks (38 active + 1 deprecated).#setup,#daily,#tickets,#specs,#review,#architecture,#audits,#workflow,#comms,#deprecated) has a matchingid=on its target.site/skills.htmlin a browser; verify category sections render correctly, anchor links scroll, mobile-viewport collapses to single-column, dark-mode preference toggles the colour scheme. Opensite/index.htmland verify the newskillsandchangeloglinks appear in the nav and route correctly.Glossary
/<name>. Each is backed by.claude/skills/<name>/SKILL.md. The skills page enumerates the full surface in one place.github.com/me2resh/apexyard/releases(the releases index), not a specific tag. Each release publishes its own page; visitors clicking the link see whatever's most recent. No need to update the link on each release cut.🤖 Generated with Claude Code