Specialized knowledge for AI agents working on Video.js 10.
| Workflow | Load |
|---|---|
| Building store/features | api |
| Building HTML components | component + aria |
| Building React components | component + aria |
| Writing documentation | docs |
| Writing component reference | api-reference |
| Writing Design Docs / RFCs | design or rfc |
| Reviewing API/architecture | api → review/workflow.md |
| Reviewing documentation | docs → review/workflow.md |
| Reviewing components | component → review/workflow.md |
| Reviewing accessibility | aria → review/workflow.md |
| Accessibility audit | aria |
| Committing / creating PRs | git or /commit-pr |
| CSS → Tailwind migration | css-to-tailwind |
| Reviewing Tailwind migration | css-to-tailwind → review/workflow.md |
| Reviewing branch changes | /review-branch |
| Analyzing GitHub issues | /gh-issue |
| Creating GitHub issues | /create-issue |
| Updating AI docs | /claude-update |
| Creating new skills | /create-skill |
| Skill | Purpose | Has Review? |
|---|---|---|
| api | API design and DX — extensibility, type safety, progressive disclosure | Yes |
| aria | Accessibility patterns — ARIA, keyboard, focus, media player a11y | Yes |
| claude-update | Update CLAUDE.md and skills when introducing new patterns | No |
| commit-pr | Commit changes and create/update PRs with conventions | No |
| component | Build headless UI components — compound patterns, state, styling | Yes |
| css-to-tailwind | Migrate CSS/SCSS/styled-components to Tailwind v4 — @theme, tokens, parity, reporting |
Yes |
| create-issue | Create GitHub issues with consistent formatting and conventions | No |
| create-skill | Create new skills with proper structure and conventions | No |
| design | Write Design Docs — decisions you own, component specs, feature designs | No |
| api-reference | Scaffold component API reference pages | No |
| docs | Write Video.js 10 documentation (concepts, how-to, READMEs) | Yes |
| gh-issue | Analyze GitHub issues and create implementation plans | No |
| git | Git workflow — commit messages, PRs, branch naming, scope inference | No |
| merge-behaviors | Merge two SPF behaviors with cleaned-shape-first discipline | No |
| refactor-behavior | Refactor an SPF behavior using purpose-first discipline | No |
| review-branch | Review branch changes and suggest improvements | No |
| rfc | Write RFCs — proposals needing buy-in (public API, product, DX) | No |
| spf-create-behavior | Create a new SPF behavior with conventions-aligned shape (stub; grows with use) | No |
| spf-document-feature | Produce/update SPF feature registry docs (triangulation, cluster heuristics, cross-cutting checks, cascade) | No |
| spf-document-use-case | Produce/update SPF use-case-composition registry docs (four-mechanism taxonomy, constituent-feature cascade) | No |
| spf-implement-feature | Implement an SPF feature from its registry doc (disambiguation, phase scoping, chunk decomposition, downstream-skill routing, doc-as-starting-point) | No |
| spf-implement-use-case | Implement an SPF use-case composition from its registry doc (disambiguation/routing, constituent-feature readiness, variant assembly, doc-as-starting-point) | No |
| spf-update-behavior | Update an existing SPF behavior whose purpose is changing (stub; distinct from /refactor-behavior which preserves purpose) | No |
| split-behavior | Split one SPF behavior into N with axis-declared, constraints-audited discipline | No |
Skills with review capability have a review/ subfolder:
skill/
├── SKILL.md
├── references/
└── review/
├── workflow.md # Review process and checklists
├── agents.md # Sub-agent prompts
└── templates.md # Output formats
| Skill | Review Focus |
|---|---|
api/review/ |
API design, architecture, DX, type safety |
docs/review/ |
Documentation quality — tone, structure, examples |
component/review/ |
Component architecture, state, props, styling |
aria/review/ |
Accessibility — ARIA, keyboard, focus, WCAG |
css-to-tailwind/review/ |
Tailwind migration — utilities, arbitrary values, theme gaps |
skill-name/
├── SKILL.md # Entry point with overview and reference table
├── references/ # Detailed reference files (load on demand)
│ └── *.md
└── review/ # (optional) Review workflow
├── workflow.md
└── *.md
Add a reference file:
- Create file in
references/ - Add entry to reference table in SKILL.md
- Add cross-links to related files
Add review capability:
- Create
review/subfolder - Add
workflow.mdwith process and checklists - Add agent prompts and templates
- Add Review section to SKILL.md
Add a new skill:
- Create directory with SKILL.md
- Add frontmatter with
nameanddescription - Add to this README
When code changes introduce new patterns that a skill should cover:
- Identify affected skill (component, aria, api, docs, css-to-tailwind)
- Update the relevant reference file or add a new one
- If pattern is cross-cutting, update CLAUDE.md Code Rules instead
Triggers for skill updates:
- New component patterns (compound components, state management)
- New accessibility patterns (ARIA, keyboard, focus)
- New API design decisions (extensibility, type safety)
- New DX considerations (inference, defaults, naming)
- New Tailwind or skin parity patterns (
packages/skins)
For detailed guidance and consistency checklists, run /claude-update.