documentation

Generate clear, well-structured documentation with enforced frontmatter and SEO best practices.

22|3|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/kubb-labs/fabric --skill documentation-kubb-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/kubb-labs/fabric/tree/main/.skills/documentation
Command: npx skills add https://github.com/kubb-labs/fabric --skill documentation-kubb-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The documentation skill provides a structured style guide to ensure clear, grammatically correct writing for Kubb documentation, helping teams produce consistent, readable content.

Core Features & Use Cases

  • Writing Style Guide: Active voice, present tense, grammatically correct prose.
  • Content Patterns: Templates and structures for blog posts, API docs, and guides.
  • SEO & Readability: Guidance to optimize content for search and developer comprehension.

Quick Start

Tell the AI to write a new documentation page following the provided style guide, including frontmatter and a 2–3 paragraph opening, using proper grammar and tone.

Frequently Asked Questions about documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write documentation that follows consistent writing patterns and grammar rules?

To write documentation with consistent grammar, generate content using active voice and present tense while applying predefined writing patterns and templates for blog posts, API docs, and guides to ensure readability.

What's the best way to generate API reference docs and tutorials with proper frontmatter?

Generate API reference docs and tutorials by enforcing frontmatter definitions alongside SEO best practices, producing ready-to-publish pages with proper grammar, formatting, and a consistent voice.

How do I optimize documentation content for SEO and developer comprehension?

Optimize documentation for SEO and developer comprehension by applying structured content patterns and writing-style guidance, generating clear prose with active voice and present tense that ranks well and educates readers.

Can I use this for blog posts and guides, or is it only for API references?

Yes, you can use it for blog posts and guides as well as API references, because it provides templates and structures across all these formats to maintain a consistent voice and formatting throughout your content.

What writing style should I apply to ensure clear, grammatically correct documentation?

Apply a writing style using active voice, present tense, and grammatically correct prose to ensure your documentation remains clear, readable, and consistent across all generated pages.

Why does my generated documentation lack consistent formatting and frontmatter?

Documentation lacks consistent formatting when frontmatter definitions and writing-pattern guidance are not enforced, which this approach solves by applying structured style rules to produce ready-to-publish content.