write-html-component-design

Write HTML design records. Use when the user explicitly requests one.

Repositorio: videojs/v10
Última actividad en el origen: 10 de agosto de 2026 a las 17:26
Idioma detectado de SKILL.md: inglés
Estrellas: 933
Forks: 91

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/videojs/v10 --skill write-html-component-design

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name	write-html-component-design
description	Write HTML design records. Use when the user explicitly requests one.

HTML component design records

Read internal/design/README.md, nearby records, and relevant HTML code, tests, exports, and package metadata.

Require an explicit request. Use its path or the smallest UI record location, with HTML scope clear.
State the element boundary and only the rationale or constraint that code and tests cannot explain.
Cover ownership, anatomy, markup versus CSS, APIs, opt-outs, registration, or bundle cost only when they explain the choice.
Link source instead of copying inventories or mechanics. Include alternatives or consequences only when material.

Keep it to a few paragraphs. Do not add a React contract or companion record without a separate request.

Example

Input: “Write an HTML component design record for chapter selection.”

Output: A compact custom-element decision, its non-inferable rationale, and useful source links.

Volver a la búsqueda Volver a la instalación

write-api-reference

Write generated Video.js API reference pages. Use for components, hooks, controllers, factories, builder compatibility, demos, or extracted JSDoc.

2026-09-09

create-vjsc-component

Create VJSC modules. Use for UI and styles.

2026-09-09

implement-spf-use-case

Implement an SPF use-case composition. Use when a delivery scenario combines feature variants and requires composition, tests, and status updates.

2026-09-03

Ver todos los de este repositorio

name	write-html-component-design
description	Write HTML design records. Use when the user explicitly requests one.

HTML component design records

Read internal/design/README.md, nearby records, and relevant HTML code, tests, exports, and package metadata.

Require an explicit request. Use its path or the smallest UI record location, with HTML scope clear.
State the element boundary and only the rationale or constraint that code and tests cannot explain.
Cover ownership, anatomy, markup versus CSS, APIs, opt-outs, registration, or bundle cost only when they explain the choice.
Link source instead of copying inventories or mechanics. Include alternatives or consequences only when material.

Keep it to a few paragraphs. Do not add a React contract or companion record without a separate request.

Example

Input: “Write an HTML component design record for chapter selection.”

Output: A compact custom-element decision, its non-inferable rationale, and useful source links.

write-html-component-design

Datos de origen

Opciones de instalación

Revisa los archivos de origen

HTML component design records

Example

Más de este repositorio

HTML component design records

Example

Más de este repositorio