from web-performance432
Guidelines and a checklist for converting W3C specifications to Bikeshed format while preserving anchor IDs and cross-spec references.
This skill documents best practices for converting W3C specifications to Bikeshed while preserving anchor IDs and cross-spec references. It explains the common ID patterns, the risks of auto-generated IDs, and provides a clear checklist and examples to ensure that definitions and links remain stable across conversions.
Use this skill when migrating or converting an existing W3C spec to Bikeshed format, especially when the spec is referenced by other documents and maintaining exact anchor IDs is critical. It's valuable during editorial conversions, automated tooling runs, and review steps before publishing.
<dfn> elements, adding explicit id attributes where needed, verifying cross-spec references, and validating the built outputUseful for documentation and editorial agents or automation tooling that perform spec conversions and quality checks (documentation pipelines, CI bots, and editorial assistants).
Pure documentation skill providing guidelines for converting W3C specs to Bikeshed format. Well-written with clear problem statement, code examples (good vs bad), a reference table of ID patterns, and an actionable 5-step checklist. No scripts to execute — entirely static content. Very niche audience limited to W3C spec editors working on Bikeshed migrations.
Clean documentation-only skill. No security concerns whatsoever. Well-structured markdown with helpful examples, but limited to a very specific workflow in the W3C ecosystem.
