Convert stable ADRs into bilingual MDX docs with working demos.
npx skills add https://github.com/Pionpill/retikz --skill develop-document
Please help me install this Agent Skill. Skill: develop-document Source: https://github.com/Pionpill/retikz/tree/main/.agents/skills/develop-document Command: npx skills add https://github.com/Pionpill/retikz --skill develop-document
It solves the problem of turning a feature that already passes implementation and test into complete documentation that users can discover, understand, and try via working demos on the docs site.
Use the develop-document skill to generate the complete stage-4 documentation plan and checklist for an ADR, then delegate the actual MDX/demo/API/sidebar/i18n outputs to the docs-doc-principle pipeline and doc-skill sub-splits.
High-intent search queries and answers about installing and using this skill.
To convert an ADR into user-facing documentation, validate impacted existing pages and enforce a checklist for API table rows, preview examples, and bilingual MDX alignment. This ensures the resulting demos render the intended behavior correctly under pnpm dev:docs.
Generating bilingual MDX documentation requires validating zh/en structural alignment and synchronizing i18n keys. You must complete the mandatory checklist covering API table rows, sidebar registration, and demo file naming to ensure full bilingual completeness.
To ensure React demos run correctly after adding new component props, validate that all impacted existing pages under apps/docs/src/contents are updated. Enforce demo file naming conventions and confirm the demos execute properly under pnpm dev:docs.
Updating documentation for changed defaults or semantics requires sidebar and i18n registration. You must validate impacted pages, add API table rows, align bilingual MDX structure, and synchronize i18n keys to maintain documentation completeness.
You need to validate existing docs pages before writing new MDX content whenever an ADR introduces new IR fields, new components, or removed APIs. Reading relevant pages under apps/docs/src/contents first determines what to update, add, or omit for functional changes.
Yes, you can document removed APIs and changed semantics by applying the red, yellow, and green documentation stages. This process validates impacted pages, enforces a mandatory checklist for API tables and demos, and ensures bilingual alignment for the docs site.
innFactory-AICreate and register bilingual CompanyGPT documentation pages with frontmatter and sidebar mapping.
PionpillReview documentation pages for structure, readability, and consistency before release.
idealjsCreate Next.js MDX/TSX component demo pages with variants and visual regression tests.
lexmountEnforce bilingual parity and navigation consistency in Mintlify .mdx documentation.
