agent-docs-kit

Create or update Project Atlas and architecture MDX pages in an agent-docs-kit Fumadocs project. Use whenever the user asks for a project overview, architecture map, system shape, subsystem boundaries, data flow, runtime chain, contracts, ownership, onboarding map, refactor context, or architecture diagrams.

Record shipped changes in an agent-docs-kit Fumadocs project. Use after refactors, features, bug fixes, API or data-contract changes, architecture changes, migrations, deploy changes, or operational fixes that need an immutable paper trail.

Validate an agent-docs-kit Fumadocs project. Use before committing docs changes, after generated docs or glossary files change, or whenever the user asks whether the documentation system, MDX content, glossary, or agent-docs-kit setup is healthy.

Regenerate and review the glossary in an agent-docs-kit Fumadocs project. Use whenever MDX frontmatter terms were added, changed, duplicated, renamed, or need consistency cleanup before docs are committed.

Create or update future plans, blueprints, design direction, implementation plans, or proposal MDX pages in an agent-docs-kit Fumadocs project. Use when documenting intended work before it ships or when the user wants a plan separated from current architecture and shipped change records.

General entrypoint for creating or updating agent-docs-kit MDX documentation in a project initialized with agent-docs-kit. Use whenever the user asks to write docs, update docs, create a Project Atlas, explain current architecture, map a repo, record a shipped change, draft a future plan, refresh glossary terms, validate docs health, or maintain the generated Fumadocs documentation system.