> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bymiles.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Using existing assets

> Use copy, brand material, screenshots, and files to guide a new build.

Existing assets help Miles avoid generic output. They give the site real language, real constraints, and a visual world to respond to.

## Useful assets

* brand guidelines
* logos and color references
* existing copy
* product or service descriptions
* screenshots of current pages
* customer quotes or proof points
* photography or image direction
* competitor or inspiration URLs
* files with pricing, services, menus, locations, or policies

## How to use them

Tell Miles what each asset is for:

```text theme={"dark"}
Use the attached brand deck for tone and visual direction.

Use the service descriptions as source material,
but rewrite them for clarity.
```

```text theme={"dark"}
Use these screenshots to understand what the current site says.

Do not copy the layout directly.
```

Be clear about whether an asset is final source material or just inspiration. A screenshot, PDF, or reference URL can guide the direction, but Miles still needs you to say what matters.

## Using a coding agent

Give the agent the actual files and ask it to attach or provide them to Miles with a short explanation of each one. This is more reliable than asking the agent to describe a logo, image, or document from memory.

```text theme={"dark"}
Use the logo and content files in ./brand with Miles.

Tell Miles which file is the final logo and which documents contain approved copy. Do not rewrite the approved copy unless I ask.
```

## Review asset use

Check whether Miles preserved important facts, names, services, products, prices, locations, and claims. If something matters legally, commercially, medically, or financially, say so explicitly and review it before launch.