app-docs

Generates user documentation for web apps by browsing screens and capturing annotated screenshots.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill app-docs-scsm-unrestrict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-docs
Source: https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent/tree/main/frontend-engineer/skills/app-docs
Command: npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill app-docs-scsm-unrestrict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing user documentation for a web application is slow and quickly goes stale: someone must manually click through every page, take screenshots, and write step-by-step instructions. This Skill automates that process by browsing the running app via browser automation, screenshotting every screen, and producing a structured, publishable user guide. ## Core Features & Use Cases - Automated App Walkthrough: Uses Chrome MCP, Playwright MCP, or playwright-cli to discover all routes, navigate pages, and capture consistent 1280x720 screenshots with realistic data. - Four Documentation Depths: Choose quick (~10 screenshots, quick-start guide), standard (~30, full user guide), thorough (~80+, all states and flows), or exhaustive (~150+, publishable suite with admin guide, FAQ, and HTML version). - Structured Output: Produces GitHub-flavored Markdown with per-page sections, how-to workflows, keyboard shortcut tables, troubleshooting, workflow diagrams, and an optional self-contained HTML version. - Use Case: After shipping a new client-management dashboard, run the skill at standard depth to produce a complete USER_GUIDE.md with annotated screenshots of every page and CRUD workflow, ready to commit to the repo or hand to clients. ## Quick Start Ask the agent to document your running app at a given URL, for example: generate a standard-depth user guide with screenshots for the app running at http://localhost:3000.

Frequently Asked Questions about app-docs

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

FAQPage Schema
How do I generate a user guide with screenshots for my web app?

Point the skill at your running app's URL and choose a depth level. It navigates every route via browser automation, captures consistent screenshots, and writes a structured Markdown guide with step-by-step workflows and annotated images.

What browser automation tools does app documentation generation use?

It supports Chrome MCP, Playwright MCP, or playwright-cli, detected the same way as the ux-audit skill. Chrome MCP reuses your existing browser session, while Playwright requires you to provide login credentials for authenticated apps.

Can it document apps that require login?

Yes. With Chrome MCP it uses your existing authenticated session, so no extra setup is needed. With Playwright-based tools you must supply credentials so the automation can log in before capturing screens.

What is the difference between quick, standard, thorough, and exhaustive documentation depth?

Quick captures about 10 key screens for a one-page quick-start. Standard covers all pages and primary workflows. Thorough adds empty states, error states, mobile views, and every CRUD flow. Exhaustive adds tutorials, an admin guide, FAQ, and an HTML version.

Does the skill produce HTML documentation or only Markdown?

Markdown is the default output, written to docs/USER_GUIDE.md with relative screenshot paths. A self-contained HTML version with a table-of-contents sidebar, print CSS, and dark mode is produced at exhaustive depth or on request.