superpowers-writing-clearly-and-concisely

Enforce concise phrasing, active voice, and consistent punctuation in human-readable text.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/klaaay/spec-toolkit --skill superpowers-writing-clearly-and-concisely
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-writing-clearly-and-concisely
Source: https://github.com/klaaay/spec-toolkit/tree/main/apps/spec-kit-app/public/commands-packages/superpowers/skills/superpowers-writing-clearly-and-concisely
Command: npx skills add https://github.com/klaaay/spec-toolkit --skill superpowers-writing-clearly-and-concisely

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps writers apply a curated set of principles to any human-readable text—such as documents, commit messages, error prompts, explanations, reports, and UI copy—so the writing becomes clearer and more powerful.

Core Features & Use Cases

  • Basic rules: keep sentences short, choose active voice, and place the subject near the verb to avoid confusion.
  • Clarity techniques: use concrete details, remove filler words, and prefer specific numbers over vague terms.
  • Quick adaptation: apply these principles to reviews, drafts, user messages, and technical documentation to improve readability.

Quick Start

Apply these rules to your next document to improve clarity and reduce wordiness.

Frequently Asked Questions about superpowers-writing-clearly-and-concisely

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

FAQPage Schema
How do I improve writing clarity in technical documentation and UI copy?

To improve writing clarity, apply principles like active voice, short sentences, and placing subjects near verbs to ensure unambiguous communication in technical documentation and UI copy.

What is the best way to write concise commit messages and error prompts?

The best way to write concise commit messages and error prompts is to remove filler words, choose active voice, and prefer specific numbers over vague terms to eliminate wordiness.

How do I fix wordy sentences and inconsistent tense in my reports?

Fix wordy sentences and inconsistent tense in reports by enforcing rules for concise phrasing, consistent tense, and proper punctuation to improve overall readability.

Can I use a style guide approach to edit drafts and user messages for readability?

Yes, you can apply a style guide approach to edit drafts, user messages, and reviews by using concrete details and removing filler words to enhance text readability.

Does this writing approach support formatting PRs and technical explanations?

This writing approach supports PRs and technical explanations by enforcing concise phrasing and proper punctuation to ensure the communication remains unambiguous.

When should I not use concise phrasing techniques for human-readable text?

The metadata does not specify limitations on when to avoid concise phrasing techniques, but the approach targets general human-readable text where active voice and short sentences are preferred.