What you can ask an agent

Not everything deserves a procedure. The jobs below are one request each, and their whole difficulty is knowing they are possible. They work the same with the assistant built into the CMS and with your own agent over MCP, since both drive the same site through the same operations.

Tasks that have a guide keep their prompt in that guide. What follows is what has none.

Import a document

Here is the .docx. Read it, propose a mapping to our content-types
and the collection it should land in, and wait for my go before writing.
Keep the headings hierarchy and the links.

Check: the block structure follows the document rather than one long wysiwyg, and the images came across as real media rather than links to the original file.

Several formats go through, both for the integrated assistant and over MCP — Word documents, PDFs, spreadsheets (.csv, .xlsx) and images among them. If you have the source in more than one format, hand over the most structured one: a .docx carries its heading hierarchy, a PDF of the same document often does not, and what the agent cannot see in the structure it has to infer from the prose.

Translate a page

Translate this page into English. Keep the French as the source,
leave the page slug alone, and write one locale at a time.
Interface labels go through the dictionary, not into the content.

Check: no interface string was translated as content. For a collection entry, ask for the slug to be translated too — the reader gets an address in their language and the engine remaps the links — unless other entries reference that slug as a join key. See Run a multilingual site.

Generate a page from a brief

Create the "Workshops" page from workshops-brief.md.
Reuse the blocks of the content-kit page, do not invent a structure.
Leave it out of the menu and unpublished, then tell me what to review.

The longer form of this one, with the design system, is Let AI generate your content.

Describe a batch of images

List the media in the "itineraires" folder with no description,
write one for each, factual, under 120 characters, then apply them.
Show me the list first.

Rewrite for search

Rewrite the meta title and description of these six pages.
Under 60 and 155 characters, no superlatives, one page per line, for review.
Do not touch the body content.

Fix something everywhere

We changed the brand name from "Lisière" to "Lisière Revue".
Find every occurrence in page content, blocks and collection entries.
List them, then wait: I want to see the list before anything is written.

Check: the list first, always. A global replace on a live collection has no undo button.

Fill a collection from a list

Here are 30 rows: title, date, venue, ticket link.
Create one entry per row in the "evenements" collection, matching the existing fields.
Do the first one alone and show it to me, then do the other 29.

The one-then-the-rest shape is worth keeping: a wrong field name costs one entry instead of thirty.

Generate an illustration

Generate a wide header image for this article, same visual register as the
existing covers, no text in the image. Put it in the "couvertures" folder.

Audit before a launch

Go through every page: missing meta description, empty alt text,
untranslated field in the second locale, link pointing at a 404.
One table, no fixes yet.

Related