All 141 tools / Handoff and design ops
Sort critique notes into observation, opinion, solution, vague and question, and rewrite the weak ones.
Feedback lintFreeFor designers, product teams and agencies
30/day
free runs a day, no sign-in.
Before: what you give it
The example input, as typed in. You paste text, CSS, markup or notes.
Make it pop more I don't like the blue The checkout button is the same grey as the cancel link, so people will not know which one finishes the order Can we use a carousel here? Feels off
After: what comes back
The first lines of a real run on that input. Nothing here is edited by hand.
5 notes: 1 observations, 0 solutions without a problem, 1 opinions, 2 vague, 1 questions. 20% ready to act on. [vague] Make it pop more "Make it pop" cannot be acted on; say what you see that gives that impression Observation: on the [element or screen], I see [what is actually there]. Impact: because of that, [who] will [do or miss what]. Suggestion: [optional; a direction to try, not an instruction]. [opinion] I don't like the blue a preference with no effect attached; say who it affects and how, or drop it Observation: on the [element or screen], I see [what is actually there]. Impact: because of that, [who] will [do or miss what]. Suggestion: [optional; a direction to try, not an instruction]. [observation, ready] The checkout button is the same grey as the cancel link, so people will not know which one finishes the order [question] Can we use a carousel here? ... full output on the tool page
What you get
Each note labelled with why it is weak, a share of notes ready to act on, and a rewrite skeleton
What it cannot do
Classifies wording only; it cannot tell whether a note is right about the design.
Who it is for
- Designers
- Product teams
- Agencies
Free and Pro
| Free | 30 runs a day per IP address, up to 20,000 characters a run. |
|---|---|
| Pro | No daily limit, 300 requests a minute, up to 200,000 characters a run. |
Use it from your assistant
The tool is called lint_design_feedback. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.
claude mcp add --transport http designers https://designers.allthepossibles.com/mcp
curl -X POST https://designers.allthepossibles.com/api/feedback-lint -H 'content-type: application/json' -d '{"text":"Make it pop more\nI don'\''t like the blue\nThe checkout button is the same grey as the cancel link, so people will not know which one finishes the order\nCan we use a carousel here?\nFeels off"}'
Try it here
The form starts with the same example input, so you can run it first and then swap in your own.
More in handoff and design ops
- Personal data scan
Find real emails, phone numbers, cards, IBANs and API keys in design text before you share the file.
- Handoff spec check
Find the missing states, sizes, tokens and behaviours in a component handoff list before developers ask
- Naming convention check
Audit layer, token and file names for mixed styles, default names like Frame 12 and version leftovers
- Asset export planner
Get the formats and sizes to export for each asset across web, iOS, Android, favicon and social
- SVG bloat check
Find the editor metadata, long decimals and unused defs bloating an SVG, with the bytes they cost
- Design changelog
Turn two lists of tokens or components into a changelog with probable renames and a version bump