Prompt library

Say where it goes and it goes there. Otherwise you spend the next message moving it.

Tags get written as a whole list, so it has to read them before it adds one. Names, subject lines and preview text are not like that, they change on their own.

Personalization fields go in as plain text, so type them the way your platform expects and they come out the same. Saying "more than the greeting" stops it going in one predictable place.

Handing over the guide puts your house rules at the start instead of the end. Ask for the list before it edits and you can keep what is right and argue with what is not.

Nothing has to open, so it is quicker than clicking through them yourself. Do one folder and you catch the few that would have looked broken in an inbox.

Naming the stages up front is what makes the set hang together instead of five emails that say the same thing. Asking for the standard in the same breath builds accessibility in rather than checking for it at the end.

One good starting point saves more time than any number of clever prompts. Leave blanks where the content changes and the next person just fills them in.

Saying what the sequence is for keeps every email pulling the same way instead of four newsletters in a row. Getting the job of each one first means you approve the plan rather than the finished set.

Doing them together is what keeps them looking like a set. Say where they go once and you are not asked three times.

If the brief lives somewhere connected, it can be read straight from there. Quickest way from a signed-off brief to a finished email, and there is only ever one copy of the brief.

With your design tool connected, the colors and sizes get read straight out of it instead of you copying them across. Get the pictures hosted first and they come over too.

Pointing at a real email beats trying to describe a layout from memory. Say which fonts and colors you want and you get that layout in your own look.

A picture says more than a paragraph describing one. You get the layout you pointed at, with your own colors and words on it.

Say what the email is for and who it is going to, and leave the sections to it. Ask to see it first and nothing lands in your account until you are happy.

Ask for a summary and you get a summary instead of a giant list. Quickest way into an account someone else set up.

One change stays one change and the rest of the email is left alone. Say what you want different rather than how to do it.

Contrast and missing alt text get properly checked, so you are not guessing. Mention text size and headings the way this prompt does and those get looked at too.

Saying which standard you have to meet sorts the bits that can be checked from the bits only you can judge. You end up with a short list, and short lists actually get done.

Nothing has to open the design, so it comes back quickly. Anything nobody ever filled in comes back empty, which is exactly what you are looking for.

This is what catches the link nobody remembered to replace. Open anything it flags before you change it.

Fields go in as plain text and come out of the export exactly as you typed them. Asking to see those lines in the exported HTML is proof rather than a promise.

You do not have to pick one email to start from. Say which bit you want from each, then check the join where the two meet.

Say who it is going to and the argument stops being about taste. You get the differences and a pick you can push back on.

One email you got right can be the starting point for every region, faculty or business unit that needs it. It keeps the look it was built with, so ask for the new workspace's styles once it is there.

Decide before you import anything. Most teams send far fewer templates than they keep, so the honest list is short and the rest can stay in the archive where it has been living happily for years.

You can find and drop in a photo without going off to hunt one down first. Say how wide you need it and it turns up sharp instead of fuzzy.

A copy is identical first time, which rebuilding from memory never is. It copies everything, so check the footer before it goes anywhere.

Locked rows are how a central team keeps a shared header, footer or legal block from drifting once a template is out with everyone else. Say what you want changed and ask which rows it could not touch, so nothing quietly does not happen.

You get the code and a filename, ready to paste into whatever you send from. This is the step for any platform you have not connected.

Fonts, spacing and mobile-only rows are what move when the email lands in your sending platform. Ask for the personalization fields to be listed too and you skip the hand-editing that usually follows.

Starting from the one that already works beats starting from nothing. Ask what each new one should say first and you agree the plan before anything gets built.

You see the actual email in the chat, not a description of it. Say which folder it is in and you get there in one go.

A button should say what happens next, which Shop Now and Learn More never do. Three buttons saying the same thing look fine on the page but read as a useless list to anyone using a screen reader.

The niggly fixes you redo every send are worth handing over in one go. Ask how many it found and you will know if it missed some.

Ask what is weak and you get more than "looks good". Better to hear it now than in the meeting.

Sorting out the layout first saves a long back and forth later. Words and pictures are easy to change afterwards, so the shape is the bit worth agreeing now.

A score does not tell you what to do next. A short list of fixes, worst first, does, and asking what already works stops you rewriting the good bits.

Ask for the plan first and you say yes once instead of checking every rename. The list also reminds you what is in there.

If translation goes to a tool or a person, you need the words out and back rather than done in place. Ask which section each line came from and putting it back is easy.

Code on its own leaves the next person guessing what the placeholders are for. Ask for a note with it and it becomes a proper handover.

Already drafting somewhere else? Paste it in and you get a real email you can style, check and export.

Two things count as waiting, and the forgotten one has no status at all, so it never turns up when you ask for "in review". Ask for both and nothing slips.

Name the folder and you get that folder, not the whole workspace. Landing pages turn up in the list too, but the emails are the ones you can build from.

Setting the language matters because screen readers use it to say the words properly. Ask to keep the layout the same, because translated text usually runs longer.

Doing them in one go keeps them all looking the same, which is what slips when you do them one by one. Each gets its language set so screen readers read it properly.

One message tags the whole folder instead of you clicking through every email. Ask for the list before and after, so you can check it and undo it.

The link already says which email you mean, so pasting it saves you answering four questions. Fastest way to point at one specific email.

Checking the design and checking the details are two different jobs, and the second is where the costly mistakes hide. Say what you want checked and it stays on those things.

Say the shape you want, a table, a list or a spreadsheet, and it comes back ready to paste. Ask for a link on each line and whoever reads it can click straight to the email.

Real text over a background picture looks the same but still reads when the picture does not load. Pick a text color that works on its own, because white on a dark photo turns into white on white.

Paste the code and you get an email you can edit again. Everything comes over except your social links, which take a minute to set.

Do it at the end of a good session, while it is all still fresh. Everything you had to explain gets written down, so next time starts where this one finished.

Hand over the report instead of typing numbers out. Where people actually clicked is the useful bit: lots of clicks on a footer link means the layout is burying the main one.

Keep the layout you know works and swap everything that makes it look like the wrong company. Say what to change, and read the footer before it goes out.

One email's numbers do not mean much; three months of them do. Ask what keeps working and which few to redo first, and you get a decision instead of a spreadsheet.

Saving gives you a link that opens the email itself. Whoever you send it to sees today's version, not a screenshot from last week.

Until you save it, it only exists in the chat. Say the folder and the name up front and you get one message instead of three questions, plus a link.

You can see where everything stands without opening a single design. Anything nobody has sent for review yet has no status at all, which tells you plenty.

You find out where you are allowed to save things before you build something you cannot save. Asking for recent workspaces keeps the list short instead of showing you every one anybody ever made.

You see your saved fonts, colors and button styles, so you know what to ask for later. Then say "use my saved styles" when you build and you get them.

The link always opens the latest version, and anything else you have connected can post it into the channel your reviewers already use. Keep the list of what to check to about four things, or it gets skimmed.

One layout you know converts can start every client instead of a blank canvas. Asking what still names the old client catches the footer, the legal line and the contact address, which is where a borrowed layout gives itself away.

A picture that says something needs describing; a decorative one is better left alone. Ask to hear them all read out in order, because that is how someone using a screen reader gets them.

Handy when a workspace has no saved styles yet, or the client's colors live somewhere else. Say them once and they stick for the rest of the chat.

Quicker than remembering names or clicking through folders. Ask for about three, which is what each workspace remembers.

A number gives it something to aim at. Ask to see what changed and you can put back anything it cut that mattered.

Explain it once and you get something you can run again. The point is not the typing, it is that the checks still happen when someone is rushing.

Tell it not to rewrite and signed-off words stay exactly as signed off. You get the layout without a pile of edits to argue about.

Paste the rows instead of describing them. Ask for the phone version at the same time and you avoid a table people have to scroll sideways.

You always name the email being replaced, so nothing gets overwritten by accident. Say you want it updated and that is the one that changes.

Point at pictures that are already online and you get those exact pictures, no swaps. Say how wide each one should be and they turn up the right size.

Ask for a few plus a pick and you get choices and a decision. Say the character limit and none of them get cut off in the inbox.