doc-style

Apply documentation guidelines to write concise prose for API docs, manuals, and knowledge bases.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/liangmiQwQ/skills --skill doc-style-liangmiqwq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-style
Source: https://github.com/liangmiQwQ/skills/tree/main/my-skills/doc-style
Command: npx skills add https://github.com/liangmiQwQ/skills --skill doc-style-liangmiqwq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines for writing documentation and prose reduce cognitive load by encouraging clear, direct language and minimal formatting.

Core Features & Use Cases

  • Clear prose-first guidelines that prioritize readability over decorative formatting
  • Emoji and decorative element avoidance, with a directive to use simple language
  • Applicability to API docs, user manuals, and internal knowledge bases to maintain consistency

Quick Start

Draft a documentation page using concise prose and minimal formatting.

Frequently Asked Questions about doc-style

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

FAQPage Schema
How do I write clear documentation with concise prose?

Clear documentation uses direct language and minimal formatting to reduce cognitive load. Apply prose-first guidelines that prioritize readability over decorative elements, ensuring sentences remain straightforward and actionable for the reader.

What is the best way to format API docs and user manuals?

The best way to format API docs and user manuals is using simple sentences over heavy formatting. Maintain consistency across internal knowledge bases by avoiding emojis and decorative elements, focusing entirely on actionable writing instructions.

Does a good documentation style guide require minimal formatting?

A good documentation style guide requires minimal formatting to keep the focus on clear prose. By avoiding decorative elements and heavy structural markup, sentences deliver direct value and reduce the cognitive load for readers.

How do I draft an internal knowledge base page using simple language?

Draft an internal knowledge base page using concise prose and simple language. Start by defining the name and description in the frontmatter, then present actionable writing instructions in the body while intentionally avoiding emojis.

When should I avoid emojis in technical writing?

Avoid emojis in technical writing when following a minimal formatting philosophy for API docs or manuals. This directive keeps prose clear and direct, ensuring the documentation remains consistent and professional across internal knowledge bases.

Can I use heavy formatting for readability in documentation?

Heavy formatting should not be used for readability in documentation. Prose-first guidelines prioritize clear, direct sentences over decorative formatting to reduce cognitive load and maintain a consistent style across user manuals.