Knowledge across repositories

A step of the Cloud application tree on Gradus, in the Frontend area: Second app, UI, browser tests.

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.

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.

• Show on map
• This step as Markdown
• Every step of the tree, for AI assistants

This is https://gradus.kazet.blog/tree/cloud-application/step/knowledge-across-repos as plain HTML. In a browser the page also lets you mark the step forged and copy a message for your AI assistant.