document-writer

Enforce Storyblok documentation style, structure, and spelling standards.

60|40|Updated May 19, 2025
One-click install
npx skills add https://github.com/storyblok/monoblok --skill document-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: document-writer
Source: https://github.com/storyblok/monoblok/tree/main/.claude/skills/document-writer
Command: npx skills add https://github.com/storyblok/monoblok --skill document-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a centralized writing style guide and content structure patterns to ensure consistency and quality across Storyblok DX documentation.

Core Features & Use Cases

  • Writing Style Guide: Defines voice, tone, and terminology for all docs.
  • Voice & Perspective: Enforces active voice, imperative mood, third-person descriptions, and plain language.
  • Spelling and Capitalization: Standard American spellings and consistent casing for headings, code, and URLs.
  • Structure Guidance: Prescribes headings, lists, and a consistent Quick Start pattern for tasks.
  • Use Case: For example, when authoring a new documentation page, apply the guide to maintain a uniform style.

Quick Start

Draft a new documentation page for a Storyblok feature using the guide's voice, terminology, and structure rules.

Frequently Asked Questions about document-writer

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

FAQPage Schema
How do I maintain consistent documentation style across Storyblok projects?▼

To maintain consistent documentation style across Storyblok projects, apply a centralized writing guide that enforces frontmatter structure, voice, terminology, and spelling standards for all docs. This ensures uniform quality without requiring external tooling.

What voice and perspective should I use for Storyblok documentation?▼

Storyblok documentation should use active voice, imperative mood, third-person descriptions, and plain language. Following these voice and perspective rules ensures clarity and consistency across all content.

Do I need external tools or dependencies to enforce documentation structure?▼

No, you do not need external tools or dependencies to enforce documentation structure. The guide provides built-in rules for headings, lists, and a consistent Quick Start pattern for tasks directly within your workflow.

What are the spelling and capitalization standards for Storyblok docs?▼

The spelling and capitalization standards for Storyblok docs require standard American spellings and consistent casing for headings, code, and URLs. This maintains professional and uniform content formatting.

How do I structure a new documentation page for a Storyblok feature?▼

To structure a new documentation page for a Storyblok feature, use the prescribed headings, lists, and a consistent Quick Start pattern. This structure guidance ensures all task pages follow the same layout.

What's the best way to standardize READMEs and related content in Storyblok?▼

The best way to standardize READMEs and related content in Storyblok is to apply a centralized writing style guide. This enforces defined frontmatter, voice, and style rules to solve the problem of inconsistent documentation.