القائمة
Run the automated test suites and explain what testing exists here. Use when the user wants to run tests or verify the scaffolder, the kit CLI, or the codemod engine still work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
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.
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.
Find and fix slow frames: stop making new objects every frame, batch sprites by sheet, skip what is off screen, and
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.
| name | cbt-test |
| description | Run the automated test suites and explain what testing exists here. Use when the user wants to run tests or verify the scaffolder, the kit CLI, or the codemod engine still work. |
This repo has three node --test suites, 37 cases in total. There is no Vitest suite, no Playwright suite, and no
top-level tests/ directory – each package owns its own test/ folder.
| Suite | Cases | Covers |
|---|---|---|
packages/create-blit386/test/scaffold.test.mjs | 20 | The scaffold path end to end (JS and TS), the non-TTY --yes fallback, optional CI and agent files, the .blit/ ownership manifest, blit agents sync (drift, full sync, --force, note and merge preservation), blit agents add (including collision safety), and blit migrate preview + --write |
packages/create-blit386/test/env.test.mjs | 4 | meetsNodeFloor: the Node version floor guard, including pre-release and custom-floor strings |
packages/kit/test/codemod.test.mjs | 13 | The migration registry and the anchored codemod engine behind blit migrate: auto-applied renames vs. names reported for review, receiver anchoring, idempotence, and registry field completeness |
pnpm run test at the root is pnpm -r test, which runs all three.
/cbt-test
packages/create-blit386/dist/index.js (the scaffold CLI itself) and packages/kit/dist/cli.js (used for the
agents sync / migrate checks). The kit package rebuilds itself through a pretest script; the scaffolder package
does not, so run pnpm run build first if either dist/ is missing or stale.Build if needed
Execute pnpm run build when dist/ is missing or stale.
Run the suites
Execute pnpm run test from the repository root. To run one package: pnpm --filter @blit386/kit test or
pnpm --filter create-blit386 test.
Report results
npm install or Vite build inside a generated project.agents sync cases are skipped when git is unavailable (they need a three-way merge).For full quality gates before commit, use /cbt-preflight instead.