> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/public/readme_public.md).

# Public Assets

The `public/` directory contains static files that Vite serves and copies as-is. Use it for assets that need a stable browser URL instead of bundle-managed imports from `src/assets/`.

## URL Mapping

Files in this directory are served from the site root:

```
public/assets/trend-finder/trend-finder-engine-background.webp
-> /assets/trend-finder/trend-finder-engine-background.webp
```

Reference these paths with root-relative URLs in app code, metadata, or docs.

## Structure

| Path                   | Purpose                                                |
| ---------------------- | ------------------------------------------------------ |
| `favicon.svg`          | Root favicon linked from route metadata                |
| `assets/ai-os/`        | AI OS public/social media assets                       |
| `assets/trend-finder/` | Trend Finder public imagery used by extension surfaces |
| `README_public.md`     | Directory guide for public assets and path conventions |

The Trend Finder asset folder has its own [`README.md`](/ai-os-and-trend-finder-docs/public/assets/trend-finder.md) with the current image inventory.

## What Belongs Here

* Browser-visible static assets that need stable URLs.
* Social preview images and route metadata images.
* Public extension imagery referenced by root-relative paths.

Prefer `src/assets/` for app images that are imported by TypeScript, processed by Vite, or tightly coupled to a component module.

## Boundaries

* Do not place private runtime data, generated telemetry, logs, account auth, local environment files, screenshots with private data, or secret values here.
* Keep rich imagery compressed. Prefer WebP for photos and rendered artwork, SVG for vector icons, and PNG only when the use case requires it.
* Meaningful images need descriptive `alt` text where they are rendered.
* If adding larger assets or changing asset policy, update [`docs/media-policy.md`](/ai-os-and-trend-finder-docs/docs/media-policy.md).

## Validation

Run the narrowest useful check for the change:

```bash
bun run build
```

If the asset affects a browser-visible route, also run the relevant Playwright spec or the full E2E suite:

```bash
bun run test:e2e
```


---

# 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://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/public/readme_public.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.