nx-docs-writer

Convert nx.dev documentation from Markdoc to Starlight format.

1|Updated Jun 3, 2025
One-click install
npx skills add https://github.com/jaysoo/dot-ai-config --skill nx-docs-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-docs-writer
Source: https://github.com/jaysoo/dot-ai-config/tree/main/dot_gemini/skills/nx-docs-writer
Command: npx skills add https://github.com/jaysoo/dot-ai-config --skill nx-docs-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardized, high-quality nx.dev documentation can be hard to maintain across pages, and migrations between Markdoc and Starlight introduce inconsistencies that slow teams.

Core Features & Use Cases

  • Consistent documentation writing and editing for nx.dev sites.
  • Guidance for migrating Markdoc to Starlight and debugging content transformations.
  • Validation and best-practice guidelines to fix documentation site issues.

Quick Start

Update nx.dev docs by converting Markdoc pages to Starlight format and validating the output.

Frequently Asked Questions about nx-docs-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Markdoc content to Starlight for nx.dev documentation?

Migrating Markdoc content to Starlight for nx.dev documentation involves transforming page structures and validating content transformations to ensure format consistency. This process enforces frontmatter with a name and description while using the body for operational instructions.

What is the required frontmatter format for nx.dev docs pages?

The required frontmatter format for nx.dev docs pages mandates a name and description. This standardization ensures high-quality, consistent documentation across all pages by moving operational instructions into the body.

How do I fix content transformation issues when updating nx.dev documentation?

Fixing content transformation issues when updating nx.dev documentation requires debugging the Markdoc to Starlight conversion process. It enforces strict frontmatter validation and body content guidelines to resolve inconsistencies and maintain site quality.

Does the nx-docs-writer approach work for debugging existing Starlight documentation sites?

Yes, the nx-docs-writer approach works for debugging existing Starlight documentation sites by validating best-practice guidelines and fixing site issues. It ensures standardized content transformations and frontmatter consistency across nx.dev pages.

What is the best way to maintain consistency across nx.dev documentation pages?

The best way to maintain consistency across nx.dev documentation pages is enforcing frontmatter with a name and description while using the body for operational instructions. This standardizes writing, editing, and migration from Markdoc to Starlight.