Skip to main content
When Figr does not do what you expected, it is usually a context or prompt gap. Work through the relevant section below.
Check these first:
  • Is a design language or design system actually added?
  • Is the right Context Pod attached?
  • Did you point Figr at the existing layout or component to follow?
Where the active design system shows in the interface
Then nudge it:
Make this screen closer to our existing settings pages, using the current components and spacing.
Ask for them explicitly:
List the edge cases for this billing upgrade flow, including payment failure, expired card, permission restriction, and downgrade impact.
A checklist of states to request
Use this formula:
A card showing the prompt formula
Given [context], help [user] achieve [goal]. The current problem is [problem]. Use [inputs and design system]. Consider [states and edge cases]. Output [artifact, design, or review].
Example:
Given our onboarding flow and design system, help a workspace admin finish setup faster. The current problem is drop-off on the team-invite step. Use the attached recording and design language. Consider empty, error, and success states. Output a redesigned setup screen.
Check these:
  • Is the design final enough to export?
  • Did you export the right item?
  • Are you comparing against the latest version?

​
Account and access

You are not an Admin. Only Admins see the full organization settings. Ask an Admin to change your role or to make the change for you. See Roles and permissions.
Domain access is on, so anyone with a matching company email joins without an invitation. Turn it off if you want to approve every invite manually. See Domain auto-join.
Check whether you removed them from the organization or only changed their role. A role change does not remove access, but removing them from Members & Roles does.
Your team shares one credit pool. Upgrade to a higher plan to get more credits immediately, or wait for next month’s allocation. See Usage and credits.