What problem does it solve?
Creating a new SPF playback-engine behavior without a disciplined workflow leads to behaviors with unclear purpose, oversized slot maps, mismatched cleanup patterns, and tests written after the fact. This Skill enforces a purpose-first, conventions-aligned creation workflow so each behavior is atomic, independently testable, and correctly wired into the engine composition.
Core Features & Use Cases
- Purpose-first articulation: Define the behavior's business rule, signal inputs/outputs, lifecycle, and source-reset rules before writing any code.
- Conventions-aligned scaffolding: Apply the project's signal, actor, reactor, config, and cleanup conventions (named-cleanup-collection, not AbortController) when designing the slot map and composition placement.
- TDD workflow: Write a failing test in the behaviors test directory first, implement the smallest behavior, then wire it at the owning composition layer and run the affected SPF tests.
- Use Case: When asked to extract manifest refresh scheduling into its own behavior, use this Skill to produce one independently testable responsibility with explicit inputs, writes, lifecycle, cleanup, composition, and proportional verification.
Quick Start
Ask the AI to create a new SPF behavior for a specific atomic responsibility, such as extracting manifest refresh scheduling into its own behavior.
