Skip to content

docs: document kits v3 and preserve v2 - #26065

Draft
dvdksn wants to merge 6 commits into
docker:mainfrom
dvdksn:codex/kits-v3-docs
Draft

docs: document kits v3 and preserve v2#26065
dvdksn wants to merge 6 commits into
docker:mainfrom
dvdksn:codex/kits-v3-docs

Conversation

@dvdksn

@dvdksn dvdksn commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Description

The kit documentation describes v2 runtime customization, while v3 introduces buildable workload and mixin images with typed runtime capabilities. Make v3 the primary documentation path and preserve the v2 guide, examples, and reference in a separate section without marking earlier formats deprecated.

  • Teach shared kit concepts in the v3 guide through an OpenCode workload with Ruff and team review instructions, then explain capabilities, lifecycle hooks, composition, and builds.
  • Replace the v1 agent tutorial with a step-by-step v3 Claude Code walkthrough, and add v3 examples for instructions, configuration, skills, hooks, and tool builds.
  • Document the v3 schema and verified sbx support limits, add a v2-to-v3 field mapping, and align navigation, positional workload-kit commands, and credential guidance.

Validated kit image builds, binary smoke checks, descriptor samples against the schema implementation, scoped Markdown and style lint, a full Hugo build, and internal links. Full authenticated sbx launches remain untested.

@netlify /ai/sandboxes/customize/kits/

Generated by Codex

The kit documentation described v2 runtime customizations and a v1 agent
walkthrough, without the v3 workload, build, or capability contracts.
Make v3 the primary guide, schema reference, and examples, retain the v2
pages in a separate section, and align navigation and credential guidance.

Co-authored-by: Codex <noreply@openai.com>
@netlify

netlify Bot commented Sep 11, 2026

Copy link
Copy Markdown

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 3d92c6d
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6aa4202c7c159000086c51c2
😎 Deploy Preview https://deploy-preview-26065--docsdocker.netlify.app/ai/sandboxes/customize/kits/
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Replace the outdated Mistral Vibe launch syntax and explain positional local, OCI, and Git workload references. Keep mixin usage distinct and point v2 examples at the matching documentation.
The draft introduced build requirements and schema mechanics before showing what a kit contains or how to run one.

Lead with source files and a runnable workload, explain capabilities through examples, and defer composition and build rules. Order mixin examples by complexity, develop the agent descriptor step by step, move migration guidance after the reference, and preserve the signing anchor used by the homepage.
The introductory shell workload gave readers little reason to use kits, while shared concepts remained in the preserved v2 guide.

Use OpenCode with Ruff and review instructions for the introductory workload. Bring use cases, agent guidance, settings, environment configuration, debugging, and a skill example into v3, and focus v2 pages on their schema and behavior.
The Run a kit section continued the OpenCode example and mixed basic usage with credentials, source formats, composition, and sandbox reuse.

Lead with general run syntax and group sources, mixins, and naming into dedicated subsections. Keep credential setup in the authentication section and remove agent-specific tutorial steps from usage guidance.
Several guide sections assumed readers had followed the OpenCode example, and individual recipes depended on an unlinked sample workload.

Lead topics with their concepts, link supporting examples and recipe prerequisites, and point reference readers to specific guide sections. Group registry publishing and Git sharing by task and keep launch syntax in the usage section.
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