> For the complete documentation index, see [llms.txt](https://developer.frontitude.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.frontitude.com/mcp/examples.md).

# Examples

Try any of these with a connected agent. Copy the prompt and swap in your own project and category names.

## Check whether copy already exists

> Before I write a new error message for an expired invite, check whether we already have copy that says something close to this.

Your agent searches your library by meaning, then opens the closest matches in full. You get the wording, the status of each one, and the translations if you ask for them. Reuse what's already there instead of adding a near-duplicate.

## Create reusable components

> In the Web app project, take the texts on the Payment frame and turn the buttons and error messages into components in the Checkout category.

Your agent reads the frame, picks the texts that belong in the library, and creates the components. Ask for a dry run first. It reports everything it would create and writes none of it. Each converted text becomes an instance of its new component, so they share one value from then on.

## See what impact a change would have

> Which screens use the Save changes button component, and what changes on them if I rewrite it to Save and continue?

You get back every text using that component, with the project, page and frame each one sits in. Now you can see what the rewrite would change before you commit to it.

## Find what isn't translated yet

> How many components in the Onboarding category have no Japanese translation, and which ones are they?

The count comes first, broken down by language, so you see the size of the gap before your agent lists anything. Then it lists the components missing that language, ready to hand to your translator.

## Audit what isn't Final before a launch

> We ship the new billing screens on Friday. Tell me what copy is not Final yet across the Billing project, frame by frame.

Frame by frame, your agent counts by status, then lists everything short of Final: New, Draft and In Review. You know exactly what's left before Friday.

In the same conversation your agent can move the ones you approve to Final. That can start auto-translation, if your workspace has it on. Auto-translation spends your [translation allowance](/mcp/limits-and-errors.md).

{% content-ref url="/pages/f5nrPumVYUYHpxTImMNw" %}
[Getting good results](/mcp/getting-good-results.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.frontitude.com/mcp/examples.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.