Skip to content

feat(#165): skills reference page + changelog link on the landing site#167

Merged
atlas-apex merged 1 commit into
devfrom
feature/GH-165-skills-page-and-changelog-link
May 4, 2026
Merged

feat(#165): skills reference page + changelog link on the landing site#167
atlas-apex merged 1 commit into
devfrom
feature/GH-165-skills-page-and-changelog-link

Conversation

@atlas-apex

Copy link
Copy Markdown
Collaborator

Summary

Closes #165. Two small landing-site additions:

  1. 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 from SKILL.md frontmatter so the page matches the runtime). Same brutalist-terminal design as the homepage; no JS, no build step.
  2. Homepage nav — two new links in the titlebar:
    • skills./skills.html
    • changelog →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

  • Skills page is hand-curated — the descriptions match SKILL.md frontmatter 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.
  • Inlined CSS in skills.html — duplicates ~18 design tokens from 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.
  • Mobile-responsive — the skill grid collapses to single-column at max-width: 720px; non-CTA titlebar items hide on narrow viewports (the home link stays via .always).
  • Reduced-motion friendly — no animation; nothing to gate.

Testing

  • HTML balancenode script: index.html 102/102 divs, 22/22 anchors; skills.html 2/2 divs, 23/23 anchors.
  • No JS introduced — skills.html has no <script> tags; index.html script count unchanged.
  • Frontmatter sync — descriptions and argument hints in skills.html were extracted from SKILL.md frontmatter via a one-liner (awk over description: / argument-hint: lines) and pasted verbatim.
  • Skill count matches realityls -d .claude/skills/*/ | wc -l = 39 ✓; skills.html has 39 .skill blocks (38 active + 1 deprecated).
  • Anchor TOC links — every section anchor (#setup, #daily, #tickets, #specs, #review, #architecture, #audits, #workflow, #comms, #deprecated) has a matching id= on its target.
  • Visual + behaviour smoke (manual) — open site/skills.html in a browser; verify category sections render correctly, anchor links scroll, mobile-viewport collapses to single-column, dark-mode preference toggles the colour scheme. Open site/index.html and verify the new skills and changelog links appear in the nav and route correctly.

Glossary

Term Definition
Slash command surface The set of skills exposed to a Claude Code session as /<name>. Each is backed by .claude/skills/<name>/SKILL.md. The skills page enumerates the full surface in one place.
Hand-curated vs generated This page's content is hand-typed, mirroring SKILL.md frontmatter. A future generator can walk the skills dir and emit the HTML automatically; that's a follow-up.
Categorisation Loose grouping of skills by intent — Setup, Daily ops, Tickets, etc. — not a runtime classification. The framework doesn't enforce these categories anywhere; they exist only to make the page scan.
Self-resolving changelog link The nav link points at 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

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants