What problem does it solve? Keeping craft-ts documentation accurate is hard because Markdown code fences are invisible to CI, so examples silently rot when the public API changes. This Skill enforces a docs workflow where complete examples live in linted, Vitest-tested snippet specs and pages import them via named regions. ## Core Features & Use Cases - Page structure guidance: Defines where pages belong (Learn, Guide, Reference, Resources) and the required shape for each, including sidebar registration in the VitePress config. - Snippet extraction rules: Decides which examples get extracted into apps/docs/tests/snippets/ spec files with named #region markers and which stay inline (fragments, anti-examples, signatures). - API currency enforcement: Rewrites stale APIs (signal(), MaybeSignal, inject()) to current Craft patterns (state(), CraftServiceInput, yield*) before extraction. - Use Case: When adding a new Guide page for a craft-ts service, extract the complete craftService example into a spec file with a real it() assertion, reference it with <<< @/tests/snippets/...#region, and verify with npx nx test docs and npx nx lint docs. ## Quick Start Update the craft-ts guide page for services by extracting its complete example into a tested snippet region and running the docs test and lint targets.
