document-code
Update the documentation website for the Syncpack project.
Install
mkdir -p .claude/skills/document-code && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6848" && unzip -o skill.zip -d .claude/skills/document-code && rm skill.zipInstalls to .claude/skills/document-code
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Add and update the documentation website for Syncpack. Use when making user-facing changes to the codebase.Key capabilities
- →Generate documentation for Syncpack commands and configuration
- →Create and update MDX files for status codes and FAQs
- →Manage reusable partials and components for documentation
- →Verify internal link identifiers in astro.config.mjs
- →Validate documentation build locally
How it works
The skill maps source files like cli.rs and rcfile.rs to specific MDX documentation paths. It requires updating global reference links and verifying the site build using local development tools.
Inputs & outputs
When to use document-code
- →Update documentation for new features
- →Correct existing user-facing docs
- →Document codebase changes
About this skill
Document Code
Guide for adding and updating Syncpack's documentation website.
Quick Decision
What are you documenting?
| Adding/Updating... | Location |
|---|---|
| Command docs | site/src/content/docs/command/[cmd].mdx |
| Config property | site/src/content/docs/config/[prop].mdx |
| Version group variant | site/src/content/docs/version-groups/[var].mdx |
| Semver group variant | site/src/content/docs/semver-groups/[var].mdx |
| Status code | site/src/content/docs/status/[code].mdx |
| FAQ | site/src/faq/[id].mdx |
| Shared option partial | site/src/_partials/option/[opt].mdx |
| Reusable component | site/src/components/[name].astro |
Workflow
- Read source —
cli.rsfor commands,rcfile.rsfor config,instance_state.rsfor status codes - Create/update MDX — Match existing structure exactly
- Add link identifier — Update
globalReferenceLinksinastro.config.mjs - Test locally —
pnpm run devfromsite/ - Verify links — Check all
(IDENTIFIER)links resolve
Source to Docs Mapping
| Source | Documentation |
|---|---|
src/cli.rs Subcommand | site/src/content/docs/command/*.mdx |
src/rcfile.rs Rcfile | site/src/content/docs/config/*.mdx |
src/instance_state.rs | site/src/content/docs/status/*.mdx |
src/specifier.rs | site/src/content/docs/reference/specifier-types.mdx |
Local Development
cd site
pnpm run dev # Start at http://localhost:4321/syncpack
pnpm run build # Verify build succeeds
Site Overview
- Source located at
site/src/ - Built with Starlight on top of Astro
- Content at
site/src/content/docs/**/*.mdx - Reusable partials at
site/src/_partials/**/*.mdx - Reusable components at
site/src/components/*.astro
Command Documentation
Each command has a corresponding file at site/src/content/docs/command/[command].mdx.
Required Structure (in order)
- Description of the command's purpose from end user perspective
## Examples— Single bash code block with commented examples## Options— Start with<QuoteFilters />callout, then###for each option alphabetically (--helplast)
Shared Option Partials
Many commands share options. Define reusable partials at site/src/_partials/option/*.mdx:
import ConfigOption from "@partials/option/config.mdx";
<ConfigOption command="update" />
Config Documentation
Each config property has a file at site/src/content/docs/config/[property].mdx.
Required Structure
- Description of the config's purpose from end user perspective
## Default Value— Code block showing default (when applicable)## Examples— Code blocks with commented examples
Version Groups and Semver Groups
Each variant has its own page:
site/src/content/docs/version-groups/*.mdxsite/src/content/docs/semver-groups/*.mdx
Required Structure
- Description of the group's purpose from end user perspective
## Examples— Code block per example, capture novel use cases## Configuration—###for each config property
Status Code Documentation
Each status code has a file at site/src/content/docs/status/[code].mdx.
Reference page at site/src/content/docs/reference/status-codes.mdx explains the InstanceState enum and its nested enums (ValidInstance, InvalidInstance, SuspectInstance).
FAQ Documentation
- Create FAQ files at
site/src/faq/[id].mdx - Listed at
/syncpack/faqviasite/src/pages/faq.astro - Individual pages via
site/src/pages/faq/[id].astro
Linking Between Pages
Use named identifiers in markdown links:
When using the [update](COMMAND_UPDATE) command
Define identifiers in globalReferenceLinks function in site/astro.config.mjs.
Open Graph Images
Generated by site/src/pages/og/[...path].png.ts using Satori.
Troubleshooting
| Problem | Fix |
|---|---|
| Link not working | Check identifier in globalReferenceLinks |
| Partial not rendering | Verify import path uses @partials/ alias |
| OG image broken | Check og/[...path].png.ts handles new route |
| Build fails | Run pnpm run build locally to see error |
| Page not appearing in sidebar | Check frontmatter and Starlight config |
Checklist
Before submitting documentation:
- Structure matches existing pages of same type
- Link identifier added to
astro.config.mjs - Local dev server renders correctly
- Build succeeds (
pnpm run build) - All internal links resolve
When not to use it
- →When the documentation structure does not match existing patterns
- →When the build fails locally
Prerequisites
Limitations
- →Requires manual verification of link identifiers
- →Build must succeed locally for documentation to be valid
How it compares
Unlike manual documentation updates, this skill enforces a strict file structure and automated link validation to ensure consistency across the Syncpack site.
Compared to similar skills
document-code side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| document-code (this skill) | 1 | 4mo | Review | Intermediate |
| ml-paper-writing | 48 | 6mo | Review | Advanced |
| docs-review | 10 | 7mo | No flags | Beginner |
| claude-md-improver | 21 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by JamieMason
View all by JamieMason →You might also like
ml-paper-writing
davila7
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
docs-review
metabase
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
claude-md-improver
anthropics
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.
update-docs
vercel
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
wiki-architect
microsoft
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.