# Walkthrough

Present final screenshots or rendered artifacts as an annotated walkthrough when visual...

- Repository: https://github.com/udecode/dotai (1161 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add udecode/dotai --skill walkthrough -g -a claude-code -y`
Codex: `npx skills add udecode/dotai --skill walkthrough -g -a codex -y`
Cursor: `npx skills add udecode/dotai --skill walkthrough -g -a cursor -y`
Gemini CLI: `npx skills add udecode/dotai --skill walkthrough -g -a gemini-cli -y`

## Description

Present final screenshots or rendered artifacts as an annotated walkthrough when visual evidence is requested.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Walkthrough

Explain a completed change with a few annotated visuals. Run this after final
verification. A walkthrough explains proof; it does not replace proof. Reuse the final verified frames. Do not repeat the browser walk or send a message to a customer or anyone outside the team without explicit authorization.

## Honor The Caller Contract

The caller decides whether the walkthrough is required. Follow the stricter
repo rule when one exists.

The caller chooses scope and whether an artifact is required. Workflow, docs, and backend changes do not create a visual obligation on their own.

When the caller requires a walkthrough and it cannot be produced, block
closeout with the exact missing tool, access, or artifact. Do not waive it
silently.

When the caller requires a diff check and no relevant UI or rendered-output
change exists, record:

```txt
Walkthrough: N/A, no UI or rendered-output change in this packet.
```

For a caller that requires a diff baseline, read [baseline.md](references/baseline.md) before the first mutation. It owns capture, comparison, and honest reconstruction.

## Read The Minimum Evidence

Read only what explains the completed result:

- the latest request and acceptance criteria;
- the baseline, diff receipt, and final diff;
- final screenshots or rendered proof already captured;
- the final route, role, data fixture, viewport, theme, or source artifact.

Reuse valid final-state screenshots. Do not rerun an expensive flow only to
capture the same state.

Show the inspected saved record, receipt, message, packet or final artifact,
not just a control that promises it. Reuse the verifier's recorded artifact
inspection when its source, identity, state and hash still match; open only
missing or stale evidence. When a preview and a downloadable/readable artifact
both exist, their material claims must agree. Report a contradiction as a
failure without repeating an already-proved operation just for presentation.

## Pick The Shortest Story

The rest: https://github.com/udecode/dotai/blob/HEAD/skills/walkthrough/SKILL.md