Enforce Diátaxis four-category documentation layouts in Datarim-managed repositories.
npx skills add https://github.com/Arcanada-one/datarim --skill diataxis-docs
Please help me install this Agent Skill. Skill: diataxis-docs Source: https://github.com/Arcanada-one/datarim/tree/main/skills/diataxis-docs Command: npx skills add https://github.com/Arcanada-one/datarim --skill diataxis-docs
It prevents inconsistent, hard-to-navigate documentation by enforcing a strict Diátaxis taxonomy and file layout across tutorials, how-to guides, reference docs, and explanations.
docs/ layout with the four Diátaxis categories and required category README.md stubs.Ask the AI to run the Diátaxis docs mandate for your project and report any missing or miscategorized documentation files.
High-intent search queries and answers about installing and using this skill.
The Diátaxis taxonomy solves inconsistent documentation by enforcing a strict four-category layout: tutorials, how-to guides, reference docs, and explanations. It eliminates anti-patterns like FAQ pages or examples folders by requiring every document to map to exactly one orthogonal category.
Auditing a docs site for Diátaxis compliance involves running a surface verification process that scans your filesystem for missing or miscategorized files. It checks for the mandated four-category layout and required README stubs, identifying structural drift during optimization or archival workflows.
Yes, the Diátaxis docs mandate is stack-agnostic and works with any static site generator or CMS. It enforces a taxonomy layout without tying the mandate to any specific platform, ensuring documentation structure remains consistent regardless of your underlying technology.
You should avoid FAQ pages or examples as separate categories because they create structural drift and break taxonomy orthogonality. The Diátaxis framework treats these as anti-patterns, requiring every document to map to exactly one of the four core categories instead of creating additional buckets.
The best way to prevent documentation drift during project scaffolding is to enforce the Diátaxis taxonomy layout from the start. This creates a standardized docs structure with required category README stubs, ensuring every file maps to one of the four orthogonal categories before content is added.
Yes, you can use the Diátaxis taxonomy for archive-time surface verification. The process validates that public pages conform to the mandated four-category layout, helping operators identify and correct any repos or sites missing the required documentation structure before archiving.
az9713Initialize a project with dark code prevention directories, CLAUDE.md section, and baseline audit.
lagz0neAudit C3 architecture documentation against the actual codebase.
dt418Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.
mahamaneharouna9-cpuAnalyze markdown documentation structure and cohesion against Diátaxis frameworks.