Create a Context Pod
Create a new pod
Click Create new Context Pod (top right). Give it a name (required) and an optional description.
Add your sources
A Context Pod accepts five source types. Use as many as you like; the more you add, the deeper Figr’s understanding.Show us your product (recommended)
The richest source. Show Figr your product in motion.- Record a walkthrough directly, with optional microphone narration and full-screen capture
- Or drag and drop an existing screen recording
Upload files
Drag and drop supporting material: PDFs and design specs, screenshots and images, documents, and other product files.Paste text
Open the note editor, give it a title, and write in the rich-text area. Useful for product overviews, terminology, or notes that do not live in a file.Link website
Paste a URL, like your product or marketing site. Figr validates the link and fetches the page so it can read your live content.Add instructions
Free-form guidance that shapes how the agent responds:The pod summary
After building, you land on the pod’s summary dashboard. A right-side drawer lists everything linked to the pod, every recording, file, note, link, and instruction, alongside its generated context status. Return here anytime to review what the pod knows or to add and remove sources.

Use a Context Pod
A Context Pod only shapes output once you attach it to a prompt.
Submit your query and Figr grounds its response in the pod’s sources, referencing your real flows, files, and terminology instead of generic assumptions. Attach the same pod across many projects, so product knowledge follows you everywhere.
Context Pod vs Design Language
The two design-intelligence sources do different jobs, and most teams use both.| Context Pod | Design Language | |
|---|---|---|
| Captures | What your product is and how it works | How your product looks |
| Sources | Recordings, files, text, links, instructions | Figma frames, tokens, component files |
| Shapes | Flows, terminology, behavior, content | Colors, typography, spacing, components |
| Output | Designs that fit your product’s logic | Designs that match your visual system |
Why it matters
Without product context, Figr designs from generic assumptions: plausible screens that do not reflect your actual flows, naming, or user needs, and you re-explain your product in every prompt. With a Context Pod attached, that knowledge is always present. Figr already knows your onboarding flow, your terminology, and your constraints, so it designs for your product, not a generic version of it.Best practices
Troubleshooting
| Issue | Fix |
|---|---|
| Website link will not attach | Confirm the URL is valid and public, and wait for the validation check to pass |
| Pod does not influence a response | Make sure it is attached as a chip on the prompt before submitting |
| Recording upload fails | Check the file is a supported video format and within the size limit |
| Output ignores your terminology | Add an explicit instruction spelling out the terms to use |
Related
Context Pods
What a Context Pod is and how it grounds a project.
Setting up Design Language
Teach Figr how your product should look.
Screen Recordings
Capture a flow to drop into a pod.


.png?fit=max&auto=format&n=z16Z7ZdXfoZy_c4N&q=85&s=e6414dab1b68ff2cf0cbe14a709f5991)
