Run any Skill in Manus with one click

cbt-kit-audit

Stars0

Forks0

UpdatedJuly 14, 2026 at 05:29

Re-audit the shipped kit docs and game-author skills against the current blit386 engine API and fix stale examples. Use after adding or renaming engine public API, or when you want to check that kit content has not drifted.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

blit386

blit386/create-blit386

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	cbt-kit-audit
description	Re-audit the shipped kit docs and game-author skills against the current blit386 engine API and fix stale examples. Use after adding or renaming engine public API, or when you want to check that kit content has not drifted.

Kit content audit

Nothing syncs this repo from blit386 automatically. The kit docs and shipped skills are hand-authored beginner prose, so they drift silently when the engine changes. This skill walks the staleness checklist and fixes what is out of date.

Usage

/cbt-kit-audit

Steps

Establish what changed in the engine

If a specific engine change prompted this (a new feature, a renamed BT.* member, a getter-vs-method change, new or removed constants), note it. Otherwise audit broadly. The sibling engine repo is ../blit386; its public surface is ../blit386/src/BLIT386.ts, ../blit386/CLAUDE.md (BT API getters vs methods, Boolean naming), and ../blit386/docs/api-*.md. Read those for the current truth – never from memory.
Audit the kit docs

List the docs first – a list written down here is exactly how this audit goes stale, and it did: it still named six docs long after audio.md shipped.
```
ls packages/kit/content/docs/
```
Check every code example and API mention in each one against the current engine. For what each doc leans on, use the "Kit file / Review when" table in CLAUDE.md – that table is maintained, so read it rather than copying it here.
Audit the shipped skills

Same rule: enumerate them, do not trust a list.
```
ls -d packages/kit/content/skills/*/
```
The skills demonstrate engine APIs the same way the docs do. Check each one whose topic touches the changed surface, confirming method-vs-getter usage, BT names, and constants against the engine.

While you are here, confirm every skill directory appears in the skills table in packages/kit/README.md – that is the only human-facing list of what ships, and it has no automated guard.
Check the version pin

If new games should pin a newer engine, update BLIT386_RANGE in packages/create-blit386/src/scaffold.ts (and engineRange in the kit if present).
Keep kit content self-contained

Shipped content may reference only blit386 (the engine) and other local kit files. Do not introduce references to the blit386-demos repo (demo slugs or demos.blit386.dev URLs).
Fix and verify

Apply fixes in place, then run pnpm run preflight. Report which files changed and why.

More from this repository

same repository

cbt-release

blit386/create-blit386

Publish @blit386/kit and create-blit386 to npm following the workspace PUBLISHING.md procedure. Publishing is manual-only (pnpm publish from vancura's machine) -- there is no CI publish workflow. Does not bump versions unless the user asks.

2026-07-140

add-crt-effect

blit386/create-blit386

Stack fullscreen post-process effects (CRT curvature, scanlines, bloom, glitch) on top of the finished frame, which runs on WebGPU only. Use for a retro CRT look, screen glitches, bloom or glow, or any whole-screen filter.

2026-07-140

design-a-sound

blit386/create-blit386

Build a custom sound from scratch with AudioClip.synth and the synth knobs (waveform, envelope, pitch sweep, vibrato, noise, duty cycle) when the six ready-made presets are not what you want. Use when the user wants their own sound effect, wants to tweak or tune a preset, says a sound is too long, too high, too harsh, or too boring, or asks how to make a sound without a sound file.

2026-07-140

keep-it-fast

blit386/create-blit386

Find and fix slow frames: stop making new objects every frame, batch sprites by sheet, skip what is off screen, and

2026-07-140

play-a-sound

blit386/create-blit386

Play sound effects and background music, make retro sounds from nothing with the built-in synth presets, and set the volume of each bus. Use when the user wants a jump, pickup, explosion, laser, hit, or blip sound, wants music, asks about volume or muting, or asks why the game is silent.

2026-07-140

share-the-game

blit386/create-blit386

Build the finished game into a folder of plain files and put it online so other people can play. Use when the user wants to publish, deploy, or host the game, send a playable link to a friend, or asks 'how do I share my game', 'put my game on the internet', or 'make a real version people can play'.

2026-07-140

name	cbt-kit-audit
description	Re-audit the shipped kit docs and game-author skills against the current blit386 engine API and fix stale examples. Use after adding or renaming engine public API, or when you want to check that kit content has not drifted.

Kit content audit

Usage

/cbt-kit-audit

Steps

Establish what changed in the engine

If a specific engine change prompted this (a new feature, a renamed BT.* member, a getter-vs-method change, new or removed constants), note it. Otherwise audit broadly. The sibling engine repo is ../blit386; its public surface is ../blit386/src/BLIT386.ts, ../blit386/CLAUDE.md (BT API getters vs methods, Boolean naming), and ../blit386/docs/api-*.md. Read those for the current truth – never from memory.
Audit the kit docs

List the docs first – a list written down here is exactly how this audit goes stale, and it did: it still named six docs long after audio.md shipped.
```
ls packages/kit/content/docs/
```
Check every code example and API mention in each one against the current engine. For what each doc leans on, use the "Kit file / Review when" table in CLAUDE.md – that table is maintained, so read it rather than copying it here.
Audit the shipped skills

Same rule: enumerate them, do not trust a list.
```
ls -d packages/kit/content/skills/*/
```
The skills demonstrate engine APIs the same way the docs do. Check each one whose topic touches the changed surface, confirming method-vs-getter usage, BT names, and constants against the engine.

While you are here, confirm every skill directory appears in the skills table in packages/kit/README.md – that is the only human-facing list of what ships, and it has no automated guard.
Check the version pin

If new games should pin a newer engine, update BLIT386_RANGE in packages/create-blit386/src/scaffold.ts (and engineRange in the kit if present).
Keep kit content self-contained

Shipped content may reference only blit386 (the engine) and other local kit files. Do not introduce references to the blit386-demos repo (demo slugs or demos.blit386.dev URLs).
Fix and verify

Apply fixes in place, then run pnpm run preflight. Report which files changed and why.