ask-demon

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Ask Demon

Ask Demon

You don't remember every skill, so ask. This pack complements Matt's engineering skills: Matt owns the engineering loop (grill → spec → tickets → implement → code-review — the single review entry point) and the writing skills; this pack owns the documentation and Agent-Note maintenance loop and game-domain work. The full absorption map and seams are in the pack's skills map (
docs/skills-map.md
in the source repository).
A flow is a path through the skills. One main flow carries the documentation work; a governance run brings a whole repository's docs in line with its standard; everything else is standalone, or a prose-and-docs tool layer that runs underneath.
你不可能记住所有skill,所以直接询问即可。此工具包是对Matt工程类skill的补充:Matt负责工程循环(需求调研→规格定义→工单创建→开发实现→代码评审——单一评审入口)和写作类skill;本工具包负责文档和Agent-Note维护循环,以及游戏领域相关工作。完整的技能覆盖图和边界划分可查看工具包的技能地图(源码仓库中的
docs/skills-map.md
)。
flow指的是skill的执行路径。其中一条主流程负责文档工作;治理运行用于将整个仓库的文档统一对齐标准;其余则为独立skill,或为底层运行的文档与文案工具层。

Session discipline

会话规范

Four standing-order lines in the host repository's root
AGENTS.md
gate every action;
setup-demon-skills
writes them into a repository. Operationally:
  • Before acting — answer questions and analyze proposals without writing; treat only an explicit execution signal with a confirmed scope as authorization; unclear intent gets one clarifying question first.
  • Before committing — stop on any red check; the fix or its explanation ships in the same turn, and the final report names every failed check.
  • Before claiming — inspect files before editing or describing them; report only work that was actually done.
  • Before destructive moves — deletions, history rewrites, and force-push wait for the user to name the action.
Every flow in this pack obeys the gate: findings and plans come first, fixes run after confirmation.
宿主仓库根目录下的
AGENTS.md
文件中有四条固定规则,用于管控所有操作;
setup-demon-skills
会将这些规则写入仓库。操作层面要求:
  • 执行前——先解答问题、分析方案,不进行写入操作;仅将带有确认范围的明确执行信号视为授权;若意图不明确,先提出一个澄清问题。
  • 提交前——遇到任何红色检查项时停止;修复操作或相关说明需同步完成,最终报告需列出所有检查失败项。
  • 认领前——编辑或描述文件前先检查文件;仅汇报实际完成的工作。
  • 执行破坏性操作前——删除、历史重写和强制推送操作需等待用户明确指令。
本工具包中的所有flow均遵循上述规则:先输出调查结果和计划,获得确认后再执行修复操作。

The main flow: maintain a change

主流程:变更维护

The route documentation work travels: review a change, simplify what it surfaces, archive what it supersedes, sync the bilingual pairs.
  1. repo-standards-review
    — review a PR or branch against the repository's standards (skill frontmatter and body, docs, bilingual pairs, Agent Notes, scripts). Produces blockers plus suggestions. Run when a change is ready for review, or as a pre-push gate.
  2. doc-standards
    — when the change touches documentation, run the structural pass and audit probes so the docs land in the right home, at the right detail, under budget. The review hands off here for doc changes.
  3. find-simplifications
    — take the dead, duplicated, speculative, or over-built surface the review surfaced, and turn the worthwhile ones into proposed Agent Notes or TODO markers. The review and docs steps hand off here.
  4. archive-agent-notes
    — when a change makes an owning note obsolete, classify and archive the superseded records. A simplification hands off here.
  5. translate-docs
    — after the earlier steps touched docs or notes, sync their English↔Chinese pairs. The archive step hands off here when link repair edited a bilingual doc.
The flow cascades —
repo-standards-review → doc-standards (when docs touched) → find-simplifications → archive-agent-notes → translate-docs
— and each step is also independently invocable.
文档工作的执行路径:评审变更、简化变更暴露的内容、归档被替代的内容、同步双语文档对。
  1. repo-standards-review
    ——对照仓库标准(skill前置信息与主体内容、文档、双语文档对、Agent Notes、脚本)评审PR或分支。输出阻塞项及建议。在变更准备好评审或作为推送前检查时运行。
  2. doc-standards
    ——当变更涉及文档时,执行结构检查和审计探查,确保文档存放位置正确、细节合适、符合预算要求。评审完成后,文档变更将移交至此步骤处理。
  3. find-simplifications
    ——针对评审发现的冗余、重复、推测性或过度设计内容,将有价值的部分转化为拟议的Agent Notes或TODO标记。评审和文档步骤完成后移交至此步骤。
  4. archive-agent-notes
    ——当变更使某个Agent Note过时,对被替代的记录进行分类并归档。简化步骤完成后移交至此步骤。
  5. translate-docs
    ——当前面步骤涉及文档或笔记时,同步其英文↔中文双语文档对。当归档步骤中的链接修复修改了双语文档时,移交至此步骤。
流程会逐级触发——
repo-standards-review → doc-standards(涉及文档时)→ find-simplifications → archive-agent-notes → translate-docs
——且每个步骤也可独立调用。

The governance run

治理运行

A whole-repository pass when asked to govern, standardize, or audit the repository's documentation:
  1. Foundation — the root
    AGENTS.md
    pointer, the documentation standard, the Agent Note tree, the bilingual pairing contract, the session-discipline lines, and the documentation budget gate must exist; missing ones come from
    setup-demon-skills
    .
  2. Audit
    doc-standards
    runs the structural pass and the six corpus probes; report a non-compliance list naming each document, the violated clause, and the owning fix skill.
  3. Fix by domain, after the user confirms scope — structure, placement, budgets →
    doc-standards
    ; prose →
    prose-standard
    ; leakage →
    trim-cot-leakage
    ; dead surface →
    find-simplifications
    ; pairs →
    translate-docs
    ; superseded notes →
    archive-agent-notes
    .
  4. Close out — the documentation gates and
    git diff --check
    , re-record touched pairs, one Agent Note per non-trivial change, word deltas in the PR body — then the main flow takes the change home.
Every step confirms with the user before writing; a fix that changes promised behavior goes through a proposed Agent Note first.
当需要管控、标准化或审计仓库文档时,执行全仓库扫描:
  1. 基础检查——根目录
    AGENTS.md
    指针、文档标准、Agent Note树、双语文档对约定、会话规范规则和文档预算管控必须存在;缺失项将通过
    setup-demon-skills
    生成。
  2. 审计——
    doc-standards
    执行结构检查和六项语料探查;输出不合规列表,包含每个文档名称、违反的条款及负责修复的skill。
  3. 按领域修复(需用户确认范围后)——结构、存放位置、预算→
    doc-standards
    ;文案→
    prose-standard
    ;冗余内容→
    trim-cot-leakage
    ;无效内容→
    find-simplifications
    ;双语文档对→
    translate-docs
    ;过时笔记→
    archive-agent-notes
  4. 收尾——检查文档管控规则和
    git diff --check
    ,重新记录被修改的双语文档对,为每个非 trivial 变更创建一个Agent Note,在PR主体中记录字数变化——之后由主流程处理该变更。
每个步骤在写入前均需获得用户确认;若修复操作会改变既定行为,需先提交拟议的Agent Note。

Prose and docs tool layer

文档与文案工具层

Four skills run beneath the flow and are reachable on their own when the prose or document structure, not the process, is the problem:
  • prose-standard
    — the base: preserve the complete proposition, then remove reasoning transcripts, repetition, and decoration. Owns editorial judgment and coverage.
  • trim-cot-leakage
    — one smell: prose whose vantage is the authoring session (dead citations, change narration, review choreography). Restate the facts, delete the transcript.
  • prune-prompt-pollution
    — another smell: negation priming, absence declarations, stale meta-narrative, strawman warnings. Restate the positive target or the consequence.
  • doc-standards
    — the structure side: placement, tutorial/reference classification, corpus audits, and budget-gate probes. Owns where documents live and how they are shaped; prose-standard owns how they read.
有四个skill在流程底层运行,当文案或文档结构(而非流程)出现问题时,可单独调用:
  • prose-standard
    ——基础工具:保留完整核心信息,移除推理记录、重复内容和修饰性文字。负责编辑判断和内容覆盖。
  • trim-cot-leakage
    ——处理一类问题:视角为创作会话的文案(无效引用、变更说明、评审流程描述)。重述事实,删除会话记录。
  • prune-prompt-pollution
    ——处理另一类问题:否定引导、缺失声明、过时元叙事、稻草人警告。重述正向目标或后果。
  • doc-standards
    ——结构层面工具:存放位置、教程/参考分类、语料审计和预算管控探查。负责文档的存放位置和结构形态;prose-standard负责文档的表述方式。

Standalone

独立skill

Off the main flow; reach for each on its own trigger.
  • pre-push-checks
    — before pushing, select the narrowest checks that cover the outgoing diff; protect history-rewriting pushes with
    --force-with-lease
    .
  • merging-stacked-prs
    — land a stack of dependent GitHub PRs through
    gh stack
    ; layers with Matt's
    resolving-merge-conflicts
    .
  • workflow-capture
    — turn a proven or requested workflow into a reusable skill.
  • record-browser-gif
    — record browser/Web UI demos as evidence GIFs for GUI-changing PRs.
  • agent-doorbell
    — install hook-based desktop/audio reminders for agent stop and attention events.
  • dota2-custom-game-dev
    — DOTA2 custom game addons.
  • roblox-luau-developer
    — Roblox Luau development, debugging, and Rojo sync.
  • roblox-typescript-developer
    — Roblox TypeScript (roblox-ts) development.
  • unreal-blueprint-analyzer
    — read-only Unreal Blueprint asset analysis.
不属于主流程,需根据特定触发条件单独调用。
  • pre-push-checks
    ——推送前,选择覆盖 outgoing diff 的最窄范围检查;使用
    --force-with-lease
    保护重写历史的推送操作。
  • merging-stacked-prs
    ——通过
    gh stack
    合并GitHub上的依赖PR栈;可与Matt的
    resolving-merge-conflicts
    配合使用。
  • workflow-capture
    ——将已验证或需求中的工作流转化为可复用的skill。
  • record-browser-gif
    ——录制浏览器/Web UI演示GIF,作为GUI变更PR的佐证。
  • agent-doorbell
    ——安装基于钩子的桌面/音频提醒,用于Agent停止和需关注事件。
  • dota2-custom-game-dev
    ——DOTA2自定义游戏插件开发。
  • roblox-luau-developer
    ——Roblox Luau开发、调试及Rojo同步。
  • roblox-typescript-developer
    ——Roblox TypeScript(roblox-ts)开发。
  • unreal-blueprint-analyzer
    ——只读式Unreal Blueprint资产分析。

Setup

安装配置

The maintenance flow needs a repository's conventions in place first — the Agent Note tree, the bilingual pairing contract, the documentation standard, the session-discipline lines, and the documentation budget gate. Run
setup-demon-skills
once to scaffold them and record where they live.
维护流程需要先配置好仓库的约定——Agent Note树、双语文档对约定、文档标准、会话规范规则和文档预算管控。运行一次**
setup-demon-skills
**即可快速搭建这些内容并记录其存放位置。