Documentation system archetype for marketing, sales, and go-to-market docs — awareness, messaging, and audience language. Use when authoring or organizing marketing, sales, GTM, positioning, or messaging documentation; keep each shard under progressive…
Documentation system archetype for OSS libraries (npm, PyPI, crates.io): keep package docs maintainable as APIs and ideas evolve — source holds API truth; Markdown shards hold intent, stability promises, and migration notes. Use when building a docs-as-code…
Documentation system archetype for product docs sites (MkDocs, Docusaurus, VitePress): keep human-facing docs maintainable as features keep shipping — MDCP shards stay the authoring source of truth, site generators publish downstream. Use when building…
MDCP Helper: Act as an expert Systems Architect to draft and design system architecture using MDCP shards.
Use when the work item is documentation-only: authoring or refactoring MDCP shards, fixing stale client/feature/developer docs, removing planning backlogs from durable shards, or when the user asks for a technical-writer pass without product-code changes.
MDCP Helper: Act as an expert Software Engineer to implement and document new features using MDCP shards.
Use when bootstrapping MDCP in a greenfield or brownfield repository, first-time setup of sharded docs, migrating legacy markdown into MDCP guides, getting started with an MDCP documentation pipeline, or onboarding onto MDCP helper skills for a first feature.
Documentation system Agent Skill for MDCP (MarkDown Context Protocol): keep specs, architecture notes, and product ideas in small Markdown shards so docs stay maintainable as ideas keep arriving. Teaches agents docs-as-code discipline — update shards before…