Critique any Figma file in 30 seconds with Crade
Crade reads the Figma file on your screen and gives you specific design feedback: spacing, typography, visual hierarchy, what is working, what is not.
measured.
Critique this landing page design. What is working, what is not, what should I change first?
Working: . Hero headline is specific and scannable . Single CTA, no competing buttons . Logo bar adds trust without bloat Not working (in priority order): 1. Hero CTA "Get started" is generic. Specific verb beats generic. Try "Start a free project" or "See it on your data". 2. Hero subtitle is two sentences when one would do. Cut the second. 3. Feature card icons feel disconnected from the content. Either ditch the icons or make them subject-specific. 4. Typography scale is too tight. Hero 56px → subtitle 18px is a big jump but features 24px → body 14px is jammed. Increase the body or shrink the headline. Fix first: the CTA copy. Single change, biggest impact on conversion.
Good design feedback is hard to give and harder to ask for. "Looks good!" is useless; "this is wrong" without specifics is worse. Crade reads your Figma file on screen and gives you specific, actionable feedback: what to fix, what to keep, and why.
What you put on your screen
- Your Figma file open at the frame or page you want critiqued
- Make sure the work is visible (zoom out to fit if needed)
- Optionally: the brief or requirements alongside, so Crade knows the goal
What you say to Crade
Mention the context. "This is a B2B SaaS landing page targeting CFOs" vs "This is a consumer app for teens" changes the feedback completely.
What you get back
- What is working (so you do not break it)
- What is not working, in priority order (the highest-impact issues first)
- Specific suggestions, not vague directions ("increase the gap between the hero text and the CTA by 24px")
- What to fix first if you only have time for one change
- Anything that looks unintentional (typography inconsistency, alignment drift, color clash)
Tips for better critiques
- Tell Crade the audience and goal. "Goal: get developers to sign up" steers the feedback.
- Ask for trade-offs, not just verdicts. "What am I trading off if I keep this layout?" is more useful than "is this good?".
- For accessibility, ask specifically. "Does this pass WCAG AA contrast?" Crade reads the colors and tells you.
- Compare two versions side by side: "Which is stronger and why?".
- After making changes, paste back: "I made these edits. Better or worse?".
Common critique areas
- Visual hierarchy (what does the eye go to first, second, third)
- Typography (consistency, readability, scale relationships)
- Spacing (whitespace use, alignment, grid adherence)
- Color (contrast, palette discipline, emphasis)
- Information density (too much, too little, right balance for the context)
- Accessibility (contrast ratios, focus states, error messaging)
Frequently asked questions
Is Crade a replacement for a senior designer's review?
No. Crade catches the obvious things (alignment, contrast, hierarchy) but a senior designer brings taste, brand fluency, and context that Crade does not have. Use Crade to polish before review, not instead of.
Will Crade actually open the Figma file?
Crade reads what is visible on your screen. The Figma file needs to be open with the relevant frame in view. Crade does not access Figma's API.
Can Crade help with components and design systems?
Yes. Show Crade your component library or design system page; ask "is this card consistent with my system?" or "suggest a variant for X". Crade reads the existing patterns.
What about wireframes?
Yes. Crade gives less feedback on visual polish (because that is intentionally absent in a wireframe) and more on structure, hierarchy, and flow.
Can Crade redesign for me?
Crade can suggest specific changes but it does not draw in Figma. You make the edits yourself based on the critique.
The whole loop in one sentence
Figma file on screen, one prompt with the audience and goal, specific feedback back. Self-critique becomes faster and more reliable than relying on "looks good!" from your team chat.
A brief lands in your Notes app. Thirty seconds later, the landing page is open in your browser. Here is what to put in front of Crade, what to say, and the exact step-by-step from brief to live preview.
Build red. Stack trace. Module not found. Type mismatch. Crade reads your editor, terminal, and error output on screen and tells you exactly what is wrong and how to fix it.
Crade reads your database schema on screen and gives you the exact SQL for what you actually want, in PostgreSQL, MySQL, BigQuery, or whatever you are running.