Critique a screen
A senior design review of any screen, in the order that matters.
YouCritique our plan-settings screen before we ship.
Settings Billing
Plan & billing
Pro Current plan
£12 per seat a month · renews 1 November
Seats8 of 10
Projects14 of 20
YouCritique our plan-settings screen before we ship.
Critique · plan settings
- OBSERVED“Upgrade to Team” is the only filled button on a page for managing a plan.
- OBSERVED“Delete account” sits beside “Cancel plan”, in the same small grey style.
- INFERREDA subscriber here most likely wants to manage their plan, not upgrade.
- UNKNOWNWhere “Pause” and “Cancel plan” lead. Those screens weren’t supplied.
Your callFix before shipping, or test it first.
Illustrative example. The labels: OBSERVEDSeen in what you gave itINFERREDA hunch, with how to test itUNKNOWNCan’t tell; says what would settle it
Say it your way
- “Critique this checkout screen before we ship on Friday.”
- “I generated this settings page with v0. Is it actually good?”
- “Sanity-check the hierarchy on this Figma frame.”
It works through
- Hierarchy
- Comprehension
- Behaviour
- Risk
- You decide
You get back
- Problems, ranked
- Evidence for each
- The consequence
- How to verify a fix
Install in one command.
It loads by itself when a request like these comes in. Free and open source, no account.
Claude Code
unzip splitfire-interface-critique.zip -d ~/.claude/skills/ Every project on this machine. Use .claude/skills/ inside a repository to share with your team.
Codex
unzip splitfire-interface-critique.zip -d ~/.agents/skills/ Every project. Use .agents/skills/ inside a repository instead, then restart Codex.
Claude apps
On claude.ai or the desktop app, upload the .zip in your skills settings. One zip is one skill.