Commit, push, and create or update a Video.js pull request. Use when the user explicitly requests repository publication or PR preparation.
videojs/v10
SkillsMP has collected 37 skills from videojs/v10. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 37
- GitHub stars
- 947
- GitHub forks
- 91
Skills in this repository
Showing 37 of 37 collected skills.
Translate or audit the values in a Video.js locale pack. Use when a key needs values, en.ts copy changes underneath a pack, or one pack needs an audit.
Review the current branch without editing code. Use for PR-style findings, regressions, merge-base comparison, or pre-merge risk assessment.
Review Video.js documentation without editing it. Use for accuracy, reader outcomes, structure, voice, examples, MDX, READMEs, or docs diffs.
Write generated Video.js API reference pages. Use for components, hooks, controllers, factories, builder compatibility, demos, or extracted JSDoc.
Write Video.js guides, concepts, READMEs, and JSDoc. Use for site prose, examples, inline API documentation, or package documentation.
Create VJSC modules. Use for UI and styles.
Create or change Video.js React UI components. Use for React component boundaries, state ownership, compound parts, render customization, styling hooks, exports, or client behavior.
Implement an SPF use-case composition. Use when a delivery scenario combines feature variants and requires composition, tests, and status updates.
Create Vite plugins. Use for hooks.
Maintain deferred VJSC parity gaps. Use when work under packages/skins/src adds, closes, or explicitly defers a parity gap.
Create repository skills. Use for repeatable agent workflows.
Create or change Video.js custom-element UI components. Use for HTML component boundaries, properties, events, controllers, light-DOM parts, styling hooks, registration, or lifecycle.
Document an SPF feature record. Use when the user explicitly requests capability scope, relationships, status, constraints, or evidence.
Document an SPF use-case record. Use when the user explicitly requests delivery scenarios, variants, relationships, status, or verification.
Configure Vite+. Use for tasks, cache, migration, or CI.
Create Rolldown plugins. Use for hooks.
Review custom-element UI without editing code. Use for data flow, markup, styling, transitions, registration, or bundles.
Review React UI without editing code. Use for data flow, APIs, customization, styling, transitions, or bundles.
Transform code. Use for Rolldown.
Implement UI transitions and rendered presence. Use for lifecycle, cancellation, rapid reopen, or HTML/React parity.
Design Video.js TypeScript APIs. Use for public shape, inference, state, extension points, middleware, composition, or ergonomics.
Create or extract one SPF playback-engine behavior. Use for a new atomic responsibility with signals, lifecycle, cleanup, composition, and tests.
Implement an SPF feature from its registry entry. Use when an engine capability spans behaviors and requires tests plus status updates.
Maintain repository agent guidance. Use for AGENTS.md, CLAUDE.md compatibility, skill drift, duplicated instructions, or context budgets.
Review Video.js TypeScript APIs without editing code. Use for inference, state, extensibility, composition, packaging, or architecture audits.
Review HTML component designs. Use for boundaries, APIs, opt-outs, and bundles.
Review React component designs. Use for boundaries, APIs, opt-outs, and bundles.
Write or update a Video.js architecture, feature, or decision record only when the user explicitly requests that record. Use for compact, non-inferable rationale outside UI component design.
Write HTML design records. Use when the user explicitly requests one.
Write React design records. Use when the user explicitly requests one.
Draft or revise a Video.js RFC. Use for public APIs, product direction, user-facing DX, shared architecture, or hard-to-reverse proposals needing buy-in.
Draft or create a videojs/v10 GitHub issue and its native planning relationships. Use when asked to file a bug, feature, task, epic, or repository issue.
Change SPF playback-engine behaviors. Use when updating, refactoring, splitting, or merging responsibilities, signals, lifecycle, cleanup, or composition.
Implement accessible Video.js UI. Use for semantics, ARIA, keyboard interaction, focus, screen readers, captions, or live regions.
Investigate GitHub issues without changing code. Use when asked to analyze, diagnose, scope, or produce an evidence-backed implementation plan.
Review Video.js UI accessibility without editing code. Use for semantics, names, ARIA, keyboard, focus, captions, contrast, motion, or WCAG.