doc

Write, update, audit, and status documentation across five Skaile Dev doc surfaces.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill doc-skaile-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc
Source: https://github.com/skaile-ai/ai-assets/tree/main/skaile-development/skills/doc
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill doc-skaile-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps teams create, maintain, and verify documentation across the skaile-dev monorepo, ensuring coverage of all five doc surfaces (READMEs, CLAUDE.md, Starlight pages, DOMAIN.md / SKILL.md, and _devlog) and preventing drift between code and docs.

Core Features & Use Cases

  • Supports writing new docs for undocumented code, updating stale pages after code changes, and auditing gaps across packages.
  • Manages all five documentation tiers (README.md, CLAUDE.md, Starlight docs, DOMAIN.md / SKILL.md, and _devlog) and coordinates with helper scripts (doc-tracker, doc-audit, doc-status) to keep surfaces in sync.
  • Provides a three-mode workflow (write/update/audit/status) and guidance for validating frontmatter, sources, and page registration.

Quick Start

Run the doc skill in the required mode for a specific target or package.

Frequently Asked Questions about doc

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

FAQPage Schema
How do I keep monorepo documentation in sync with code changes?

To keep monorepo documentation in sync with code changes, you run an update mode that identifies stale pages and coordinates with helper scripts to update surfaces. This prevents drift between code and docs across all five documentation tiers.

What are the best ways to audit documentation gaps across a monorepo?

Auditing documentation gaps across a monorepo involves running a status mode that validates frontmatter and checks page registration. This process identifies undocumented code and tracks coverage across README, CLAUDE, and Starlight surfaces.

How do I write new documentation for undocumented code in a monorepo?

Writing new documentation for undocumented code requires a write mode that creates and registers pages across five doc surfaces. It validates frontmatter and coordinates with tracking scripts to ensure the new documentation is accessible and properly synced.

Does the docs workflow support Starlight pages and frontmatter validation?

Yes, the docs workflow supports Starlight pages and frontmatter validation. It updates Starlight documentation specifically to keep content in sync with code, while validating frontmatter to maintain consistency across the monorepo's documentation surfaces.

When should I run a documentation audit instead of a standard update?

You should run a documentation audit instead of a standard update when you need to verify overall coverage and find undocumented packages. While updates fix specific stale pages, auditing uses status scripts to comprehensively check for gaps across all five doc surfaces.