Standardized project context for agents

One project. One context layer.

APC defines a neutral, repository-owned way to store agent-readable project context in a canonical .apc/ folder. It is designed for AI agents, editors, CLIs, and developer tooling that need a shared understanding of a project.

APC as a shared project context layer between AI applications and project data, knowledge, tools, and integrations.

Concept

Portable by default

APC keeps durable context in the repository instead of scattering it across tool-specific folders and private runtime state.

Scope

Project-level context

APC covers metadata, agent definitions, skills, curated project memory, and related project conventions. It does not define runtime execution or store private runtime state.

Interop

Compatible with MCP

APC and MCP solve different layers. APC standardizes project context. MCP connects agents to external tools and services.

Why APC

Teams increasingly maintain agent prompts, skills, rules, and memory in duplicated tool-specific locations such as:

.claude/
.cursor/
.windsurf/
.codex/
.opencode/

APC proposes a simpler model:

A project should own one durable context layer that any compatible tool can read.

What APC standardizes

project metadata
agent definitions
reusable skills
curated project memory
optional MCP registry hints

Start reading

Core principles

Portable
Project-owned
Human-readable
Tool-neutral
Filesystem-first

Current draft

The current APC draft uses a canonical .apc/ directory and treats the filesystem as the durable project-owned source of truth.

APC documentation in this site is intentionally protocol-oriented. It does not define a runtime, daemon, or vendor-specific workflow.