Writing is design. And as agents join our teams, an increasing amount of UX and brand copy can end up delegated to them. From page titles to section headings, card descriptions to empty states, language can make or break a design. And when the results are clearly identifiable as “AI slop,” readability, trust, and brand consistency can quickly suffer.
That can lead to one of two problems:
- Designers need to spend valuable time rewriting the work by hand after the fact.
- The quality and efficacy of the language veers towards inconsistency over time.
Luckily, research shows that AI writing carries measurable tells that can be mitigated against.
The tells of AI writing
At the simplest level, there are very specific words and combinations of words that give AI writing away. Wikipedia’s editors maintain a “Signs of AI writing” page that tracks patterns and even model eras: “delve” was overused in 2023 and faded in 2024, while newer models lean on “emphasizing,” “enhance,” “highlighting,” and “showcasing.” The tells shift faster than most style guides can keep up with, but a careful reader will be able to detect them anyway.
Pew Research Center classified roughly 490,000 English-language web pages from Common Crawl, spanning January 2021 to July 2026, using the Pangram AI-detection model. AI-typical vocabulary (like “delve,” “interplay,” or “testament”) has more than doubled since 2023. Negative parallelism (“it’s not just X, it’s Y”) has nearly tripled. By the 2026 samples, about 9.4% of .com pages showed signs of AI authorship, which is roughly double the rate for .org pages.
The problem is structural, too. Jakob Nielsen’s readability research found that ChatGPT writes at a 16th-grade level, comprehensible to the top 5–10% of readers, while long-standing usability research recommends 8th grade for broad consumer audiences. Asked for 8th grade, it produced 10th; he had to request 6th to get 8th. The same gap shows up in interface copy: the plain, specific sentence a designer would write is not the model’s default.
Nielsen Norman Group (NN/g) studied product-embedded generative AI, including Amazon’s Rufus and Instagram’s AI search, and found the same violations of web-writing principles: jargon, walls of text where a direct answer was asked for, and bold emphasis used as filler.
From research to skills
Research alone isn’t always easy to put into action, though. So, over the past month, our design writing team dug deep into the literature and data, before creating actionable agent skills that designers can put to work across their projects. The result was two installable agent skills, focusing on pain points that had been surfaced to the team.
The first, agentic-ux-copy, writes interface copy: headings, buttons, empty states, errors, and more. When a designer puts the skill to use, the agent begins by asking key questions about audience, voice, and constraints before it writes. If the designer already has a messaging guide or other resources they’re building from, the agent distills that information into a compact brand file instead. Best practices for agent skill design suggest that long documents are often only partially applied. The brand file is built on real copy examples rather than adjectives, because examples teach voice and adjectives barely move it: practitioner experience suggests that persona and tone instructions do around 5% of the work people assume, and the examples carry the rest.
Three rules do most of the work. No parroting: descriptions that restate the user’s prompt, the feature’s name, or the heading they sit under. No repetition: copy must vary in sentence structure, not just vocabulary. And no concrete verbs on abstract concepts. You can find the full research-backed list in a new section of the Automattic Design System.
The skill also ships a deterministic linter: 47 banned words and 33 banned patterns, plus a set of judgment calls flagged for human review.
The second, voiceover-scriptwriting, writes narration for AI video and text-to-speech. It plans against word budgets: natural spoken English runs at 130–150 words per minute, so a 15-second slot holds 30–40 words.
If the script runs long, the fix is to cut a point, never to speed up the read, as rushed delivery makes a video feel cheap.
It runs a mandatory normalization pass, because “11” is “eleven” in English, “once” in Spanish, and “elf” in German: everything is written exactly as it should be spoken. It tags emotion and delivery from per-model dictionaries covering six TTS providers, because tag syntax doesn’t transfer between models, and a skill that hard-codes one breaks on the next. And it validates duration per scene, with a buffer, because text-to-speech (TTS) doesn’t guarantee that narration will fit.
Both skills share an architecture. The core skill is kept deliberately light and simple, loading per-brand and per-model reference files on demand. Brand files are distillations of real guides, rather than forks — they record their source and date, and get re-distilled when the guide changes. Claims are held verbatim: “more than 99.99% uptime since 2005” must never be paraphrased into “guaranteed 99.999%.” That’s the difference between a style preference and a legal problem.

Why this matters now
NN/g’s State of UX 2026 report speaks to the bigger challenges with agent-initiated writing: AI fatigue is growing rapidly in 2026, and as more online writing starts to sound the same, both clarity and differentiation are at risk. That’s why designers and companies using AI thoughtfully are already showing signs of outperforming those shipping slop haphazardly and at scale. Distinctive writing is becoming a design differentiator again.
The ground rules also shifted while this work was underway. The SAG-AFTRA Interactive Media Agreement, ratified in July 2025, requires consent and disclosure before a performer’s voice is replicated. The EU AI Act’s Article 50 requires synthetic audio to be disclosed, with fines reaching €15 million or 3% of worldwide turnover. A skill that treats consent and disclosure as steps the agent cannot skip is more reliable than a paragraph in a policy document.
One of the biggest challenges of style guides and design system documentation is getting everyone on a team to put them to work, rather than leaving them to gather dust. With agents, the risk hasn’t gone away, but there’s an opportunity to mitigate the issue by turning abstract guidance into actionable skills.
Part of a wider set of skills
This is one thread of a larger effort. Working towards higher-quality agentic experiences described thirteen best practices for designing agentic experiences, a skill that turns them into a focused starting brief, and agent instructions that carry them into the code. When we tested that guidance, rule violations fell from 65% to 22% (WooCommerce with Claude) and from 27% to 2% (WordPress with Codex), and agents that stopped to ask before acting rose to 67% in both setups.
The writing skills follow the same pattern: research and curated practices, distilled into skills a designer can point their agent at and put to work. Alongside the agentic design guidance, they’re part of a growing library of skills designers at Automattic use every day, spanning everything from experience design to effective, on-brand design writing.
What we’re learning
Ban lists go stale as model vocabulary shifts by era. The words that flagged a 2023 draft as AI-written are not always the same words that flag a 2026 one as agent slop, so lists, skills, and linters need human-in-the-loop owners, reviewers, and maintainers. A skill without a maintenance plan is a sure way to regenerate the problem over time.
As we roll out the skills, the measures of their success is straightforward: are designers rewriting less in their daily work, and are the results delivering consistently for our customers?
Human judgment continues to play an important role, as agent skills encode decisions, not taste. The key strength of the skills themselves is in ensuring that agents ask instead of assume, keep claims verbatim, and leave the designer to decide whether the result works.
We’re looking forward to measuring the impact and iterating on the skills over time.
Take a look
While the skills are currently incorporated into an internal plugin, we’ve now published the research-based guidance and downloadable agent instructions and resources to the Automattic Design System. We’d love to hear your thoughts and feedback and hope to publish public-facing skills in the near future.
Useful links
- Pew Research Center – How Much of the Internet Is Written With AI?
- Jakob Nielsen – AI Generates Complex Text, Challenging Many Readers
- NN/g – Product-Specific GenAI Needs to Write for the Web
- Wikipedia – Signs of AI writing
- NN/g – State of UX 2026: Design Deeper to Differentiate
- Claude – Best practices for Claude Code
- Comics Beat – Video game actors pass SAG-AFTRA Interactive Media Agreement
- EU AI Act – Article 50: Transparency obligations
- Pexo – How Long Should an Explainer Video Be?
- Nobex – Free script timer
- ElevenLabs – Why are numbers, dates, symbols and acronyms not properly pronounced?
Railsware – How to AI: fixing generic AI content (not with better prompts)



















Leave a Reply