菜单
v0.1.0 - Simplify a reviewed and sufficiently deep algorithm tutorial without weakening derivation, evidence, invariants, correctness, complexity, or final runnable demo. Use when the article is structurally accepted but too repetitive, checklist-like, or heavy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
v0.1.0 - Check a tutorial draft against its saved plan and sketch before review. Use when a draft needs plan adherence, concept timing, code continuity, runnable snippet, and Hugo placement checks before tutorial review.
v0.1.0 - Record an approved tutorial plan into an ignored local run directory. Use when a LeetCode or algorithm tutorial plan must survive context compaction, multi-turn work, or handoff before build starts.
v0.1.0 - Create a teaching skeleton and code-growth contract from a saved tutorial plan. Use before tutorial build when concept timing, helper extraction, final-code placement, or checkpoint continuity must be made explicit.
v0.1.1 - Build exactly one planned LeetCode tutorial increment through problem pressure, naive baseline, break, change, check, freeze, and review handoff. Use when a task-first LeetCode tutorial plan is ready and the next checkpoint must be drafted without self-approval.
v0.1.0 - Build exactly one planned algorithm tutorial checkpoint and stop for review. Use when a task-first algorithm tutorial plan is ready and the next section must derive one mechanism, invariant, code fragment, or runnable checkpoint from concrete pressure without self-approval.
v0.1.0 - Deepen 1-2 selected concepts in a reviewed algorithm tutorial using PDKH standards. Use when a method tutorial needs stronger invariant, formalization, correctness, complexity, counterexample, or engineering-reality evidence without broadening into unrelated topics.
| name | algorithm-tutorial-simplify |
| description | v0.1.0 - Simplify a reviewed and sufficiently deep algorithm tutorial without weakening derivation, evidence, invariants, correctness, complexity, or final runnable demo. Use when the article is structurally accepted but too repetitive, checklist-like, or heavy. |
Tighten a structurally accepted algorithm tutorial while preserving its derivation and depth. This is not a repair skill for broken teaching structure.
When NOT to use: planning, first drafting, review acceptance, deepening, or algorithm changes.
## Simplification Summary
- ...
## Preserved Evidence
- ...
## Remaining Risks
- ...