Use when a client-facing guide to an existing product is wanted — a complete, non-technical, screenshot-backed explanation of every user type, screen, workflow, and admin/CMS module, built from the running application. Asks the blocking questions first, explores the real app, captures genuine screenshots, then produces the Markdown guide and, if requested, a PDF, a presentation artifact, and a separate end-user guide. Documents what exists; never invents.
Turn a running product into a package a non-technical client can read without a developer: what the product is, who uses it, and how every workflow works — shown with real screenshots. One run, whole project.
This is product and user-flow documentation, not a developer handover. It differs from application-documentation (per-screen reference for the team, in docs/) and documentation (the .ai/ record). It may read their output, never restates it.
When to Use
A client, stakeholder, or buyer must understand the product as it exists today.
Handover, launch, onboarding of a customer's staff, or a sales/acceptance review.
The product has a reachable running build (local, staging, or approved test environment).
Not for planned features, API/architecture docs, or code audits.
Inputs
The running application(s) and an approved test environment with safe test accounts (one per user role).
.ai/projects/current/ and the repo's existing docs / artifacts conventions.
The answers to the questions below.
Discovery Questions (ask first — before any exploring or writing)
Ask these in one message, with a recommended default for each so the user can answer "defaults". Do not start work until answered or defaults are confirmed.
Product and audience — Which product, and who reads this (client owner, their staff, end users)? Their technical level?
Environment — Where does the app run (URLs, build, simulator/device), and which test accounts exist per role? Are any surfaces unreachable (e.g. a mobile build, payment, email)?
Surfaces and roles in scope — Mobile, desktop, web, CMS/admin, company/team features? Any role or area to exclude?
Formats — Markdown guide with screenshots is always produced. Also wanted: PDF? Presentation artifact? Separate end-user guide? (Default: Markdown only.)
Branding and language — Client name/logo, tone, language, length preference? Anything confidential to obscure beyond passwords and tokens?
State the assumptions you proceed on if an answer is missing. Environment gaps become entries in the limitations list, not silent omissions.
Required Workflow
Ask the discovery questions; record answers and assumptions (confirmed / assumptions / questions).
Locate conventions — existing artifacts/docs folder, naming, any prior guide. Match them (application-documentation).
Inventory the product from the app, not the code: surfaces, navigation, roles, settings, integrations. Write a coverage checklist of every screen, menu, tab, modal, form, and action found. Read code or configuration only to find routes, roles, and labels; never to describe behavior you did not observe.
Drive the real app (browser or simulator; run / playwright-e2e / maestro-e2e for the mechanics) with safe test data. Walk each workflow per role: start screen → navigation → form → action → result, including errors and restricted access. Do not modify product behavior.
Capture screenshots as you go — one per step that matters, per role where the interface differs. Name them meaningfully (individual-03-create-account-form.png), keep them beside the guide that uses them, obscure secrets and personal data, and check each is readable.
Write the guide for the audience (below). Verify each written step against what you saw.
Produce requested formats — PDF and/or presentation from the finished Markdown, using the Artifact tool or the project's existing convention; a separate end-user guide with only the end-user roles' content.
Review against the checklist; fix gaps; list limitations and open questions.
Hand over a short summary: location, sections, roles and surfaces covered, screenshot count, unverified items, questions for the client.
The Package
Under the confirmed location, client-guide/:
client-guide/
├── README.md # main document: product overview, how parts fit, who sees what, how to read this guide
├── <role-or-area>.md # one per user type / surface that exists (individual, company admin, employee, CMS admin …)
├── configuration.md # themes, branding, settings — only if they exist
├── capture-and-media.md # only if capture/media features exist
├── limitations-and-questions.md
├── coverage.md # final overview: what is covered, by role and surface
└── screenshots/ # real captures, meaningful filenames
Sections are discovered, not templated. Create a file only for what exists; the names above are examples. Add files for anything found that fits none of them.
Writing Rules
Plain, professional English; explain every term the first time; use the actual labels shown in the app.
Per feature: what it is for, numbered steps, what the user sees next, restrictions, alternative outcomes (errors, no access).
Distinguish roles clearly; where two roles see different screens, show both.
Screenshot beside its step, with a caption saying what it demonstrates.
Cross-link related workflows.
No code, endpoints, schemas, repo structure, setup steps, or infrastructure.
Decision Rules
If a workflow cannot be reached or verified → say so in limitations-and-questions.md, with whether it is a product limitation or an environment/testing limitation. Never fabricate a screenshot or claim it works.
If a feature is in code but not reachable in the app → record as unverified; do not describe it as available.
If a screen is planned or stubbed → list as "not yet available" or omit with a note; never present it as working.
If behavior is ambiguous → record a question for the client; do not guess a business rule.
If a real record, token, or password would appear → use test data or obscure it before saving.
If the convention already has an artifacts location → use it; do not invent a structure.
Rules
Document the product as it is today. No planned functionality, no idealized flows.
Screenshots are genuine captures. No mockups, edits that change content, or re-drawn screens; redaction only.
Test data only; no secrets, tokens, or private customer information (../../system/SECURITY_RULES.md).
Do not change application code or data to make the guide easier; test-data changes made through the product are fine.
Do not commit or push without approval (../../system/GIT_WORKFLOW_RULES.md).
Anti-Patterns
Writing from the first few screens or from the code, then "filling in" the rest.
Mockups or imagined screens standing in for captures.
A developer handover in client clothing: routes, tables, components, setup.
Silent omissions — inaccessible areas not mentioned anywhere.
One generic "admin" section when the CMS has distinct modules.
Screenshots dumped in one folder, uncaptioned, named image1.png.
Starting before the formats, roles, and environment are confirmed.
Coverage checklist exists and every item is documented or listed as a limitation.
Every user type and surface in scope has its own section.
Every CMS/admin module explored: purpose, who uses it, data shown, actions, search/filter, results, limits.
Major workflows: start screen, navigation, form, action, result — each with a screenshot.
Screenshots genuine, readable, captioned, named meaningfully, placed beside the steps; secrets obscured.
Written steps verified against the running app; labels match.
Roles with different interfaces have separate screenshots.
Limitations and open questions listed; product vs environment limits distinguished.
No code, endpoints, schemas, or setup detail in the guide.
Requested extra formats produced (PDF / presentation / end-user guide) and match the Markdown.
coverage.md states what the guide covers and what it does not.
Definition of Done
A navigable package in the agreed location: a main document, one section per real user type and surface, configuration and media sections where they exist, real captioned screenshots beside the steps, a limitations-and-questions list, a coverage overview, and any requested PDF, presentation, or end-user guide — every claim verified against the running product or marked unverified.
Related Skills
application-documentation, documentation, playwright-e2e / maestro-e2e (driving the app), test-data-management, test-environment-management, ai-output-review (no invented facts), privacy-review (what to obscure), final-quality-audit.
Related Knowledge
../../knowledge/ (domain terms for consistent wording).
Related References
None required.
Context Loading Guidance
Requires: the answers, the running app, existing docs conventions.
Does not require: source code beyond finding routes/roles/labels, planning history, other skills' bodies.
May load:application-documentation (placement), playwright-e2e/maestro-e2e (driving).
Stop when: the package is reviewed and handed over.
Token Efficiency Guidance
Keep the coverage checklist as the single source of progress; write each section right after its workflow is captured, then discard the working notes. Use screenshots as evidence, not as text to re-describe. Delegate per-role exploration to parallel agents only with one shared checklist and filename convention (../../system/MULTI_AGENT_RULES.md).
1---2name: client-guide3description: Use when a client-facing guide to an existing product is wanted — a complete, non-technical, screenshot-backed explanation of every user type, screen, workflow, and admin/CMS module, built from the running application. Asks the blocking questions first, explores the real app, captures genuine screenshots, then produces the Markdown guide and, if requested, a PDF, a presentation artifact, and a separate end-user guide. Documents what exists; never invents.4metadata:5 source: https://skillmd.com/skills/ahtishamshahzad/client-guide6---78# Client Guide910## Purpose1112Turn a **running product** into a package a non-technical client can read without a developer: what the product is, who uses it, and how every workflow works — shown with real screenshots. One run, whole project.1314This is **product and user-flow documentation, not a developer handover**. It differs from `application-documentation` (per-screen reference for the team, in `docs/`) and `documentation` (the `.ai/` record). It may read their output, never restates it.1516## When to Use1718- A client, stakeholder, or buyer must understand the product as it exists today.19- Handover, launch, onboarding of a customer's staff, or a sales/acceptance review.20- The product has a reachable running build (local, staging, or approved test environment).21- **Not** for planned features, API/architecture docs, or code audits.2223## Inputs2425- The running application(s) and an **approved test environment** with safe test accounts (one per user role).26- `.ai/projects/current/` and the repo's existing docs / artifacts conventions.27- The answers to the questions below.2829## Discovery Questions (ask first — before any exploring or writing)3031Ask these in one message, with a recommended default for each so the user can answer "defaults". Do not start work until answered or defaults are confirmed.32331. **Product and audience** — Which product, and who reads this (client owner, their staff, end users)? Their technical level?342. **Environment** — Where does the app run (URLs, build, simulator/device), and which test accounts exist per role? Are any surfaces unreachable (e.g. a mobile build, payment, email)?353. **Surfaces and roles in scope** — Mobile, desktop, web, CMS/admin, company/team features? Any role or area to exclude?364. **Formats** — Markdown guide with screenshots is always produced. Also wanted: **PDF**? **Presentation artifact**? **Separate end-user guide**? (Default: Markdown only.)375. **Branding and language** — Client name/logo, tone, language, length preference? Anything confidential to obscure beyond passwords and tokens?386. **Output location** — Default: the repo's existing artifacts/docs convention; else `docs/client-guide/`. Confirm.3940State the assumptions you proceed on if an answer is missing. Environment gaps become entries in the limitations list, not silent omissions.4142## Required Workflow43441. **Ask** the discovery questions; record answers and assumptions (confirmed / assumptions / questions).452. **Locate conventions** — existing artifacts/docs folder, naming, any prior guide. Match them (`application-documentation`).463. **Inventory the product** from the app, not the code: surfaces, navigation, roles, settings, integrations. Write a coverage checklist of every screen, menu, tab, modal, form, and action found. Read code or configuration only to find routes, roles, and labels; never to describe behavior you did not observe.474. **Drive the real app** (browser or simulator; `run` / `playwright-e2e` / `maestro-e2e` for the mechanics) with safe test data. Walk each workflow per role: start screen → navigation → form → action → result, including errors and restricted access. Do not modify product behavior.485. **Capture screenshots as you go** — one per step that matters, per role where the interface differs. Name them meaningfully (`individual-03-create-account-form.png`), keep them beside the guide that uses them, obscure secrets and personal data, and check each is readable.496. **Write the guide** for the audience (below). Verify each written step against what you saw.507. **Produce requested formats** — PDF and/or presentation from the finished Markdown, using the Artifact tool or the project's existing convention; a separate end-user guide with only the end-user roles' content.518. **Review** against the checklist; fix gaps; list limitations and open questions.529. **Hand over** a short summary: location, sections, roles and surfaces covered, screenshot count, unverified items, questions for the client.5354## The Package5556Under the confirmed location, `client-guide/`:5758```59client-guide/60├── README.md # main document: product overview, how parts fit, who sees what, how to read this guide61├── <role-or-area>.md # one per user type / surface that exists (individual, company admin, employee, CMS admin …)62├── configuration.md # themes, branding, settings — only if they exist63├── capture-and-media.md # only if capture/media features exist64├── limitations-and-questions.md65├── coverage.md # final overview: what is covered, by role and surface66└── screenshots/ # real captures, meaningful filenames67```6869**Sections are discovered, not templated.** Create a file only for what exists; the names above are examples. Add files for anything found that fits none of them.7071## Writing Rules7273- Plain, professional English; explain every term the first time; use the **actual labels** shown in the app.74- Per feature: what it is for, numbered steps, what the user sees next, restrictions, alternative outcomes (errors, no access).75- Distinguish roles clearly; where two roles see different screens, show both.76- Screenshot beside its step, with a caption saying what it demonstrates.77- Cross-link related workflows.78- No code, endpoints, schemas, repo structure, setup steps, or infrastructure.7980## Decision Rules8182- If a workflow cannot be reached or verified → say so in `limitations-and-questions.md`, with whether it is a **product limitation** or an **environment/testing limitation**. Never fabricate a screenshot or claim it works.83- If a feature is in code but not reachable in the app → record as unverified; do not describe it as available.84- If a screen is planned or stubbed → list as "not yet available" or omit with a note; never present it as working.85- If behavior is ambiguous → record a question for the client; do not guess a business rule.86- If a real record, token, or password would appear → use test data or obscure it before saving.87- If the convention already has an artifacts location → use it; do not invent a structure.8889## Rules9091- Document the product as it is today. No planned functionality, no idealized flows.92- Screenshots are genuine captures. No mockups, edits that change content, or re-drawn screens; redaction only.93- Test data only; no secrets, tokens, or private customer information (`../../system/SECURITY_RULES.md`).94- Do not change application code or data to make the guide easier; test-data changes made through the product are fine.95- Do not commit or push without approval (`../../system/GIT_WORKFLOW_RULES.md`).9697## Anti-Patterns9899- Writing from the first few screens or from the code, then "filling in" the rest.100- Mockups or imagined screens standing in for captures.101- A developer handover in client clothing: routes, tables, components, setup.102- Silent omissions — inaccessible areas not mentioned anywhere.103- One generic "admin" section when the CMS has distinct modules.104- Screenshots dumped in one folder, uncaptioned, named `image1.png`.105- Starting before the formats, roles, and environment are confirmed.106107## Validation Checklist108109- [ ] Discovery answers (or confirmed defaults) recorded; assumptions listed.110- [ ] Coverage checklist exists and every item is documented or listed as a limitation.111- [ ] Every user type and surface in scope has its own section.112- [ ] Every CMS/admin module explored: purpose, who uses it, data shown, actions, search/filter, results, limits.113- [ ] Major workflows: start screen, navigation, form, action, result — each with a screenshot.114- [ ] Screenshots genuine, readable, captioned, named meaningfully, placed beside the steps; secrets obscured.115- [ ] Written steps verified against the running app; labels match.116- [ ] Roles with different interfaces have separate screenshots.117- [ ] Limitations and open questions listed; product vs environment limits distinguished.118- [ ] No code, endpoints, schemas, or setup detail in the guide.119- [ ] Requested extra formats produced (PDF / presentation / end-user guide) and match the Markdown.120- [ ] `coverage.md` states what the guide covers and what it does not.121122## Definition of Done123124A navigable package in the agreed location: a main document, one section per real user type and surface, configuration and media sections where they exist, real captioned screenshots beside the steps, a limitations-and-questions list, a coverage overview, and any requested PDF, presentation, or end-user guide — every claim verified against the running product or marked unverified.125126## Related Skills127128`application-documentation`, `documentation`, `playwright-e2e` / `maestro-e2e` (driving the app), `test-data-management`, `test-environment-management`, `ai-output-review` (no invented facts), `privacy-review` (what to obscure), `final-quality-audit`.129130## Related Knowledge131132`../../knowledge/` (domain terms for consistent wording).133134## Related References135136None required.137138## Context Loading Guidance139140- **Requires:** the answers, the running app, existing docs conventions.141- **Does not require:** source code beyond finding routes/roles/labels, planning history, other skills' bodies.142- **May load:** `application-documentation` (placement), `playwright-e2e`/`maestro-e2e` (driving).143- **Stop when:** the package is reviewed and handed over.144145## Token Efficiency Guidance146147Keep the coverage checklist as the single source of progress; write each section right after its workflow is captured, then discard the working notes. Use screenshots as evidence, not as text to re-describe. Delegate per-role exploration to parallel agents only with one shared checklist and filename convention (`../../system/MULTI_AGENT_RULES.md`).
Run npx get-skill add ahtishamshahzad/client-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Use when a client-facing guide to an existing product is wanted — a complete, non-technical, screenshot-backed explanation of every user type, screen, workflow, and admin/CMS module, built from the running application. Asks the blocking questions first, explores the real app, captures genuine screenshots, then produces the Markdown guide and, if requested, a PDF, a presentation artifact, and a separate end-user guide. Documents what exists; never invents. It is listed under Docs & Writing on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
ahtishamshahzad (@ahtishamshahzad) published this skill. Their other Agent Skills are listed on their SkillMD profile.