Menu
Use for backend bug fixes, cleanup, extraction, or moving code between layers while preserving behavior and architecture boundaries.
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.
Based on SOC occupation classification
Use when adding or changing backend HTTP API handlers, REST controllers, request/response DTOs, Joi schemes, or OpenAPI REST contract entries.
Use when changing Redis or cache behavior.
Use when changing backend game, package, validation, or service rules.
Use when changing backend timers, scheduled work, Redis expiration handlers, pub/sub listeners, cleanup work, or lifecycle notifications.
Use when adding or changing server Socket.IO game events, GameActionType handlers, action use cases, socket payloads, GameActionExecutor flows, or public socket contracts. Do not use for REST-only endpoint changes.
Use when changing docs, skills, AGENTS files, specs, ADRs, source-of-truth routing, or when code changes make existing docs stale.
| name | backend-maintenance |
| description | Use for backend bug fixes, cleanup, extraction, or moving code between layers while preserving behavior and architecture boundaries. |
Use this skill when the task is a backend bug fix, cleanup, extraction, or refactor rather than a new public feature.
server/AGENTS.mddocs/agent/04-docs-drift-policy.md if docs become staledocs/agent/03-verification-matrix.mdBefore editing, classify the task:
refactor_only — behavior must remain identical.bug_fix — behavior changes only for broken or edge cases.cleanup — readability/structure improves without behavior change.extraction — logic moves to a better owner.If the category changes during work, update the handoff summary.
domain/, orchestration to application/, transport code to presentation/.From server/:
npm run lint
npm run build
Run focused tests for touched behavior. If no test exists and the change is risky, add one or document why not.
Report work category, behavior expected to change or not change, layer ownership changes, tests/checks run or skipped, and docs updated or why not needed.