一键在 Manus 中运行任何 Skill

fix

星标0

分支0

更新时间2026年7月2日 14:11

Diagnose and fix a BLIT386 game error using the local docs. Use this whenever the game crashes, shows a blank or black screen, throws an error in the browser console, freezes, or behaves unexpectedly, even if the user only says 'it is broken', 'nothing shows up', or 'why is this not working'.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

blit386

blit386/create-blit386

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Fix a runtime error

Diagnose and fix a BLIT386 game error using the local docs.

When to use

Use when the game crashes, shows a blank screen, throws an error in the browser console, or behaves unexpectedly.

Steps

Open docs/when-something-breaks.md first. It covers the most common beginner errors with concrete fixes.
On a blank screen: ensure BT.paletteSet(palette) was called in init() before any draw call.
If you see "Cannot read properties of undefined": you likely forgot await before sprite or font load calls.
Note: 0 is not a valid palette index – slot 0 is always transparent; use slot 1 or higher.
Check AGENTS.md for correct engine API usage – getters have no (), methods do.
Post-process effects require WebGPU – confirm BT.activeBackend is not 'software' (the Canvas 2D fallback does not run effects). Keep starters free of post-process effects.

What to check

update() is for logic only; render() is for drawing only. Drawing in update() causes visual glitches.
If key or button taps feel randomly missed: isKeyPressed/isKeyReleased/inputString/isPressed/isReleased must be read in update(). Reading them in render() can miss the one-frame edge; see docs/input.md.
All screen coordinates must be whole numbers (Vector2i, Rect2i). Fractions cause off-by-one pixel issues.
If you see {{ or }} in a file, a template placeholder was not substituted – this is a scaffolding bug, not a game bug.

同仓库更多 Skills

同仓库

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

cbt-kit-audit

blit386/create-blit386

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.

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

name	fix
description	Diagnose and fix a BLIT386 game error using the local docs. Use this whenever the game crashes, shows a blank or black screen, throws an error in the browser console, freezes, or behaves unexpectedly, even if the user only says 'it is broken', 'nothing shows up', or 'why is this not working'.

Fix a runtime error

Diagnose and fix a BLIT386 game error using the local docs.

When to use

Use when the game crashes, shows a blank screen, throws an error in the browser console, or behaves unexpectedly.

Steps

Open docs/when-something-breaks.md first. It covers the most common beginner errors with concrete fixes.
On a blank screen: ensure BT.paletteSet(palette) was called in init() before any draw call.
If you see "Cannot read properties of undefined": you likely forgot await before sprite or font load calls.
Note: 0 is not a valid palette index – slot 0 is always transparent; use slot 1 or higher.
Check AGENTS.md for correct engine API usage – getters have no (), methods do.
Post-process effects require WebGPU – confirm BT.activeBackend is not 'software' (the Canvas 2D fallback does not run effects). Keep starters free of post-process effects.

What to check

update() is for logic only; render() is for drawing only. Drawing in update() causes visual glitches.
If key or button taps feel randomly missed: isKeyPressed/isKeyReleased/inputString/isPressed/isReleased must be read in update(). Reading them in render() can miss the one-frame edge; see docs/input.md.
All screen coordinates must be whole numbers (Vector2i, Rect2i). Fractions cause off-by-one pixel issues.
If you see {{ or }} in a file, a template placeholder was not substituted – this is a scaffolding bug, not a game bug.