菜单
Use at the start of any session to understand which skill to invoke. Maps the full workflow — feature development, bug fixing, architecture, and utilities — for a C++ game server project with SVN.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Aquarius-mu/gameserver-agent-skills --skill guide命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Find deepening opportunities in the codebase — refactors that reduce coupling, simplify interfaces, and improve AI-navigability. Use when improving architecture, finding refactoring opportunities, or making a codebase easier to work with.
Use before any feature work — explores intent, asks clarifying questions one at a time, produces a design doc. Invoke before writing any code or plan.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "less tokens", or invokes /caveman.
基于 SOC 职业分类
正在显示 SKILL.md
| name | guide |
| description | Use at the start of any session to understand which skill to invoke. Maps the full workflow — feature development, bug fixing, architecture, and utilities — for a C++ game server project with SVN. |
This package provides a complete agent workflow for C++ game server development.
Invoke the relevant skill BEFORE any response or action. Even a 1% chance a skill might apply means you should invoke it. Skills tell you HOW to approach work; don't skip them.
idea → /brainstorm → /to-prd → /plan → /to-issues → /implement loop → svn commit
/brainstorm — Explore intent, ask clarifying questions, produce a design spec/to-prd — Turn the design into a formal PRD and publish to the issue tracker/plan — Break the PRD into a step-by-step implementation plan/to-issues — Slice the plan into independently-grabbable SVN-ready issues/implement — Execute: implement slice → ./qmake.sh → /review → svn commitbug report → /debug → implement fix → /review → svn commit
/debug — Build a feedback loop, reproduce, hypothesise, fix/implement — Apply the fix with the implement→build→review loop/review — Code review before committing/zoom-out → /architect → /plan → /implement loop
/zoom-out — Get a map of relevant modules and callers/architect — Find deepening opportunities, reduce coupling/plan + /implement — Execute the refactor/prototype → capture decision → /plan → /implement
| Skill | When to use |
|---|---|
/brainstorm | Before any feature work — explore requirements, produce a design doc |
/to-prd | Turn conversation context into a formal PRD on the issue tracker |
/plan | Before touching code — write a step-by-step implementation plan |
/to-issues | Break a plan into independently-grabbable issues |
/implement | Execute: implement → build → review → commit (repeat per slice) |
/review | Code review before any SVN commit |
/debug | Disciplined bug diagnosis with feedback loop |
/architect | Find and fix architectural friction in the codebase |
/zoom-out | Get a broader map of modules and callers in an unfamiliar area |
/prototype | Build throwaway C++ code to answer a design question |
/grill | Interview the user or design relentlessly until shared understanding |
/triage | Move issues through the triage state machine |
/handoff | Compact the session into a document for the next agent to pick up |
/caveman | Ultra-compressed output mode (~75% fewer tokens) |
./qmake.sh (Unity Build + distcc)cpgame <server_id>svn commit -m "...", all history via svn log.sdp files in Common/ (CS/SC) and Inter/ (server-to-server)No code is committed without passing: ./qmake.sh compiles clean → /review subagent approves → svn commit.