Skip to main content

create-spf-behavior

Create or extract one SPF playback-engine behavior. Use for a new atomic responsibility with signals, lifecycle, cleanup, composition, and tests.

Zur Installation springen

Quellinformationen

Repository
videojs/v10
Letzte Quellaktivität
13. August 2026 um 16:54
Erkannte Sprache von SKILL.md
Englisch
Sterne
947
Forks
91

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
2 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
create-spf-behavior
description
Create or extract one SPF playback-engine behavior. Use for a new atomic responsibility with signals, lifecycle, cleanup, composition, and tests.
# Create an SPF behavior Read `references/workflow.md` completely before acting; it contains the detailed SPF creation workflow and failure checks. Read adjacent behaviors, the composition site, state/context slots, and `internal/design/spf/conventions/README.md`. Load only the applicable signal, actor, reactor, configuration, or behavior convention. 1. Define one-sentence purpose, inputs, writes, lifecycle, cleanup, ordering, and source-reset rules. 2. Confirm the responsibility is independently testable and does not hide coordination with another behavior. 3. Add focused failing tests, implement the smallest behavior, and wire it at the owning composition layer. 4. Verify slot ownership, naming, cleanup, boundaries, and final test coverage. If existing ownership must change, treat the work as a behavior refactor. If the requested capability spans multiple behaviors, keep this workflow scoped to the one atomic responsibility and surface the broader composition work separately. Run the narrow affected SPF tests. Build SPF when public types or exports change, and measure size when a public entry point can grow. ## Example Input: “Extract manifest refresh scheduling into its own behavior.” Output: One independently testable responsibility with explicit inputs, writes, lifecycle, cleanup, composition, and proportional verification.
Auf GitHub ansehen