$pwd:

documentation

Name: Documentation
Author: joe-butler-23

// Technical documentation creation and improvement with emphasis on clarity, conciseness, and maximum communication efficiency. Use for README files, API docs, project documentation, code comments, and any written content. Prioritizes brevity over verbosity, essential information over comprehensive detail, and immediate usefulness over exhaustive coverage.

$ git log --oneline --stat

stars:0

forks:0

updated:December 15, 2025 at 15:40

SKILL.md

readonly

package.json

"author": "joe-butler-23"

"repository": "joe-butler-23/nix-config"

$ git clone

$ download --local

[HINT] Laden Sie das komplette Skill-Verzeichnis einschließlich SKILL.md und aller zugehörigen Dateien herunter

related-imports.ts

// Verwandte Skills

import docs-architect

from "amo-tech-ai"

import documentation-standards

import moai-project-documentation

from "modu-ai"

310

import documentation-criteria

import writing-documentation-with-diataxis

from "sammcj"

import nav-sop

from "alekspetrov"

import internal-linking-optimizer

from "aaron-he-zhu"

import documentation-criteria

from "shinpr"

import decisions

from "maragudk"

import competitor-content-analyzer

from "OneWave-AI"

documentation

Documentation Skill

Efficient technical documentation should communicate maximum value with minimum words.

Core Principles

Clarity First: Every sentence must add value. Remove redundancy, filler words, and unnecessary explanations.

Structure: Good documentation is impeccably structured. Most important info appears the top of the document, Lead with actionable information. Duplication is avoided at all costs.

Essential Only: Include what users actually need. Skip background, philosophy, and tangential information unless directly relevant.

Good writing is clear and concise. Avoid verbosity: do not write 3 documents where 1 would suffice, do not write a pargraph where a sentence would suffice.

Efficiency is kindness to your users.

name	documentation
description	Technical documentation creation and improvement with emphasis on clarity, conciseness, and maximum communication efficiency. Use for README files, API docs, project documentation, code comments, and any written content. Prioritizes brevity over verbosity, essential information over comprehensive detail, and immediate usefulness over exhaustive coverage.