Examples

Start with the story you need to publish.

Each example begins with the visible result, explains what GuideShot proves, and lets you inspect the exact recipes that generated it.

Open annotation reference
3 recipes2 properties

Localization and themes

One connected guide expands into every declared language and color scheme. Change a matrix property to switch the published artifacts without recapturing the page.

Language
Theme
What you are seeing
A three-step release flow captured from the same product workspace.
What GuideShot proves
One recipe matrix publishes every requested language and color scheme.
What changes
The product copy, annotation copy, alt text, and theme change together.
The release form with its release notes field highlighted for review.

2 / 3

Review changes

Set the version, target, and notes before anything is published.

  1. 1Add the release details
  2. 2Review the release notes
3 recipes

Device-specific artifacts

Publish a wide desktop guide, a 4:3 tablet guide, and a portrait phone guide from explicit profiles and artifact ratios.

What you are seeing
The same workspace presented at desktop, tablet, and mobile sizes.
What GuideShot proves
The browser viewport and final artifact ratio are independent, validated contracts.
What changes
Navigation, density, intrinsic dimensions, and aspect ratio change by device.
The workspace captured with the desktop profile and persistent navigation.

1 / 3

Desktop profile

A 1280×960 browser viewport publishes a true 16:9 desktop artifact.

  1. 11920×1080 output
  2. 2Persistent navigation is visible
4 recipes

Authenticated and prepared state

Start with an isolated browser, install a synthetic session, perform a real action, and prove the result before capture.

What you are seeing
A public workspace, an authenticated workspace, and a projects list before and after filtering.
What GuideShot proves
Scenarios establish safe domain state while typed actions and readiness checks establish visible UI state.
What changes
Identity, workspace access, visible rows, and the verified confirmation change.
The Launch workspace loaded with the synthetic Alex Kim administrator session.

2 / 4

Install synthetic state

A reviewed scenario installs a synthetic user, role, and workspace before the page loads.

  1. 1Prepare the isolated session
  2. 2Verify the named workspace
5 recipes

Frame the right context

Choose the full viewport, complete page, one target, related targets, or an explicit region based on what the reader needs to understand.

What you are seeing
One revenue workspace published with five deliberate framing strategies.
What GuideShot proves
Stable target geometry replaces manual image cropping and keeps the requested ratio intact.
What changes
The amount of surrounding product context and the final artifact shape change.
The revenue trend panel framed as a focused widescreen artifact.

3 / 5

Focus on one product region

A stable target creates a focused widescreen artifact without a fragile crop.

  1. 1Resolve the revenue panel
  2. 2Expand to a 16:9 frame
1 recipe3 properties

Feature and role matrices

Generate only supported rollout, role, and plan combinations while keeping one explicit control baseline.

Rollout
Plan
Role
What you are seeing
A permissions panel whose available actions follow the selected audience.
What GuideShot proves
Matrix exclusions remove impossible states and an inclusion restores one reviewed baseline.
What changes
The rollout, role, plan, and resulting permissions change together.
Team permissions for a supported feature, role, and plan combination.

1 / 1

Publish only supported audiences

One recipe expands into the feature, role, and plan combinations the product actually supports.

  1. 1Exclude impossible combinations
  2. 2Include the explicit control baseline
4 recipes

Privacy and deterministic loading

Protect sensitive pixels before caching and wait for the exact loading or ready state the guide intends to publish.

What you are seeing
Synthetic account data plus an activity report in explicit loading and ready states.
What GuideShot proves
Capture masks protect raw scenes, redactions protect output, and readiness assertions prevent timing races.
What changes
The protection layer and the declared application readiness state change.
Account details with the email address masked before the capture is cached.

1 / 4

Mask before caching

Targets in the privacy namespace are hidden before the raw scene is persisted.

  1. 1Mark the sensitive target
  2. 2Capture a safe scene
1 recipe1 property

Actionable diagnostics

Replace generic capture timeouts with stable error codes, exact recipe context, and one corrective action.

Failure
What you are seeing
A capture report for missing, duplicated, hidden, unstable, or untrusted product state.
What GuideShot proves
Failures are typed early enough for people and agents to respond consistently.
What changes
The diagnostic code, failed contract, and recommended correction change.
A GuideShot diagnostic with a stable code, recipe context, and corrective action.

1 / 1

Turn failures into corrective actions

Each diagnostic keeps a stable code while the message names the failed contract and a practical remedy.

  1. 1Identify the stable code
  2. 2Apply the stated corrective action