app-docs

# App Documentation Generator Browse a running web app, screenshot every screen, and produce documentation good enough to publish. Not a screenshot dump — a structured guide that teaches someone how to use the app. ## Browser Tool Detection Same as ux-audit — Chrome MCP, Playwright MCP, or playwright-cli. ## URL Resolution Same as ux-audit — prefer deployed/live URL over localhost. ## Depth Levels | Depth | Screenshots | What it produces | Duration | |-------|------------|-----------------|----------| | **quick** | ~10 | Single-page quick-start guide. Key screens, happy path only. | 10-15 min | | **standard** | ~30 | Full user guide. All pages, primary workflows, reference tables. | 30-60 min | | **thorough** | ~80+ | Comprehensive guide. All states, mobile views, every CRUD flow, troubleshooting. | 1-3 hours | | **exhaustive** | ~150+ | Publishable documentation suite. Everything in thorough plus: getting started tutorial, feature-by-feature deep dives, admin guide, keyboard shortcut reference, FAQ, and HTML version. | 3-6 hours | Default: **standard** ## Workflow ### 1. Get App Details Ask the user: - **App URL** (required — or auto-detect from wrangler.jsonc / running dev server) - **App name** (for the guide title) - **Auth** — Chrome MCP uses their session; Playwright needs credentials - **Depth** — quick, standard, thorough, or exhaustive - **Audience** — who reads this? (end users, admins, new team members, clients) ### 2. Discover All Routes Navigate the ...