bestagentkits

Ak Render — Testing skill for Claude Code

Testing community

Declarative interactive HTML renderer and Page Spec runtime for AgentKit.

How to install Ak Render

This entry records only its repository, not the path inside it, so there is no exact command to give. Open bestagentkits/ak-render and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Ak Render does

Declarative interactive HTML renderer and Page Spec runtime for AgentKit.

Alternatives in Testing

README

@bestagentkits/render

Declarative page compiler for AgentKit: a constrained JSON/YAML **Page Spec** in, a deterministic, self-contained, interactive **standalone HTML** out.

Agents describe meaning and composition. The compiler owns HTML, CSS, interaction, accessibility, responsive layout, theming, asset bundling, security policy, and byte-for-byte determinism.

npx @bestagentkits/render page.yaml --out page.html

The emitted file opens directly from disk (`file://`) and makes zero network requests by default. The local compiler is canonical: no account, no network, no server.

**Status:** pre-1.0, in active construction. This repository is being built in milestones. The package skeleton, ADR, CI, and fixture corpus exist; the schema, compiler, themes, runtime, catalog, and cloud service land in the milestones described in [docs/adr/0001-page-spec-compiler-boundary.md](./docs/adr/0001-page-spec-compiler-boundary.md) and the [changelog](./CHANGELOG.md). Nothing below is advertised as available before it exists.

Why

AgentKit's HTML-producing skills each carried the presentation layer in model context: layout, CSS, JavaScript, charts, responsive rules, theming, and verification. That costs tokens, adds latency, invites retries after HTML/CSS/JS mistakes, and lets skills drift against each other.

`ak:diagram` already proved the alternative for diagrams: typed IR, deterministic compiler, trusted fragment boundary. AK Render applies the same pattern to whole pages.

Design in one screen

Page Spec (JSON/YAML, authored by a model)
   |  parse -> validate -> normalize
   v
internal IR (flat nodes, stable content-derived IDs)
   |  resolve registry -> resolve theme -> render
   v
single self-contained HTML document
   |  collect used assets/runtime features -> assemble -> verify
   v
deterministic artifact (opens from file://, zero network by default)

Six decisions define the boundary, argued in [ADR 0001](./docs/adr/0001-pag