Project Structure
Orient yourself in the Microsoft Agent Framework .NET monorepo so you know which package, sample, or test project to open before changing agents or providers.
Overview
Project-structure is an agent skill most often used in Build (also Ship review, Operate iterate) that explains the Agent Framework .NET repo layout across src, tests, samples, and shared code.
Install
npx skills add https://github.com/microsoft/agent-framework --skill project-structureWhat is this skill?
- Maps dotnet/src packages: Microsoft.Agents.AI core, Abstractions, A2A, OpenAI, Foundry v2, legacy Azure persistent, Anth
- Explains tests/ naming: UnitTests and IntegrationTests per source project
- Documents samples/ for runnable references and Shared/LegacySupport include patterns
- Table-style folder guide for src, tests, and samples responsibilities
- Documents 8+ named src packages including core, abstractions, A2A, OpenAI, Foundry, Anthropic, and Workflows
Adoption & trust: 26 installs on skills.sh; 11.2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You opened agent-framework but cannot tell which .NET project holds workflows, which holds OpenAI bindings, or where integration tests live.
Who is it for?
Developers new to Microsoft.Agents.AI who need a mental map before patching providers, workflows, or samples.
Skip if: Builders not using the agent-framework .NET repo who need generic solution templates unrelated to this layout.
When should I use this skill?
User is working in or contributing to the Microsoft Agent Framework .NET repository and needs to understand project layout and package boundaries.
What do I get? / Deliverables
You know exactly which folder and package to edit, which test project to run, and where samples illustrate the pattern you need.
- Accurate map of src/, tests/, and samples/ targets for the requested change
- Pointer to the correct package and matching test or sample project name
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
First meaningful touchpoint is Build when you clone agent-framework to extend agents, providers, or workflows—the skill prevents wrong-folder edits before Ship. Agent-tooling is the right shelf because the content maps src packages (OpenAI, A2A, Workflows, Foundry) and how samples/tests mirror them.
Where it fits
Pick Microsoft.Agents.AI.Anthropic vs OpenAI project before adding a new tool-calling sample.
Locate Foundry v2 vs legacy AzureAI.Persistent provider code before swapping endpoints.
Trace a failing CI job to the correct IntegrationTests project for the package you changed.
Onboard a collaborator by naming samples/ entry points that mirror production agent wiring.
How it compares
Use this explainer skill instead of generic repo-wide grep when you need package-level boundaries in a large agent monorepo.
Common Questions / FAQ
Who is project-structure for?
Solo and indie developers working in microsoft/agent-framework who need fast orientation across many NuGet-style projects and test twins.
When should I use project-structure?
At the start of Build agent-tooling work when choosing where to implement a provider; during Ship review when tracing which test project covers a failing package; during Operate iterate when onboarding a teammate to the same repo.
Is project-structure safe to install?
It is read-only documentation in the agent; review the Security Audits panel on this Prism page like any third-party skill before enabling it in your coding agent.
SKILL.md
READMESKILL.md - Project Structure
# Agent Framework .NET Project Structure ``` dotnet/ ├── src/ │ ├── Microsoft.Agents.AI/ # Core AI agent implementations │ ├── Microsoft.Agents.AI.Abstractions/ # Core AI agent abstractions │ ├── Microsoft.Agents.AI.A2A/ # Agent-to-Agent (A2A) provider │ ├── Microsoft.Agents.AI.OpenAI/ # OpenAI provider │ ├── Microsoft.Agents.AI.Foundry/ # Microsoft Foundry Agents (v2) provider │ ├── Microsoft.Agents.AI.AzureAI.Persistent/ # Legacy Microsoft Foundry Agents (v1) provider │ ├── Microsoft.Agents.AI.Anthropic/ # Anthropic provider │ ├── Microsoft.Agents.AI.Workflows/ # Workflow orchestration │ └── ... # Other packages ├── samples/ # Sample applications └── tests/ # Unit and integration tests ``` ## Main Folders | Folder | Contents | |--------|----------| | `src/` | Source code projects | | `tests/` | Test projects — named `<Source-Code-Project>.UnitTests` or `<Source-Code-Project>.IntegrationTests` | | `samples/` | Sample projects | | `src/Shared`, `src/LegacySupport` | Shared code files included by multiple source code projects (see README.md files in these folders or their subdirectories for instructions on how to include them in a project) |