Skip to content

chore: agent tooling (rtk, codebase-memory, skills) + public roadmap page - #74

Merged
Andersseen merged 2 commits into
mainfrom
chore/agent-tooling-rtk-memory-skills
Aug 7, 2026
Merged

chore: agent tooling (rtk, codebase-memory, skills) + public roadmap page#74
Andersseen merged 2 commits into
mainfrom
chore/agent-tooling-rtk-memory-skills

Conversation

@Andersseen

@Andersseen Andersseen commented Aug 7, 2026

Copy link
Copy Markdown
Owner

Two commits: agent tooling, then the first user-facing docs page.


1. Agent tooling (c72b727)

No library or docs-app code. Nothing here runs in CI or ships to consumers.

RTK (Rust Token Killer)

RTK is a CLI proxy that filters verbose command output before it reaches the context window.

Committed .rtk/filters.toml with the two filters RTK has no built-in for: the ng-packagr library build (pnpm build:lib) and the manifest / AI-docs generators. Each carries inline tests — rtk verify goes 154/154 → 158/158, which is how the schema was validated rather than trusted from docs.

Deliberately not committed: the PreToolUse hook. RTK only installs it globally (rtk init -g~/.claude/settings.json), and a repo-level hook referencing a binary most contributors don't have would error on every Bash call. It stays opt-in per machine; without rtk installed nothing changes and nothing breaks.

CLAUDE.md also warns against a bare rtk init — local mode injects a large instruction block straight into CLAUDE.md, which this repo keeps curated.

codebase-memory MCP

Added via npx -y codebase-memory-mcp, matching how playwright and chrome-devtools are already wired, so no local install is needed. Handshake verified against v0.9.0 (initialize → ok, tools capability).

Its index is not automatic (autoindex.skip reason=disabled), so the docs say to run index_repository once per clone. The graph lives in ~/.cache/codebase-memory-mcp/, outside the repo; .codebase-memory/ is gitignored.

Skills

Skill Why
/release-check [--fix] Audits local versions vs npm vs GitHub Releases vs Actions runs vs the Cloudflare deploy, and repairs with --fix
/verify-ui <name> Makes the existing CLAUDE.md browser-verification playbook repeatable
/theme-audit <name> Sweeps a component across the 5 × 5 presets plus dark mode

/release-check is written from a real incident. On 2026-08-06 GitHub dropped the push events for #72 and #73: main was green and said 1.0.0, while npm still served 0.9.0 and nothing had deployed. Both workflows already declare workflow_dispatch, so the recovery was a dispatch. That release has since been dispatched and completed@voltui/components@1.0.0 and @voltui/cli@1.0.0 are on npm, both GitHub Releases exist, and the docs app is deployed.


2. Public roadmap page (ebc0ab9)

Adds /docs/roadmap, so a visitor can see where the project is going — 1.0 as a starting line, not an abandoned finish.

Four items, ordered by dependency rather than by date:

  1. Docs in Ukrainian and Spanish — docs site only; component names, selectors, inputs and outputs stay English, since translating an API would break every copied component
  2. A first-party headless layer under @volt-ui/core — replaces ng-primitives, shipped separately from the styled components so a consumer can take headless alone
  3. Two distributions — with Tailwind and without
  4. More layouts — composed from existing Volt UI components, honestly labelled as the least critical item

The page has no dates on purpose, and says so: the ordering is the commitment. It also explains why the headless port comes before growing the catalog — every component added first is one more to port later.

@volt-ui/core is the name already reserved for this in specs/SPEC.md §7, so the page states existing intent rather than inventing a package.

Accessibility

Rendered as an <ol>, because the sequence is the substance and it has to reach screen readers — the numbered badges are decoration (aria-hidden). Status and scope chips carry sr-only labels (Status:, Applies to:), otherwise "Next" and "Library" read as floating text.

Linked from the Getting Started sidebar and cross-linked from Versioning & Stability.


Verification

  • rtk verify — 158/158, including the 4 new inline filter tests
  • npx -y codebase-memory-mcp — MCP initialize handshake returns ok
  • pnpm test:run299/299 across 57 files
  • pnpm typecheck, pnpm lint — clean
  • Roadmap page driven in a real browser: a11y tree verified as a semantic list, zero console errors, and rendered under volt/sharp light, dusk/ghost dark, and ember/brutal light
  • pnpm format:check — the 10 remaining warnings are pre-existing on main (scripts/*.mjs, public/web-editor-lite.min.js) and left untouched as out of scope

🤖 Generated with Claude Code

Andersseen and others added 2 commits August 7, 2026 07:43
Agent tooling only — no library or docs-app code changes.

RTK (Rust Token Killer): commit .rtk/filters.toml with the two filters RTK
has no built-in for — the ng-packagr library build and the manifest/AI-docs
generators — each with inline tests (`rtk verify`: 158/158). The PreToolUse
hook stays opt-in per machine (`rtk init -g`) rather than committed, so a
contributor without rtk installed is unaffected. A bare `rtk init` is called
out as unsafe here: local mode injects a large block into the curated CLAUDE.md.

codebase-memory: add the MCP server via `npx -y codebase-memory-mcp`, matching
how playwright and chrome-devtools are already wired, so no local install is
needed. Handshake verified against v0.9.0. Its index is not automatic, so the
docs say to run index_repository once per clone; the graph lives outside the
repo in ~/.cache, and .codebase-memory/ is gitignored.

Skills:
- /release-check — audits local versions vs npm vs Releases vs Actions vs the
  deploy, and repairs with --fix. Written from the 2026-08-06 incident, where
  GitHub dropped the push events for #72 and #73: main was green and tagged
  1.0.0 while npm still served 0.9.0 and nothing had deployed.
- /verify-ui — makes the CLAUDE.md browser-verification playbook repeatable.
- /theme-audit — sweeps a component across the 5x5 presets plus dark mode.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Adds /docs/roadmap so readers can see where the project is going and that
1.0 is a starting line, not an abandoned finish.

Four items, ordered by dependency rather than by date:

1. Docs in Ukrainian and Spanish (docs site; component APIs stay English)
2. A first-party headless layer under @volt-ui/core, replacing ng-primitives,
   shipped separately from the styled components so a consumer can take
   headless alone
3. Two distributions, with Tailwind and without
4. More layouts composed from existing Volt UI components

Deliberately no dates — the ordering is the commitment. The page also
explains why the headless port comes before growing the catalog: every
component added first is one more to port later.

@volt-ui/core is the name already reserved for this in specs/SPEC.md §7, so
the page states existing intent rather than inventing a new package.

Rendered as an <ol>, since the sequence is the substance and the numbered
badges are decoration (aria-hidden); status and scope chips carry sr-only
labels. Linked from the sidebar and cross-linked from Versioning & Stability.

Verified in a real browser: a11y tree checked, zero console errors, and
rendered under volt/sharp light, dusk/ghost dark, and ember/brutal light.
299/299 unit tests, typecheck and lint clean.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Andersseen Andersseen changed the title chore: add rtk filters, codebase-memory MCP, and three repo skills chore: agent tooling (rtk, codebase-memory, skills) + public roadmap page Aug 7, 2026
@Andersseen
Andersseen merged commit f794e2e into main Aug 7, 2026
2 checks passed
@Andersseen
Andersseen deleted the chore/agent-tooling-rtk-memory-skills branch August 7, 2026 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant