product-documentation

Product documentation standards covering user guides, feature documentation, release notes, and end-user communication

hack23/homepage58 installsApache-2.0Synced Aug 26

Works with

Claude CodeCursorCodex CLIGitHub CopilotGemini CLI
---
name: product-documentation
description: Product documentation standards covering user guides, feature documentation, release notes, and end-user communication
license: Apache-2.0
---

# Product Documentation Skill

## Purpose

Ensures product documentation is clear, comprehensive, and user-focused, helping users understand features, solve problems, and get maximum value from products.

## Rules

### Documentation Types

**User Guides (MUST HAVE):**
- Getting Started guide
- Feature documentation
- Troubleshooting guide
- FAQ
- Glossary

**Release Documentation:**
- Release notes (new features, bug fixes, breaking changes)
- Migration guides
- Upgrade instructions
- Deprecation notices

**Reference Documentation:**
- Feature specifications
- Configuration options
- Keyboard shortcuts / CLI commands
- System requirements

### Writing Standards

**MUST:**
- Use clear, concise language
- Write for the target audience (technical level)
- Use active voice ("Click Save" not "Save should be clicked")
- Include visuals (screenshots, diagrams, videos)
- Provide examples
- Keep up-to-date with product

**Structure:**
```markdown
# Feature Name

## Overview
[What it does and why it's useful]

## Prerequisites
[What users need before starting]

## How to Use
### Step 1: [Action]
[Detailed instructions with screenshots]

### Step 2: [Action]
[More instructions]

## Examples
[Real-world use cases]

## Troubleshooting
[Common problems and solutions]

## Related
[Links to related documentation]
```

## Examples

### Feature Documentation Template
```markdown
# Email Notifications

## Overview
Receive automatic email alerts when important events occur in your account.

## Setting Up Notifications

1. Go to **Settings** → **Notifications**
2. Toggle the events you want to be notified about
3. Verify your email address
4. Click **Save Preferences**

## Available Notification Types

- **Security Alerts**: Login attempts, password changes
- **System Updates**: Maintenance windows, feature releases
- **Account Activity**: Billing changes, user additions

## Troubleshooting

**Problem**: Not receiving notifications  
**Solution**: Check spam folder, verify email address

## Related
- [Email Configuration](./email-config.md)
- [Security Settings](./security.md)
```

## Related Policies

- [Documentation Portfolio SKILL](../../architecture/documentation-portfolio/SKILL.md)
- [Brand Voice & Tone SKILL](../../business/brand-voice-tone/SKILL.md)

## Related Documentation

- [hagbard-celine Agent](../../../agents/hagbard-celine.md)

More Writing & Documentation skills

paper-context-resolver

lllllllama/rigorpilot-skills

Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.

450.8k

repo-intake-and-plan

lllllllama/rigorpilot-skills

Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.

450.0k

minimal-run-and-audit

lllllllama/rigorpilot-skills

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

449.9k

← All Writing & Documentation skills

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY