> ## Documentation Index
> Fetch the complete documentation index at: https://docs.figr.design/llms.txt
> Use this file to discover all available pages before exploring further.

# Screen Recordings

> One of the best ways to teach Figr how your product actually works.

<iframe src="https://www.youtube.com/embed/h2dpxr8Fpbw" title="Screen recording walkthrough" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

Screen recordings teach Figr how your product actually works. Reach for one when a single screenshot cannot capture the experience: user flows, click paths, navigation, transitions, states, behavior, and your spoken context.

<Tip>
  **Best practices**

  * Record one flow at a time and keep it focused
  * Narrate what you are doing and why
  * Use realistic data and show the states that matter
  * Skip long, unrelated sessions
</Tip>

## What to record

* "How a user upgrades their plan."
* "The current onboarding flow."
* "Where users get stuck in setup."
* "How admins manage permissions."

<Steps>
  <Step title="Record one flow">
    Capture a single flow end to end, narrating the user, the goal, and where the friction is.
  </Step>

  <Step title="Upload it to Figr">
    Add the recording to your prompt, or attach it to a Context Pod so Figr can reuse it later.
  </Step>

  <Step title="Ask Figr to reason first">
    Have Figr understand the flow before it designs anything.

    ```text theme={null}
        Use this recording to understand the current onboarding flow. Identify UX friction, missing states, and unclear moments. Then suggest a better flow before designing screens.
    ```
  </Step>
</Steps>