菜单
A relentless interview to sharpen a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this when the user wants to brainstorm a feature, explore requirements, compare design directions, clarify scope before implementation, or write a design/spec before coding. Trigger on: brainstorm, design, spec, requirements, options, trade-offs, before coding, before implementation. Do NOT trigger on direct requests to build/code/fix/modify behavior immediately, or on implementation of an already approved spec/plan.
Validates an existing game project PRD or GDD for production readiness. Runs a comprehensive 10-step review covering information density, clarity & ambiguity, traceability, implementation leakage, game-domain compliance, and holistic quality. Use when the user asks to validate, review, audit, check, score, or verify a game PRD, GDD, requirements doc, or design spec — especially phrases like "验证设计案", "检查PRD质量", "审查需求文档", "这份文档能不能进开发", "PRD写得怎么样", "review this GDD", "is this PRD production-ready", "check requirements doc". Do not use for: drafting or writing a new PRD/GDD from scratch; general writing polish or grammar fixes; validating non-game PRDs (SaaS, enterprise, mobile apps without game mechanics); code review; UX specification; implementation planning; or discussing what a good PRD looks like in the abstract.
使用 excalidraw-cli 和 @moona3k/excalidraw-export 绘制手绘风格示意图并导出为 SVG。当用户要求绘制线框图、界面流转图、架构图、流程图，或提到 excalidraw、手绘风格图、wireframe、示意图时，主动使用此 skill。也适用于需要将已有 .excalidraw 文件转为 SVG 的场景。
将本地 Markdown 文档推送到 iWiki 页面，自动识别 Obsidian 风格的图片/附件链接（支持 ![[file]]、![[file|size]]、[[file]] 三种格式，覆盖 jpg/png/svg 等类型），上传图片为附件并替换为带尺寸的 iWiki 引用。当用户提到"推送到 iWiki"、"更新 iWiki"、"同步到 iWiki"、"把 md 发到 iWiki"等意图时，主动使用本 skill。也适用于用户给出 iWiki URL 和本地 md 路径并希望同步的场景。
NBA2KOL2 游戏"时刻"皮肤配表工具。用于向 PlayerSkin.xlsx 及其关联 sheet 追加新的皮肤条目，覆盖完整的依赖链（UniformPanel、PicPanel、VideoPanel、CelebratePanel、IntroPanel、Main、UserInfoPanel），并配置关联的 Equipment.xlsx、Condition.xlsx、ClothesSet.xlsx、ID2StringMapTable.xlsx、Item.xlsx、CommonExchange.xlsx。 在以下场景下请主动使用本技能： - 用户提到要"配表"、"新增皮肤"、"加皮肤条目"、"填 PlayerSkin" - 用户说要配置"时刻"内容、新球员皮肤、或某某球员的XXX版本 - 用户提到 PlayerSkin.xlsx 的任何 sheet（Main、IntroPanel、PicPanel、VideoPanel、UniformPanel、CelebratePanel） - 用户提供了 Main ID、球员英文名文件夹、中文名版本标签等皮肤配置相关信息 - 用户提到"陈列室"、"致敬传奇"、"历史球员"、"现役球员"等系列名称 - 用户说"配XX球员"、"加个时刻"、"新增一个皮肤"、"开始配表" - 用户提到 Equipment、Condition、ClothesSet、Item、CommonExchange 等关联表的配置 - 用户说"碎片"、"合成"、"分解"、"道具配置"、"本地化文本"等配表相关术语
NBA2kOL3 Excel configuration table management tool for designers. Use when working with game config tables in the Table repository: (1) Adding new configuration sheets to existing Excel files, (2) Adding new configuration tables, (3) Converting Legacy (2-row header) to NBA2kOL3 (4-row header) format, (4) Generating/updating proto message definitions, (5) Visualizing table structure with DOT graphs, (6) Managing MacroString enum definitions, (7) Validating field references between tables, (8) Migrating module texts to Local sheet with localization keys, (9) Executing table-to-binary conversion. Also use when the user mentions "本地化sheet" or "本地化Sheet" — these are Chinese terms that always refer to the Excel "Local" sheet in this project. This skill provides direct access to Table Toolkit operations and follows the project's established workflow.
| name | grill-me |
| description | A relentless interview to sharpen a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases. |
| disable-model-invocation | true |
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
If a question can be answered by exploring the codebase, explore the codebase instead.
