change-spf-behavior
GitHub指导修改SPF播放引擎行为，涵盖更新、重构、拆分或合并职责。通过标准化工作流确保状态、生命周期及测试的正确性，并执行相关构建与测试命令。
触发场景
安装
npx skills add videojs/video.js --skill change-spf-behavior -g -y
SKILL.md
Frontmatter
{
"name": "change-spf-behavior",
"description": "Change SPF playback-engine behaviors. Use when updating, refactoring, splitting, or merging responsibilities, signals, lifecycle, cleanup, or composition."
}
Change an SPF behavior
Treat code and tests as implementation truth. Read the behavior, composition site, state/context slots, helpers, and tests, then load only the relevant file from internal/design/spf/conventions/.
Before acting, read the one detailed workflow that matches the requested change:
- Purpose expands or changes:
references/update.md - Purpose stays fixed while implementation improves:
references/refactor.md - One responsibility splits by type or concern:
references/split.md - Two responsibilities may become one:
references/merge.md
- State the current purpose, intended delta, and observable business rules.
- Map inputs, writes, lifecycle gates, cleanup, ordering, and source-reset rules.
- Choose the smallest destination shape that preserves those constraints.
- Pin observable behavior with tests before changing implementation.
- Re-read the final behavior without the diff and verify ownership, cleanup, composition, naming, and coverage.
For a split, name the ownership axis and cross-boundary invariants. For a merge, confirm the result owns one coherent purpose; extract a helper when only an algorithm is shared. Ask for direction when alternatives materially change ownership or public contracts.
Run the narrow affected tests, then as applicable:
pnpm -F @videojs/spf test
pnpm -F @videojs/spf build
pnpm -F @videojs/spf size
Example
Input: “Split source cleanup out of the playback lifecycle behavior.”
Output: A documented ownership boundary, pinned invariants, focused implementation changes, and proportional SPF checks.
版本历史
- 8a0a3d8 当前 2026-10-20 08:02
