القائمة
Use when adding a new ECS component, MCP command, or engine capability. Checklist of all files that must be updated across Rust engine, web layer, and integration points.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Check changelogs for Bevy, Next.js, Zustand, wasm-bindgen, Rapier, and all SpawnForge deps. Use when training data may be stale, before major upgrades, or when a library API behaves unexpectedly.
Forward-looking sister to changelog-review. Scans our SaaS + library stack (analytics, monitoring, observability, agent tracking, infrastructure, AI, payments, auth) against TODAY's provider changelogs / releases / betas to surface capabilities we are NOT yet using — newly shipped or long-available-but-unadopted — that could improve the product or our build harness. Every opportunity comes with its provider cost. Use for quarterly capability audits, when asking "what new features can we leverage," or before planning a growth/observability/infra initiative.
SpawnForge Stripe webhook patterns — idempotent refunds, CTE atomic claims, neonSql transaction ordering, token billing. Auto-loads when editing billing code.
Monitor open PRs for CI failures and review comments, then fix issues automatically. Use when PRs need to be driven to green — checks CI status, Sentry comments, merge conflicts, and applies fixes.
Review a PR for SpawnForge bugs, security issues, and regressions. Posts inline GitHub comments with severity markers. Use when asked to "review PR", "code review", or "check this PR". Invoke with /pr-code-review <PR number>.
Taskboard management skill. View, create, update, and manage tickets on the project taskboard. Enforces standard ticket format with user stories and acceptance criteria.
| name | component-checklist |
| description | Use when adding a new ECS component, MCP command, or engine capability. Checklist of all files that must be updated across Rust engine, web layer, and integration points. |
When adding a new ECS component, update these domain-scoped files:
engine/src/core/<component>.rs — Component struct + marker (add pub mod in core/mod.rs)engine/src/core/pending/<domain>.rs — Request structs + queue methods + bridge fnsengine/src/core/commands/<domain>.rs — Dispatch entry + handler functionengine/src/bridge/<domain>.rs — Apply system + selection emit (register in bridge/mod.rs SelectionPlugin::build())engine/src/core/history.rs — UndoableAction variant + EntitySnapshot fieldengine/src/core/entity_factory.rs — delete/duplicate/undo/redo + spawn_from_snapshotengine/src/core/engine_mode.rs — snapshot_scene (separate query param)engine/src/bridge/events.rs — Emit function(s)engine/src/bridge/query.rs — Query handler (if component has query support)web/src/stores/slices/<domain>Slice.ts — State + actions (+ re-export from slices/index.ts)web/src/hooks/events/<domain>Events.ts — Event handler(s)web/src/lib/chat/handlers/<domain>Handlers.ts — Tool call handler(s) (registered in executor.ts handler registry)web/src/components/editor/<Inspector>.tsx — Inspector panelweb/src/components/editor/InspectorPanel.tsx — Import + renderweb/src/components/chat/ToolCallCard.tsx — Display labelsmcp-server/manifest/commands.json — MCP commands. Set visibility: 'public' or 'internal' (mandatory)web/src/data/commands.json — COPY of #16 (keep in sync)TESTING.md — Manual test cases