# Writing with AI

> The habits that mark a draft as machine written, and how to edit them out.

An AI draft breaks the same rules as any weak draft, and has a few habits of
its own. This page covers those habits, with a draft line before each edit
and after it. Edit everything else against
[Language and grammar](https://ticketsolutionsptyltd.github.io/roadie/content/language-and-grammar.md) and
[Voice and tone](https://ticketsolutionsptyltd.github.io/roadie/content/voice-and-tone.md), like any other draft.

## The tells

Each tell shows the draft line to avoid and the edit that fixes it.

### Trailing -ing phrases

A clause like "highlighting its commitment" or "ensuring a smooth night", tacked onto the end of a sentence, claims a meaning nobody checked. Delete it, or give the fact behind it its own sentence.

**Do**

The festival added a second stage for local acts.

Gates open at 5pm, an hour earlier than last year.

**Don’t**

The festival added a second stage, highlighting its commitment to local acts.

Gates open at 5pm, ensuring a smooth entry for every fan.

### AI vocabulary

Some words turn up far more often in machine writing than in ours. Use the plain word instead.

**Do**

Here's how regional festivals sold this year.

**Don’t**

Let's delve into the vibrant landscape of regional festivals.

| Write                   | Not                   |
| ----------------------- | --------------------- |
| also                    | additionally          |
| important, or say why   | crucial, pivotal      |
| look at                 | delve into            |
| show                    | showcase, underscore  |
| improve                 | enhance               |
| build                   | foster                |
| get                     | garner                |
| busy, loud, or the fact | vibrant               |
| market                  | landscape, as an idea |
| proof of                | testament to          |
| mix                     | tapestry, interplay   |

### Not just this, but that

"It's not just X, it's Y" sets up a claim nobody made so it can knock it down. Say the point.

**Do**

We run your ticketing, and we answer the phone on show day.

**Don’t**

It's not just a ticketing platform, it's a partner in your success.

### Groups of three

List as many things as there are. A draft pads or trims ideas to three because three sounds finished.

**Do**

Scanning takes 2 seconds a ticket.

**Don’t**

Fast, simple, and seamless entry for every fan.

### Bold labels that repeat the line

A bullet that opens with a bold label and a colon, then says the label again, is a tell. Write the sentence. A bold name that ends in a full stop and leads into new detail is fine, as in the second Do example.

**Do**

Scanning took 2 seconds a ticket, down from 5.

`**Refunds.** We refund to the card you paid with.`

**Don’t**

`**Performance:** Performance improved across all venues.`

`**Refunds:** Refunds are handled by our team.`

### Curly quotes in drafts

Code, Markdown, and AI drafts use straight quotes, so search and code read
them. Rendered copy may use typographic quotes.

| Before               | After                |
| -------------------- | -------------------- |
| `title=‘Doors open’` | `title='Doors open'` |

### Chatbot phrases

Delete the assistant's side of the conversation, such as "Certainly!", "I hope this helps!", and "Let me know if you have any questions". A warm sign-off is fine only after a concrete next step.

**Do**

Gates open at 6pm. I'll send the run sheet by Thursday. Have a great show.

**Don’t**

Certainly! Here's the update. I hope this helps!

### Flattery

Answer the question. Don't praise it, or agree with the reader before you answer.

**Do**

Refunds go back to the card you paid with within 5 business days.

**Don’t**

Great question! You're absolutely right that refunds can be tricky.

## Guidelines

### Edit the draft until it states facts

**Do**

```tsx
<Callout intent='success' title='Your refund is on its way'>
  It reaches the card you paid with within 5 business days.
</Callout>
```

Say what happened and when the reader sees it.

**Don’t**

```tsx
<Callout intent='success' title='Great news!'>
  Your refund is being processed, ensuring a seamless experience.
</Callout>
```

Don't ship the draft's cheer or the clause it tacks on the end.

## The rules for every writer

A draft also breaks the rules on
[Language and grammar](https://ticketsolutionsptyltd.github.io/roadie/content/language-and-grammar.md). These catch the most.

- [Clarity](https://ticketsolutionsptyltd.github.io/roadie/content/language-and-grammar.md#clarity) catches vague claims,
  inflated words, padding, hedging, unnamed sources, arrows, and fragments.
- [Use the plain word](https://ticketsolutionsptyltd.github.io/roadie/content/language-and-grammar.md#use-the-plain-word)
  lists the swaps for the most common inflated words.
- [Dashes](https://ticketsolutionsptyltd.github.io/roadie/content/language-and-grammar.md#dashes) bans em dashes and en dashes.

## Attribution

Adapted from [unslop](https://github.com/cursor/plugins/tree/main/pstack/skills/unslop)
by Lauren Tan (pstack, MIT). The rules here are rewritten in Oztix wording,
and the ones that apply to every writer live on
[Language and grammar](https://ticketsolutionsptyltd.github.io/roadie/content/language-and-grammar.md).

Docs updated 14 Oct 2026.