“Make it sound more polished” is one of the easiest ways to end up with AI slop.
Maybe you want an article to sound expert without trying too hard, a caption to feel confident without being cringe, or a presentation to look put together without feeling corporate.
But words like “polished” and “professional” mean something different to everyone. When you give AI the same vague direction as everyone else, you get a version of the same generic output.
AI doesn’t need more adjectives. It needs to understand the choices behind your taste.
Tell AI which part you like
It’s completely normal to get inspiration from other people’s work. The important part is knowing exactly what you like in each reference.
Too vague:
More useful:
You might take the colors from one reference, the structure from another, the pacing from a third and combine them with your own ideas and experience.
That combination becomes your formula. Over time, it becomes a style people recognize as yours.
Build a one-page Taste Context file
Don’t try to define your entire creative identity. Start with this:
# MY TASTE CONTEXT
## References I like
[Reference or link]
I like:
I don’t want copied:
Why it works for me:
## Things I don’t like
[Example]
What feels wrong:
The rule AI should follow instead:
## Sounds like me
practical, sharp, specific, slightly playful, “here’s what I’d do”
## Doesn’t sound like me
unlock, supercharge, game-changing, harness, “in today’s fast-paced world”
## Rules
- one strong idea per piece
- use real examples
- no generic conclusion headings
- no em dashes
- explain jargon only when it helps
- don’t mention private inspiration sources
- don’t use the same article structure every time
## My best work
[Example]
Why it sounds or feels like me:
That’s enough for the first version.
Save the reason behind every preference
Don’t only save what you dislike. Save why you dislike it.
For example:
This only blocks one phrase.
A better rule is:
That also catches “Key takeaway,” “Final thoughts” and other versions of the same problem.
The reason helps AI understand what you actually want. The banned phrase alone doesn’t.
Add this to every skill and workflow
Most people correct the draft but lose the lesson. The next time they start a task, they have to give the same feedback again.
Add this instruction to every skill or workflow that creates content for you:
When I say “this doesn’t sound like me,” “I don’t like this wording,” “this is too corporate,” or “never use this again,” don’t only fix the current output.
Update the relevant Taste Context file so the feedback is used in future work.
Save what missed, why it missed and what to do instead. Then reread the updated file before rewriting the current output.
If the feedback may only apply to this task, ask before saving it as a permanent preference.
“Never use em dashes in my articles” should be saved.
“Make this caption shorter” probably only applies to the caption in front of you.
If it isn’t clear, AI should ask.
Let AI build the first version with you
You don’t need to fill out the file alone. Give AI a few references and let it interview you.
Help me build my Taste Context file.
I will share five examples I like or dislike. For each one, ask:
1. What exactly do I like or dislike?
2. Which specific part creates that feeling?
3. What do I not want copied?
4. Where have I made a similar choice in my own work?
If I use a vague word like “clean,” “polished” or “cheap,” ask me to explain which part created that impression.
When we finish, create:
- references I like
- things I don’t like
- words that sound like me
- words that don’t sound like me
- rules AI should follow
- examples of my best work
Show me any preferences that conflict and ask before choosing between them.
Check the work before publishing
Before you publish, ask:
- Does this sound like me?
- Is there a detail that could only come from my experience?
- Is the main idea specific?
- Did it stop before becoming overdone?
- Is it inspired by my references without copying them?
If the work fails, don’t only rewrite it. Save the lesson to your Taste Context file.
Your first file won’t be perfect. It shouldn’t be.
Start with a basic version and let every real correction make it better.