What problem does it solve? Maintaining accurate Nodefony documentation is hard: code anchors drift out of date, internal links break silently, quick-start examples stop compiling, and publishing to GitHub Pages risks dead links. This Skill provides the complete toolkit to write, verify, and publish the Nodefony documentation corpus across its three consumers: the public site, the admin console portal, and the writing standard itself. ## Core Features & Use Cases - Documentation quality gates: Run doc-lint, anchor-check, anchor-inpage, and code-check scripts to enforce frontmatter conventions, verify file:line code anchors against real source, detect dead in-page anchors, and compile quick-start TypeScript blocks. - Anchor repair: Automatically recalibrate stale code anchors after code changes using anchor-fix, which resolves symbols to their definition lines with dry-run and apply modes. - Public site publishing: Generate the GitHub Pages site with build-docs-site.mjs, decide page visibility via folder, status, and the publish frontmatter key, and enforce relative-link rules with the anti-dead-link gate. - Portal front-end components: Build documentation pages in the Studio admin console using DocLayout, MarkdownDoc, DocPageHeader, DocToc, and FlowGraph with a strict zero-magic-number layout model. - Use Case: After refactoring a Nodefony module, run anchor-check piped into anchor-fix to recalibrate every documentation anchor that referenced moved code, then re-verify with the four gates before committing. ## Quick Start Ask the assistant to write a new documentation page for a Nodefony module and run the doc-lint, anchor-check, anchor-inpage, and code-check gates on it before committing.
