Copilot App starter for Castia scenarios
The demo belongs in another repository with a specific use case and the data to test it. This repo keeps the reusable package and Copilot extras.
Scenario repo files
Section titled “Scenario repo files”| Path | Purpose |
|---|---|
.github/copilot-instructions.md |
Durable repo rules, including model, cloud, and approval boundaries. |
.github/skills/castia-lifecycle |
Teaches Copilot the Castia build, test, evaluate, optimize, and deployment boundaries. |
.github/skills/foundry-story-flow |
Keeps the local -> Foundry -> Teams demo path on the Castia rails. |
.github/prompts/build-castia-agent.prompt.md |
A one click prompt for building the first agent. |
.github/prompts/test-castia-agent.prompt.md |
A one click prompt for trying the local agent and reporting evidence. |
README.md |
The human story, quickstart, and expected demo path. |
tests/ or evals/ |
The proof that the agent works for the chosen use case. |
Keep the scenario narrow. “Build a support triage agent for this inbox” is better than “build a useful agent.”
Suggested session contract
Section titled “Suggested session contract”Put this in the scenario repo instructions and tailor the names.
# Copilot instructions
This repository is a Castia scenario repo. It demonstrates one Foundry hosted agent end to end.
Use Castia from the package version pinned by this repo. Do not edit Castia itself from this workspace.
The default path is:
1. Build or update the local agent.2. Run the local tests or evals.3. Copy `.env.example` to `.env`, fill the Foundry endpoint and model deployment, and run `uv run --directory <agent-root> python main.py`.4. Try the agent locally through Foundry Agent Playground if it is available.5. Ask before provisioning, deploying, granting permissions, publishing to Teams, or spending money.6. After deployment, record the endpoint, model deployment, and Teams handoff steps in the repo.
Do not assume a model deployment name. Discover it or ask.
Prefer GPT-5 class models or newer when the Foundry project has them. If it does not, use the best available model only after saying what changed.First prompt
Section titled “First prompt”Use .github/prompts/build-castia-agent.prompt.md as the starter prompt. Keep that file canonical so the docs do not drift from the thing Copilot actually runs.