Input Guide

Pick inputs that match what you want Figr to understand. The closer the match, the less generic the output.

Goal	Use these inputs	Best for
Understand an existing product	Screen recordings, Chrome extension, screenshots, Figma frames	Redesigns, UX audits, existing product improvements
Follow your design system	Figma input, design files, component examples, tokens	Matching visual language, creating Figma-ready outputs
Understand requirements	PRDs, docs, PDFs, pasted text, product briefs	PRD-to-design workflows, feature planning, requirements review
Reason from user behavior	Analytics, CSVs, support tickets, research notes, user feedback	Funnel improvement, activation flows, product discovery
Study a live page or competitor	Chrome extension, URL input, website capture, screenshots	Landing page analysis, competitor research, web app audits

Pick an input

Teach Figr a flow that one screenshot cannot explain.

Capture live product pages with structure, not just a flat image.

Bring in components, layout, and variants from existing design work.

Use PRDs, CSVs, research, and web context that live outside the screen.