# Knowledge across repositories

A step of the [Cloud application](https://gradus.kazet.blog/tree/cloud-application) tree on Gradus, in the Frontend area: Second app, UI, browser tests.

Page: https://gradus.kazet.blog/tree/cloud-application/step/knowledge-across-repos

Register both knowledge bases in one place the assistant reads in every session, so a change in the API is visible from the frontend repository and the other way round.

Usually comes after: [A second repository](https://gradus.kazet.blog/tree/cloud-application/step/frontend-repository).

## Prompt for your AI assistant

```
Set up a registry of knowledge bases that an AI assistant reads at the start of every session across both repositories, using Globu or an equivalent tool: register this repository's docs/ and the frontend repository's docs/ with a one-sentence description of each and when to read it. Verify from the frontend repository that a question about the API's health route is answered from the service repository's docs. Record how to register a new base in docs/index.md of both repositories.
```

Every step of the tree: https://gradus.kazet.blog/tree/cloud-application/llms.txt
