Critiquito: Design Critique
Critiquito gives design feedback. Share a screenshot or a Figma link and it returns a critique with ranked, concrete fixes covering hierarchy, type, color, copy and accessibility. It never edits your files.
Facts the bot starts with (4 on the listing)
- $41
- Job: design critique. Read one screen, a set of variants, or a short flow from a screenshot, a Figma frame, or a live URL, and return findings across hierarchy, spacing, type, color, interaction and states, copy, and…
- User prefs, fill during getting started: product and what it does = unset, who uses the screens = unset, platform = unset, severity bar = blockers and worth fixing, design system or brand rules = none given, where fixes should go…
- Working state lives in files, not in memory: a dated critique for every screen reviewed, and one open fix list per screen holding each finding, its severity, and whether a later version cleared it. Read a screen's fix list before…
Playbooks it can run (7)
- Getting started: Use on the first conversation after setup, or whenever memory has no user prefs: learn what the user wants from this bot and get them to a first result.
- Screen critique: Use when the user hands you one screen as a screenshot, an image, a Figma frame link, or a live URL and wants to know what to fix.
- Compare versions: Use when the user has two or more versions of the same screen, or hands you a new version of a screen you already critiqued.
- Flow critique: Use when the user hands you two or more screens in sequence, like signup, onboarding, or checkout, and wants the whole path reviewed.
- Accessibility pass: Use when the user asks for an accessibility review, or when a critique turned up contrast, target size, or labeling problems worth a closer look.
- UI copy pass: Use when the user wants the words on a screen rewritten: buttons, headers, empty states, error messages, tooltips, or onboarding text.
- Hand off the fixes: Use when the user wants findings turned into tickets, posted to their team, or kept somewhere they can read later, in Linear, Notion, Slack, or as text they can paste anywhere.
Jobs that run on their own (1)
- Weekly open fixes: Every week, lists the critique findings still open on each screen and offers to re-check the ones with a new version.
Apps it can use (4)
- Figma: Read a frame straight from a file link instead of waiting on a screenshot.
- Slack: Post a critique you approved into the channel your team reviews in.
- Notion: Keep the critiques and open fix lists on a page your team can read.
- Linear: File the blockers as tickets on the right team, drafted for your yes.
- Terms for every marketplace bot (x.ai third-party bot terms): adding it lets the bot read, write and send data and use third-party services through the accounts you connect. You connect each account yourself.
- License (x.ai third-party bot terms): a limited, non-exclusive, revocable license to use the bot for your own purposes. You can't redistribute or re-share it without the creator's permission.
- What a template copies (x.ai template guide): instructions, memories, skills and first-party plugins, but not the creator's secrets, private skills or custom code.
Taken from the Critiquito: Design Critique listing on x.ai (Memories, Skills, Routines and Integrations tabs); item text is shortened from the listing. Anything stated nowhere is marked "Not stated".
More Grok Bot templates
- Engineering Lead by Lauren Tan
- QA bot by Ulysses Ng
- PM bot by Ulysses Ng
- The Morning Newspaper by Karen X. Cheng
AgentScout links to the original public listings and doesn't host copies. We aren't affiliated with xAI, Anthropic, OpenAI, OpenClaw, Cursor, n8n or the creators listed. Names and logos belong to their owners. Grok Bot cards show the creator's photo from the x.ai marketplace. Listing checked Oct 21, 2026.