A skill that makes Claude read client feedback the way a senior art director does and turn it into a plan you can act on. Paste the emails, call notes or marked-up PDF and attach the work. Claude splits the feedback into single numbered comments in the client's own words, finds the concern under each vague one (what "make it pop" or "more premium" usually means, and the other reading), measures the design to check, and flags where two people want opposite things. Then it writes a numbered revision list with real numbers, the few questions worth asking, a scope check with a change order draft, and a short reply that confirms the plan.
Inside are four reference files. A phrasebook covers 39 common client comments, each with its usual meaning, the other reading, what to look for, the changes that answer it and the trap. A numbers file holds the tests (squint, greyscale, phone size, a five-second read) and working ranges for hierarchy, margins, type, colour, photos and logos, plus the WCAG 2.2 contrast rules checked on 17 October 2026. A scope file covers revisions versus changes, change orders, reply templates and US freelance contract laws, and a worked example follows one full round for a fictional drinks brand. It works one stage at a time, never invents a fee, a date or a client's words, and never averages two opposite requests into one design.
It writes plans and replies. It does not edit your design file, and it never sends anything to your client. With code execution switched on it measures the work, sampling colours, computing contrast ratios and reading every sticky note in a PDF; without it, numbers are estimates and labelled as such. The contract and advertising rules cover the US only and are not legal advice. You get the most from it by attaching the work with the feedback, plus the proposal that sets the scope, the brief and the brand guidelines, and by waiting until a round's feedback is complete. When the new version is ready, bring it back for the round check before it goes out.
Claude skill · version 1.0
Client feedback translator
Checking your access.
In the download · 6 files
- SKILL.mdThe method Claude follows: gather and split, diagnose, the revision plan, questions and scope, the reply and the round check, one stage at a time.
- README.mdHow to install it in claude.ai or Claude Code, how to start, and the licence.
- references/phrasebook.md39 common client comments, such as make it pop, more premium and make the logo bigger, each with its usual meaning, the other reading, the changes that answer it and the trap.
- references/levers-and-numbers.mdTests to run on a design, working numbers for hierarchy, space, type, colour, photos and logos, a contrast table, and the WCAG 2.2 rules, sourced and checked on 17 October 2026.
- references/scope-and-replies.mdRevision or change, a change order template, the reply template, paragraphs for hard moments, US freelance contract laws and the FTC review rule, sourced and checked on 17 October 2026.
- references/worked-example.mdOne full round for a fictional sparkling water brand: three clashing emails turned into a plan, a reply and a checked second version.
Install it and begin
01Install it in Claude CodeTerminal mkdir -p ~/.claude/skillsunzip ~/Downloads/client-feedback-translator.zip -d ~/.claude/skills/# Start it with /client-feedback-translator. If this is your first skill, type /reload-skills once.On claude.ai there is nothing to unzip: upload the zip as it is. Every step is on Install and use a Claude skill.
02Your first message to ClaudeText Use the client feedback translator skill. I am [A FREELANCER / IN-HOUSE / THE CLIENT]. Here is the work: [ATTACH THE DESIGN AS PNG OR PDF]. Here is the feedback, word for word: [PASTE THE EMAILS OR NOTES]. The person with the final say is [NAME AND ROLE]. Split it up and tell me what they are worried about.Attach the design as you sent it and paste the feedback exactly as it arrived, typos included. The proposal or contract scope and the brand guidelines make the scope check and the plan sharper.
Checklist
Before you reply to feedback
- Every comment split out, numbered and quoted in the client's own words, with who said it.One sentence often holds a compliment, a complaint and a fix, and the compliment is what the revision must not break.
- One named person with the final say for this round.Feedback with no decider goes round in circles, and the loudest reviewer ends up deciding.
- The likely concern written under every vague comment, with a confidence rating."Make it pop" usually means nobody can tell what to look at first. Turning every colour up answers the words and misses the worry.
- The design measured rather than eyeballed: contrast ratios, sizes, how much of the frame the product fills."Flat" means one thing at 1:1 and another at 7:1, and a measured number is easier to agree on than an opinion.
- Every conflict between people named, with a way through: sequence it, split it by placement, or ask the decider.Averaging two opposite requests gives a design that satisfies neither person.
- Each change written with numbers a stranger could follow, ordered from layout down to detail.Detail work done before a layout change gets thrown away, and "bolder" means something different to everyone.
- Anything outside the agreed scope given three options: add it, swap it or schedule it.A flat no strains the relationship, and quiet yeses become unpaid work the client then expects.
- A reply under 250 words that says what you will keep as it is, and why.Clients accept a decline when it answers their concern, and long replies read as defensive.
What to do it with
- ClaudeFree tier, paid above it
A language model that writes, edits, reads long documents and runs tools, including agents that work inside a codebase.
Bad at It is agreeable by default, so it will improve a bad idea instead of telling you it is bad. Ask it to argue against you and the quality of the answer changes.
- Claude CodeSubscription
An agent that reads a whole repository, edits files, runs the tests and explains what it changed.
Bad at It is fast enough to make a large mistake quickly. Work on a branch, read the diff, and never let it push. Watch the starting mode: on Pro, Max and Team plans it opens in auto mode, which Anthropic's own list says may read a .env file and send the key in it to the API that key belongs to. Switch it off.
Why it matters
Vague feedback answered literally usually leads to a third round. A logo made bigger on request can end up fighting the headline, and a price burst added for sales can undo the premium look marketing asked for. If you split the difference between two people, often neither is happy. Ask a plain chat to fix "make it pop" and it tends to turn everything up. This skill makes Claude find the concern first, check it against the measured design, put numbers on every change and send the client a plan they can say yes to before any work starts.
- Type
- technique
- Period
- ongoing