菜单
Apply project planning conventions when creating or organizing plans. Use when user asks to create a plan, add a feature plan, document a bug, or work with the plans/ directory.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Visual regression for canvas-rendered matrix progressions. Tests filmstrip strips that show how 2D data evolves visually over time. Auto-apply when editing *Progressions.ts strip definitions or stories with filmstrip components.
Screenshot testing for React components with Playwright. Captures component pixels and compares to baselines. Auto-apply when editing React component stories or *.visual.spec.ts files that test UI components.
Pure logic and math testing with Vitest. Use for single-point assertions on functions, state transitions, and physics calculations. Auto-apply when editing *.test.ts files (except *Progressions.test.ts).
Matrix data model verification using ASCII diagrams. Use when working with *Progressions.ts files, defineProgression(), or testing how 2D numeric grids evolve over time. Auto-apply when editing files matching *Progressions.ts or src/test-utils/ascii*.ts.
Testing strategy orchestrator. Use when discussing test types, test order, or choosing how to test something. Auto-apply for general testing questions.
Screenshot-based regression testing with Playwright. Compares rendered pixels against baseline PNGs. Use when working with stories, *.visual.spec.ts files, or baseline screenshots. Auto-apply when editing files in stories/ or *.visual.spec.ts.
| name | plan-management |
| description | Apply project planning conventions when creating or organizing plans. Use when user asks to create a plan, add a feature plan, document a bug, or work with the plans/ directory. |
This project uses a structured planning system. Apply these conventions when working with plans.
| Folder | Purpose |
|---|---|
plans/model/ | Wave physics, simulation, timing |
plans/visuals/ | Rendering, gradients, effects |
plans/gameplay/ | Surfer, controls, multiplayer |
plans/tooling/ | Debug panel, dev tools |
plans/testing/ | Test strategy |
plans/bugfixes/ | Bug investigation and fixes |
plans/world/ | Environmental systems |
plans/reference/ | Research docs (never archive) |
plans/archive/ | Superseded plans |
# Plan [NUMBER]: [Title]
**Status**: Proposed | In Progress | Blocked | Complete
**Category**: model | visuals | gameplay | tooling | testing | bugfixes
**Depends On**: [other plan numbers, if any]
## Problem
Clear statement of what needs to be solved.
## Proposed Solution
Technical approach and key design decisions.
## Implementation Steps
1. First step with clear acceptance criteria
2. Second step...
## Files Affected
- `src/file.js` - What changes needed
## Testing
How to verify the implementation works correctly.
When completing implementation steps from a plan:
**Status**: Proposed to **Status**: Complete (or In Progress if partially done)## Completion Summary section at the end documenting:
Automatically apply when:
plans/ directory