菜单
Explain that blit386-demos has no automated tests and how to verify demos by hand instead. Use when the user asks to run, write, or find tests in this repo.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scaffold a new blit386-demos demo file with the correct next NNN slug, the standard demo class pattern, and beginner-friendly comments. Use when the user wants to add, create, or scaffold a new demo or example, or says 'make a demo for X' or 'add a demo that shows Y'.
Create a pull request with automatic quality checks, a conventional commit, and the gh CLI. Use when the user wants to open a PR or push a branch for review.
Comprehensive pre-push review combining automated checks, a security audit, AI code analysis, and a PR-ready summary. Use before pushing significant changes or opening a pull request.
Run all quality checks (format, lint, spellcheck, knip, docs:links, build) before committing or pushing. Use when the user wants to verify the code is ready to commit or run every check at once.
Review the current changes against project rules, conventions, and quality standards. Use when the user asks to review changes, check the diff before committing, or look over recent edits.
Run cspell across the project, fix typos, and add legitimate words to the dictionary. Use when the user wants to spellcheck, fix spelling, or resolve cspell failures.
| name | demos-test |
| description | Explain that blit386-demos has no automated tests and how to verify demos by hand instead. Use when the user asks to run, write, or find tests in this repo. |
There are no automated tests in blit386-demos. Do not look for pnpm run test, vitest, or a tests/ directory -
none of these exist here.
/demos-test
Demos are interactive, visual, and authored for a single developer. Correctness is verified by:
pnpm run dev) and opening the demo in a browserpnpm run build) – a build failure surfaces broken imports or plugin errorspnpm run preflight) – lint, format, spellcheck, knip, docs:linksAutomated unit or E2E tests would require a headless WebGPU runtime (not broadly available) and would largely duplicate
what the library's own test suite (blit386) already covers.
pnpm run dev, open /demos/<slug>.html, exercise the demo manuallypnpm run build/demos-preflight or /demos-review/demos-deep-review