# UX writing agents, workflows and skills | Dan Kornberg

**Every time AI moved, Wix's writers were already there.**

Agents, workflows, and skills that let anyone at Wix write product copy with years of guidelines built in.

- Standard in the product creation kit for every PM, designer, and writer
- Dozens of Wix employees using the agents
- A step ahead at every stage: guidelines, prompts, multi-agent, harnesses

Role: UX Writing Team Lead → AI Strategist, Wix. Also called "AI Content Workflows & Skills."

## The guidelines

Wix's writing guidelines had built up over years. Some lived in docs, some in Notion, and a lot only in people's heads, passed along by word of mouth. Before anyone believed agents could handle real content, I started cross-team projects to put it all in order: one standard set.

## Made for machines

Models back then struggled with what we had in Notion: toggles, callouts, emojis. I moved the guidelines into clean markdown, so an LLM could actually use them.

## Systems, not prompts

Most people were still working on prompt wording. I was writing system prompts and step-by-step reasoning, then building multi-agent setups where agents work together on copy, each with its own job.

## The harness

When others got to system prompts, I was building UX writing harnesses: reusable skills, and MCP servers that connect agents to systems that keep updating, like the [glossary](../glossary/).

Illustrative example (not real Wix copy or agent output). The request: write the message a client sees when paying a bill fails.

1. A plain prompt: "Oops! We couldn't process your bill. Please try again later."
2. Plus a system prompt, the guidelines in markdown, and step-by-step reasoning: "Your bill payment didn't go through. Check your card details and try again."
3. Plus a checker agent and a reviewer agent, which flag that "card details" is vague: "Your bill payment didn't go through. Check the card number and expiry date, then try again."
4. Plus the harness, skills for each kind of copy and the live glossary over MCP, which flags "bill" (use "invoice"): "Your invoice payment didn't go through. Check the card number and expiry date, then try again."

## Everyone's kit

I connected the work to how design, engineering, and product already worked. The skills became part of the standard product creation kit for every PM, designer, and writer, and dozens of people used the agents. Writers and non-writers alike wrote copy that followed years of guidelines.

## Ahead

When Wix rolled out IDEs to non-developers, writers didn't have to catch up. The skills and agents were already waiting for them.

> "I ensured writers weren't playing catch up but instead were leading the charge."

## What came next

Anyone could write good first drafts now, but not everything came out good enough. That gap is why I started building checkers like the [content quality agent](../../#p-content-quality-agent).

## My role

- Started the cross-team projects that turned scattered know-how into one standard set of guidelines
- Rewrote the guidelines for models
- Wrote the system prompts and reasoning steps, and built the multi-agent setups
- Built the UX writing harnesses: skills, knowledge bases, RAG pipelines, and MCP connections
- Got the skills into the standard product creation kit for PMs, designers, and writers

Tools: system prompts, chain of thought, multi-agent orchestration, skills, MCP, RAG, knowledge bases.

## Questions a hiring manager might ask

**What did "a step ahead" look like in practice?** At each stage, the writing team's tools were ready before the rest of the company needed them. When IDEs came to non-developers, the skills were already there.

**Who used it?** Dozens of Wix employees used the agents, and the skills were part of the standard kit for every PM, designer, and writer.

**How does it connect to the glossary?** The glossary was one of the live systems the harness connected to over MCP, so agents always checked terms before writing.

Contact: dankornberg@gmail.com · linkedin.com/in/dan-korn