Standardize retikz example documentation with six-section pages and step demos.
npx skills add https://github.com/Pionpill/retikz --skill docs-doc-example
Please help me install this Agent Skill. Skill: docs-doc-example Source: https://github.com/Pionpill/retikz/tree/main/.agents/skills/docs-doc-example Command: npx skills add https://github.com/Pionpill/retikz --skill docs-doc-example
It standardizes how retikz “examples” pages are written so readers can follow a clear, reproducible learning path rather than getting lost in inconsistent structure.
Ask an AI to draft a new retikz example page that follows the docs-doc-example 6-section skeleton and generates cumulative step demos named <id>-NN-<theme>.demo.tsx.
High-intent search queries and answers about installing and using this skill.
To write reproducible step-by-step example documentation, use a fixed 6-section structure with an intro, prompt, process steps, capabilities, limitations, and related sections. This enforces strict formatting and consistent YAML frontmatter for content discovery.
A standard retikz example page features a fixed 6-section layout with a hero intro, an ExamplePrompt pattern, and teaching-first process steps. It uses TOC-ready H3 step headings and cumulative demo file naming rules for clear step-by-step learning.
Name demo files for step-by-step learning guides using the cumulative naming convention <id>-NN-<theme>.demo.tsx. This strict demo naming rule ensures readers can easily follow and reproduce each instructional diagram construction step.
No, you should keep TikZ comparisons isolated to dedicated mechanisms within the documentation. The standardized process steps enforce a strict 4-line Step format focused on instructional flow, preventing mixed content from disrupting the learning path.
Yes, YAML frontmatter is a required element for MDX example documentation. Enforcing this frontmatter ensures proper page discovery and allows the standardized 6-section instructional content to be consistently indexed and accessed.
zenobi-usAutomate API documentation creation and maintenance with OpenAPI integration.
TheBushidoCollectiveGenerate Storybook component documentation with autodocs, MDX pages, and JSDoc comments.
mkusakaCreate step-by-step explainer artifacts with structured templates and visual aids.
tianjianjiangDefine standard XML tags for AI prompts and documentation.
