maintain-vjsc-skin-gaps

Tracks VJSC parity gaps when legacy skins under packages/skins/src change.

931|91|Updated Aug 13, 2025
One-click install
npx skills add https://github.com/videojs/v10 --skill maintain-vjsc-skin-gaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintain-vjsc-skin-gaps
Source: https://github.com/videojs/v10/tree/main/.agents/skills/maintain-vjsc-skin-gaps
Command: npx skills add https://github.com/videojs/v10 --skill maintain-vjsc-skin-gaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When legacy Video.js skins change, the equivalent VJSC components can silently fall out of parity. This Skill keeps packages/skins/vjsc/gaps.md synchronized with observable legacy skin changes so parity gaps are documented, deduplicated, and removed only after verified implementation.

Core Features & Use Cases

  • Gap Tracking: Adds or updates entries in packages/skins/vjsc/gaps.md with Source, Gap, Affected, and Recommendation fields whenever legacy skin behavior changes.
  • Parity Verification: Inspects equivalent VJSC components, style rules, and generated HTML and React output to confirm whether a change already achieves parity.
  • Validation Workflow: Runs the narrowest affected skin tests, refreshes VJSC snapshots, and executes pnpm -F @videojs/skins test for cross-target changes.
  • Use Case: A contributor adds RTL control ordering to the legacy Default skin; the Skill guides recording the missing VJSC directional layout rules as a gap entry covering HTML, React, CSS, and Tailwind targets.

Quick Start

Ask the assistant to update the VJSC parity gaps file after modifying styles or behavior in packages/skins/src.

Frequently Asked Questions about maintain-vjsc-skin-gaps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track VJSC parity gaps after changing legacy Video.js skins?

Describe the observable legacy behavior change, inspect the equivalent VJSC component and generated output, then add or update an entry in packages/skins/vjsc/gaps.md with Source, Gap, Affected, and Recommendation fields.

When should I update the VJSC gaps.md file?

Update it when changing behavior, markup, selectors, data attributes, tokens, responsive rules, motion, or styles under packages/skins/src, or when fixing a legacy skin issue whose VJSC equivalent may need the same fix.

When should I not use the VJSC gap tracking workflow?

Skip it for VJSC-only work, documentation-only edits, or generated-output changes that do not alter legacy skin behavior. The workflow only tracks observable legacy skin changes affecting parity.

How do I verify a VJSC parity gap is resolved?

Verify all affected targets and CSS or Tailwind outputs after implementing the equivalent change, run the narrowest affected skin tests, refresh generated VJSC snapshots, and only then remove the gap entry.

What tests should I run for cross-target Video.js skin changes?

Run pnpm -F @videojs/skins test for cross-target skin changes, plus the narrowest affected skin tests and git diff --check. Refresh generated VJSC snapshots whenever output changes.