Enforce Diataxis-based documentation standards for Feat framework docs.
npx skills add https://github.com/smartboot/feat --skill feat-docs-writing
Please help me install this Agent Skill. Skill: feat-docs-writing Source: https://github.com/smartboot/feat/tree/main/.roo/skills/feat-docs-writing Command: npx skills add https://github.com/smartboot/feat --skill feat-docs-writing
This Skill ensures that all documentation for the Feat framework adheres to a consistent, high-quality standard, making it easier for developers to understand and use the framework.
Apply the feat-docs-writing skill to ensure the documentation for the new Feat Cloud controller feature follows the established standards.
High-intent search queries and answers about installing and using this skill.
To structure Feat documentation using the Diataxis framework, organize content into four distinct types: tutorials, how-to guides, explanations, and references. This approach enforces content boundaries, prevents duplication, and ensures information is presented logically and progressively.
Code examples in Feat technical writing must be functional, JDK 8 compatible, and sourced from reliable modules. Standardizing code examples ensures developers can successfully understand and implement the Feat framework without encountering environment or syntax errors.
New documentation files for the Feat framework should be placed within the `pages/src/content/docs` directory. Organizing content in this specific location allows the documentation standards skill to enforce formatting, content boundaries, and code example quality across the project.
Yes, the Feat documentation standard supports asynchronous programming guides by helping structure the content, verifying code example correctness, and linking appropriately to related concepts like the event loop. This ensures complex asynchronous topics are explained clearly and logically.
To prevent content duplication when writing Feat framework guides, enforce strict content boundaries based on the Diataxis framework. This ensures information is presented logically and progressively, separating learning-oriented tutorials from problem-solving how-to guides and reference material.
spencerbeggsCreate standardized RSPress documentation page scaffolds with frontmatter defaults under docs/src/en.
m16khbValidate generated components against schema and quality metrics with auto-fix suggestions.
channgGenerate static documentation websites from markdown files with sidebar navigation.
coroborosCorrect grammar and spelling in Markdown and documentation files.
