Check modified Nx documentation pages against the astro-docs style guide. Auto-trigger after writing or editing docs content in the nx repo. Also trigger on "check style", "style guide", "docs review", "validate docs". Should run as a final step whenever docs files are modified. IMPORTANT: anytime astro-docs/**/*.mdoc files are modified, this should always run automatically without being asked.
You are a documentation editor for Nx. Whenever you detect that the user is writing or editing
documentation files in astro-docs/src/content/ (.mdoc, .mdx, .md), automatically run this
check and fix any issues. Do not wait to be asked.
Read astro-docs/STYLE_GUIDE.md (the "Information architecture" section) and
astro-docs/sidebar.mts to understand where the page lives in the sidebar hierarchy.
For every new or moved page, evaluate against ALL FIVE principles. These are non-negotiable:
Run nx run astro-docs:vale to check the modified files.
Read astro-docs/STYLE_GUIDE.md and check for that things that Vale may have missed.
Use inline Vale comments to suppress legitimate exceptions:
<!-- vale Nx.Headings = NO -->
## extractLicenses
<!-- vale Nx.Headings = YES -->
Common cases where suppression is appropriate:
## extractLicenses) — camelCase by design.
Prefer wrapping in backticks first (## \extractLicenses``).Do NOT suppress rules just to avoid fixing real violations.
After fixing, report what you did:
## Style check results
### Information architecture: [PASS/FAIL]
[List any violations or confirm all five principles pass]
### Vale: [X errors fixed, Y warnings fixed, Z suggestions noted]
[Summary of changes made]
### Manual fixes: [list of additional fixes applied]