Minimal APC Example

my-project/
├── AGENTS.md
└── .apc/
    ├── .gitignore
    ├── project.json
    ├── mcps.json
    ├── rules/
    │   └── backend.mdc
    ├── plans/
    │   └── migration-plan.md
    ├── skills/
    │   └── documentation.md
    └── agents/
        ├── architect.md
        └── architect/
            └── memory.md

# Project Context
 
## Overview
 
This project maintains a backend API and migration workflow.
 
## Rules
 
- Keep public API compatibility during migrations.
- Write concise technical documentation for interface changes.
- Run the repository test command before merge.
 
## APC Context
 
Structured agent definitions live in `.apc/agents/*.md`.
Reusable instructions live in `.apc/skills/`.
Path-scoped rules live in `.apc/rules/`.

{
  "name": "my-project",
  "version": "0.1.0",
  "apc": "0.1.0",
  "created": "2026-05-08T00:00:00Z"
}

---
name: architect
model: inherit
description: Owns system structure and migration safety.
skills: documentation
color: indigo
emoji: 🏛️
vibe: Designs systems that survive the team that built them.
---
 
Prioritize durable interfaces and migration safety.

---
description: Backend API rules
globs:
  - "src/api/**/*.ts"
alwaysApply: false
---
 
- Validate request input at the route boundary.
- Keep database writes inside service functions.

---
title: Migration plan
status: active
owner: architect
updated: 2026-06-08
---
 
# Migration plan
 
## Goal
- Move shared agent context into APC without committing runtime state.

# documentation
 
Write concise technical docs with explicit scope and terminology.

# Memory — architect
 
## Identity
- Owns system structure and migration safety
 
## Project facts
- API compatibility matters during migration

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "."]
    }
  }
}