Skip to main content
skill CX Codex

user-guide-creation — Claude Code skill: user guides and tutorials

A skill for writing user guides, tutorials and step-by-step instructions with screenshots and examples. Useful when a product needs documentation.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add aj-geddes/useful-ai-prompts --skill user-guide-creation -a claude-code
Open on GitHub

What user-guide-creation does

The skill lays out the structure of user documentation: table of contents, introduction, getting started, key features, common tasks, troubleshooting and FAQ. It ships a minimal working markdown example to start from, plus a references/ directory with separate files on system requirements, installation, initial setup and three tasks: creating your first project, importing existing data, exporting data.

Style rules are part of it too. Plain language, screenshots, numbered lists for sequential steps, tips and warnings, keyboard shortcuts, more than one path to a task. A matching don't-list covers jargon without explanation, skipped steps, outdated screenshots and wall-of-text paragraphs.

Six platforms are supported, among them Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Install runs through npx skills add, or gh skill install for GitHub Copilot. Nothing beyond the skill file is needed, but you still have to test every step you document — the skill writes the text, it does not verify the product.

What it helps with

  • turn scattered notes into a user manual
  • write a step-by-step how-to for a new feature
  • draft a getting started guide for a product
  • add a troubleshooting section to existing docs
  • rewrite a wall of text into numbered steps

Example prompts for the agent

  • Write a user guide for our CLI tool, start with a table of contents and a Getting Started section
  • Draft a step-by-step tutorial for importing data, include tips and warnings
  • Rework this documentation: split it into steps, add an FAQ and a troubleshooting section

How to install user-guide-creation

1Skills CLI (Vercel)

npx skills add aj-geddes/useful-ai-prompts --skill user-guide-creation -a claude-code

2Manually: put the files in place

~/.claude/skills/user-guide-creation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/user-guide-creation/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about user-guide-creation

How do I install user-guide-creation in Claude?

Run npx skills add aj-geddes/useful-ai-prompts --skill user-guide-creation -a claude-code. The skill file lands at ~/.claude/skills/user-guide-creation/SKILL.md.

What does user-guide-creation do?

It helps write user guides, tutorials and step-by-step instructions. You get a document structure and style rules, including how to handle screenshots and examples.

Which platforms does this skill support?

Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Each platform has its own install command; for GitHub Copilot it is gh skill install aj-geddes/useful-ai-prompts user-guide-creation.

Source text

SKILL.md · MIT
---
name: user-guide-creation
description: >
  Create comprehensive user guides, tutorials, how-to documentation, and
  step-by-step instructions with screenshots and examples. Use when writing user
  documentation, tutorials, or getting started guides.
---

# User Guide Creation

## Table of Contents

- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)

## Overview

Create clear, user-friendly documentation that helps users understand and effectively use your product, with step-by-step instructions, screenshots, and practical examples.

## When to Use

- Product user manuals
- Getting started guides
- Feature tutorials
- Step-by-step how-tos
- Video script documentation
- Interactive walkthroughs
- Quick start guides
- FAQ documentation
- Best practices guides

## Quick Start

Minimal working example:

````markdown
# [Product Name] User Guide

## Table of Contents

1. [Introduction](#introduction)
2. [Getting Started](#getting-started)
3. [Key Features](#key-features)
4. [Common Tasks](#common-tasks)
5. [Troubleshooting](#troubleshooting)
6. [FAQ](#faq)
7. [Support](#support)

## Introduction

### What is [Product Name]?

[Product Name] is a [brief description of what the product does and its main purpose].

### Who is this guide for?

This guide is designed for:

- New users getting started with [Product Name]
- Existing users looking to learn advanced features
- Administrators managing [Product Name]
// ... (see reference guides for full implementation)
```

## Reference Guides

Detailed implementations in the `references/` directory:

| Guide | Contents |
|---|---|
| [System Requirements](references/system-requirements.md) | System Requirements |
| [Installation](references/installation.md) | Installation |
| [Initial Setup](references/initial-setup.md) | Initial Setup |
| [Task 1: Creating Your First Project](references/task-1-creating-your-first-project.md) | Task 1: Creating Your First Project |
| [Task 2: Importing Existing Data](references/task-2-importing-existing-data.md) | Task 2: Importing Existing Data |
| [Task 3: Exporting Data](references/task-3-exporting-data.md) | Task 3: Exporting Data |

## Best Practices

### ✅ DO

- Use simple, clear language
- Include screenshots and visuals
- Provide step-by-step instructions
- Use numbered lists for sequential tasks
- Add tips, warnings, and notes
- Include keyboard shortcuts
- Provide multiple paths to accomplish tasks
- Test every step you document
- Keep content up-to-date
- Use consistent formatting
- Add a table of contents for long guides
- Include search functionality

### ❌ DON'T

- Use jargon without explanation
- Assume prior knowledge
- Skip important steps
- Use outdated screenshots
- Write wall-of-text paragraphs
- Forget to update for new versions
- Overcomplicate simple tasks

© aj-geddes · MIT · aj-geddes/useful-ai-prompts

Similar skills

Everything for Writing and docs →

From the same set118

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor