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.

Aller à l'installation

Informations de source

Dépôt
videojs/v10
Dernière activité de la source
13 août 2026 à 16:54
Langue détectée de SKILL.md
anglais
Étoiles
947
Forks
91

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers
2 fichiers

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
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.
Voir sur GitHub