菜单
Create or update wiki knowledge pages for a game plugin or the framework. Use when writing strategy docs, skill guides, mechanics references, or updating the transferable knowledge base. Triggers on "wiki", "strategy doc", "skill doc", "mechanics doc", "game knowledge", "write documentation".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create or modify a game brain (decision engine) that subclasses BaseBrain. Use when implementing per-tick decision logic, adding roles, tuning thresholds, or writing the decide() method for a new game plugin. Triggers on "brain", "decide", "role", "threshold", "heuristic", "decision logic".
Configure or run the self-improving code evolution pipeline. Use when setting up evolution for a new game, customizing editable files, tuning the evolution prompt, running manual evolution, or managing the weekly fork/reset lifecycle. Triggers on "evolution", "evolve", "self-improving", "str_replace", "fork", "reset", "promote", "weekly cycle".
Create or modify an LLM harness that subclasses BaseHarness. Use when implementing LLM context building, directive parsing, system prompts, or post-game analysis hooks for a game plugin. Triggers on "harness", "LLM context", "system prompt", "directive", "narrator", "advisor".
Create or modify the game policy (control loop) that subclasses BasePolicy. Use when implementing perceive() to parse game engine observations, execute() to convert commands to game actions, or wiring brain + harness together. Triggers on "policy", "perceive", "execute", "control loop", "game engine bridge".
Run or configure post-game analysis on completed game memory dumps. Use when setting up the analysis pipeline, customizing the analysis prompt, reviewing learnings files, or running manual analysis. Triggers on "analyze", "post-game", "learnings", "score", "review game", "what went wrong".
Create or modify game event triggers that subclass BaseEventDetector. Use when implementing event detection for LLM consultation, adding new trigger types, tuning priorities, or configuring debounce. Triggers on "trigger", "event detection", "consult", "LLM scheduling", "when to call LLM".
| name | cyborg-wiki |
| description | Create or update wiki knowledge pages for a game plugin or the framework. Use when writing strategy docs, skill guides, mechanics references, or updating the transferable knowledge base. Triggers on "wiki", "strategy doc", "skill doc", "mechanics doc", "game knowledge", "write documentation". |
Wiki pages are markdown files that get loaded into the LLM's system prompt. They teach the LLM about game mechanics, strategy, and skills.
framework/wiki/)Game-agnostic knowledge that transfers across all games:
skills/ — frame parsing, movement, memory, LLM integration, role selectionstrategy/ — opening, resources, adaptation, common mistakes, promoted patternsmechanics/ — evolution loop, trigger system, memory tiersOnly edit framework wiki to add universal patterns — not game-specific tips.
games/{game}/wiki/)Game-specific knowledge:
strategy/opening.md — this game's opening strategystrategy/common-mistakes.md — this game's failure patternsskills/ — game-specific skills (e.g., trading, combat, deception)mechanics/ — game-specific mechanics (e.g., card types, map rules)Wiki pages are consumed by LLMs. Optimize for token efficiency:
IF resources > 50 AND tick > 200 THEN switch to builder# Page Title
Brief one-line summary of what this page covers.
## Section 1
Concise explanation with concrete examples.
| Condition | Action | Why |
|---|---|---|
| HP < 20 | Flee | Survival override |
| Resources full | Deposit | Don't waste carrying capacity |
## Common Mistakes
- **Mistake name**: What goes wrong and how to fix it
Wiki files listed in game_config.py's EDITABLE_FILES can be modified by
the evolution agent. The evolution agent updates wiki pages based on post-game
analysis, adding new rules and correcting outdated guidance.
Typical editable wiki files:
EDITABLE_FILES = [
"games/my_game/brain.py",
"games/my_game/wiki/strategy/opening.md",
"games/my_game/wiki/strategy/common-mistakes.md",
"games/my_game/wiki/skills/combat.md",
]
Successful patterns from game-specific wiki get promoted to the framework
wiki via scripts/promote_patterns.py. This makes them available to all
future games.
framework/wiki/strategy/promoted-patterns.md — patterns promoted from gamesframework/wiki/strategy/common-mistakes.md — universal failure patterns