fix: keep skill metadata within specification

SKILL.md

@@ -1,17 +1,12 @@
 ---
 name: documentation-docusaurus
 description: >
-  Opinionated guidance for building and restructuring Docusaurus documentation sites on the
-  Diátaxis framework — separating tutorials, how-to guides, reference, and explanation, and
-  refusing to mix them on one page. Use when creating a new docs site or page, reorganising an
-  existing one, deciding which quadrant a page belongs to, writing frontmatter, sidebars, or
-  admonitions, editing docusaurus.config.ts, applying voice and inclusive-language standards,
-  or setting up deployment to Vercel, Netlify, GitHub Pages, or Cloudflare Pages. Triggers on
-  docs/, blog/, docusaurus.config, sidebars.ts, .mdx files, or any request to write, improve,
-  build a local YAML data database for React/MDX views, create React Flow roadmaps or dependency
-  maps, render editable Draw.io sources with docusaurus-plugin-drawio, or restructure documentation — even when the user only says "write docs", "document this",
-  or "the docs are a mess". Asks who the reader is and what they should be able to DO before
-  writing, because the answer decides the structure.
+  Opinionated Docusaurus v3 guidance using Diátaxis. Use when creating or restructuring documentation,
+  writing MDX, configuring navigation or deployment, building a local YAML data database, creating
+  React Flow roadmaps and dependency maps, or rendering editable Draw.io sources. Triggers on docs/,
+  blog/, docusaurus.config, sidebars, MDX, documentation data, and requests to write or improve docs.
+  Requires the intended reader and outcome before writing, keeps documentation types separate, and
+  applies accessibility, inclusive-language, build, browser, and deployment verification standards.
 license: MIT
 metadata:
   author: workspace-skills-code-agent