From f28f43cef0f7434d55f656a89e71b7f6605c4bee Mon Sep 17 00:00:00 2001 From: Enrico Piovesan Date: Thu, 30 Jul 2026 10:28:42 -0600 Subject: [PATCH] docs: promote the live Registry Catalog site-wide Adds https://registry.traverse-framework.com to the Developers nav dropdown and mobile menu, and mentions it on /agents.html as the way to browse published capabilities before authoring something new. Also fixes a stale wasm32-wasip1 reference in that same paragraph, left over from before the ABI-compliant build pattern was verified. Co-Authored-By: Claude Sonnet 5 --- src/components/Nav.astro | 8 ++++++++ src/pages/agents.astro | 3 ++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/src/components/Nav.astro b/src/components/Nav.astro index 23ac6ad..f69dcea 100644 --- a/src/components/Nav.astro +++ b/src/components/Nav.astro @@ -119,6 +119,13 @@ const { currentPath = '' } = Astro.props; 6 real, runnable domains + + ⬡ + + Registry Catalog + Browse every published capability + + ⬡ @@ -166,6 +173,7 @@ const { currentPath = '' } = Astro.props; Docs All Questions Examples + Registry Catalog → Compare Security Audit Blog diff --git a/src/pages/agents.astro b/src/pages/agents.astro index 09bb64d..8db412b 100644 --- a/src/pages/agents.astro +++ b/src/pages/agents.astro @@ -88,7 +88,8 @@ const _body = `
Building with a coding agent

A Claude Skill that checks the registry before it writes anything.

-

traverse-framework/claude-skills hosts Claude Skills for building apps with Traverse — starting with traverse-app-builder, which checks the registry for a capability that already fits, authors a new one as a real JSON-Schema contract only when nothing does, compiles it to wasm32-wasip1, composes several into a multi-node workflow, and validates all of it against the real traverse-cli. It also states this platform's current execution limitations plainly, since a skill that overclaims what Traverse can run today is worse than no skill at all.

+

traverse-framework/claude-skills hosts Claude Skills for building apps with Traverse — starting with traverse-app-builder, which checks the registry for a capability that already fits, authors a new one as a real JSON-Schema contract only when nothing does, compiles it to genuinely executable, ABI-compliant WASM, composes several into a multi-node workflow, and validates and runs all of it against the real traverse-cli. It also states this platform's current limitations plainly, since a skill that overclaims what Traverse can run today is worse than no skill at all.

+

Before authoring anything new, check the Registry Catalog — every published capability, browsable with real coverage and use-case data, not just a raw JSON index.

See the skill →