Skill: andreagriffiths11/agent-context (version 1.3.0)

--- name: agent-context-system description: A persistent local-only memory system for AI coding agents. Two files, one idea — AGENTS.md (committed, shared) + .agents.local.md (gitignored, personal). Agents read both at session start, update the scratchpad at session end, and promote stable patterns over time. Works across Claude Code, Cursor, Copilot, Windsurf. Subagent-ready. No plugins, no infrastructure, no background processes. license: MIT metadata: author: AndreaGriffiths11 version: "1.0.0" --- # Agent Context System ## The Problem Agents start from zero every session. You spend an hour getting your coding agent up to speed on a project, close the session, and start from zero the next day. The agent forgot everything. Every session is a cold start. This isn't a limitation of the model. It's a context delivery problem. The agents have the capacity to remember — they just don't have the right inputs at the right time in the right format. ## The Solution Two markdown files. One committed, one gitignored. The agent reads both at the start of every session and updates the local one at the end. - **`AGENTS.md`** — Your project's source of truth. Committed and shared. Always in the agent's prompt. Under 120 lines. Contains compressed project knowledge: patterns, boundaries, gotchas, commands, architecture. - **`.agents.local.md`** — Your personal scratchpad. Gitignored. Grows over time as the agent logs what it learns each session. Session notes, dead ends, preferences, patterns that haven't been promoted yet. That's it. No plugins, no infrastructure, no background processes. The convention lives inside the files themselves, and the agent follows it. ## How It Works ### 1. Setup Run the init script. It creates `.agents.local.md` from a template, ensures it's gitignored, and wires up your agent tool's config (CLAUDE.md symlink for Claude Code, .cursorrules for Cursor, .windsurfrules for Windsurf, copilot-instructions.md for Copilot). ```bash # If you cloned the template repo: ./scripts/init-agent-context.sh # If you installed as a skill (npx skills add): bash .agents/skills/agent-context-system/scripts/init-agent-context.sh ``` Then edit `AGENTS.md` with your project specifics: name, stack, commands, actual patterns and gotchas from your codebase. This is the highest-leverage edit you'll make. ### 2. During Sessions The agent reads both files at session start. `AGENTS.md` gives it compressed project knowledge. `.agents.local.md` gives it accumulated learnings from past sessions. The agent now has context that persists across sessions. At session end, the agent appends to the scratchpad's Session Log: what changed, what worked, what didn't, decisions made, patterns learned. Most agents (Copilot Chat, Cursor, Windsurf) don't have session-end hooks, so this depends on Rule 7 in `AGENTS.md` being seen and acted on, or the user saying "log this session." Claude Code handles this automatically via auto memory. ### 3. Over Time The scratchpad grows. When it hits 300 lines, the agent compresses: deduplicate, merge related entries, keep it tight. During compression, if a pattern has shown up across 3+ sessions, the agent flags it in the scratchpad's "Ready to Promote" section using the same pipe-delimited format that `AGENTS.md` expects. You decide when to move flagged items from the scratchpad into `AGENTS.md`. The scratchpad is where things are experimental. `AGENTS.md` is where proven knowledge lives. ``` Session notes → .agents.local.md → agent flags stable patterns → you promote to AGENTS.md (personal) (shared) ``` ## Scripts The template includes five scripts: ### `init-agent-context.sh` Sets up the local agent scratchpad and agent tool integrations. Run once per clone. Safe to re-run. - Creates `.agents.local.md` from template - Ensures `.agents.local.md` is gitignored - Asks which agents you use (Claude, Cursor, Windsurf, Copilot) and wires up the right config - Creates CLAUDE.md symlink for Claude Code (since it doesn't read AGENTS.md yet) - Adds agent context directive to .cursorrules, .windsurfrules, or copilot-instructions.md ### `compress.sh` Compresses the scratchpad when it exceeds 300 lines. Deduplicates, merges related entries, flags stable patterns for promotion. Not yet implemented — instructions for the agent are in AGENTS.md's Local Context section. ### `promote.sh` Moves flagged items from `.agents.local.md`'s "Ready to Promote" section into `AGENTS.md`. Not yet implemented — currently a manual step. ### `validate.sh` Validates `AGENTS.md` stays under 120 lines and checks format consistency. Not yet implemented. ### `publish-template.sh` Push to GitHub and mark as a template repo. Run once. Creates a private GitHub repo and marks it as a template so you can use it to create new projects with `gh repo create my-project --template YOUR_USERNAME/agent-context-system --private`. ## Knowledge Flow Knowledge doesn't just sit in one place. It flows. Learnings start as session notes in `.agents.local.md`. The agent writes them at the end of each session. During compression, if a pattern has shown up across 3+ sessions, the agent flags it in the scratchpad's "Ready to Promote" section using the same pipe-delimited format that `AGENTS.md` expects. Then you decide when to move it into `AGENTS.md`. ``` Session notes → .agents.local.md → agent flags stable patterns → you promote to AGENTS.md (personal) (shared) ``` The scratchpad is where things are still experimental. `AGENTS.md` is where proven knowledge lives. The agent flags candidates. You make the call. ## AGENTS.md Template Structure The template `AGENTS.md` includes: ### Project Basic metadata: name, stack, package manager. Keep it one-liners. ### Commands Executable commands for build, test, lint, dev server. These go early because agents need them immediately. ### Architecture One line per directory. The agent gets high-level structure on every turn without needing to look anything up. ### Project Knowledge (Compressed) This is the most important section. Three subsections: - **Patterns** — `pattern | where-to-see-it` format. Named exports only, server components default, Zustand for client state, Result types not try/catch. - **Boundaries** — `rule | reason` format. Never modify src/generated, env vars through src/config, no default exports, no inline styles. - **Gotchas** — `trap | fix` format. pnpm build hides type errors, dev sessions expire after 24h, integration tests need DB up. Vercel's evals showed passive context (always in the prompt) achieves 100% pass rate vs 53% when agents must decide to look things up. This section is passive context. The agent gets it on every turn automatically. ### Rules Numbered list. Read AGENTS.md and .agents.local.md first. Plan before code. Locate files before changing. Only touch what the task requires. Run tests after every change. Summarize changes. ### Deep References Points to `agent_docs/` for when a task needs more depth than the compressed version provides. Conventions, architecture, gotchas — full detail, loaded on demand. ### Local Context Instructions for reading and updating `.agents.local.md`. Explains session-to-session learning, compression protocol, promotion pathway. Tells subagents to explicitly read the scratchpad (they don't inherit main conversation history). ## .agents.local.md Template Structure The template `.agents.local.md` includes: ### Preferences Your style, code preferences, planning preferences. Friendly vs technical tone. Minimal changes vs comprehensive refactors. Always state the plan before writing code. ### Patterns Settled truths about this project. Promote recurring session learnings here. ### Gotchas Things that look right but aren't. Include WHY. ### Dead Ends Approaches tried and failed. Include WHY they failed. Saves the agent from repeating mistakes. ### Ready to Promote The agent flags items here during compression when a pattern has recurred across 3+ sessions. Use the same pipe-delimited format `AGENTS.md` expects. The human decides when to move flagged items into `AGENTS.md`. ### Session Log Append new entries at the END. One entry per session. Keep each to 5-10 lines. Template: what changed, what worked, what didn't, decisions, learnings. ### Compression Log When the file exceeds 300 lines, compress. Log it here. ## Agent Compatibility The template works across all major agent tools: | Agent | Config File | What It Does | |---|---|---| | Claude Code | CLAUDE.md | Symlink → AGENTS.md (Claude doesn't read AGENTS.md yet) | | Cursor | .cursorrules | Directive pointing to AGENTS.md | | Windsurf | .windsurfrules | Directive pointing to AGENTS.md | | GitHub Copilot | .github/copilot-instructions.md | Directive pointing to AGENTS.md | ### Claude Code Auto Memory Claude Code shipped auto memory in late 2025. It creates a `~/.claude/projects/<project>/memory/` directory where Claude writes its own notes and loads them at session start. That's basically the `.agents.local.md` concept built into the tool. If you use Claude Code exclusively, auto memory handles session-to-session learning and the scratchpad is optional. The template's value for you is the `AGENTS.md` file itself and the promotion pathway that gives you a structured way to take what auto memory learns and move the stable parts into your root file. If your team uses multiple agents (GitHub just shipped Agent HQ with Copilot, Claude, and Codex side by side), the scratchpad matters because auto memory only works in Claude Code. The scratchpad works everywhere. ## Subagent Context Claude Code now ships subagents. Copilot CLI just shipped /fleet in experimental mode. Both tools are moving toward the same model: a lead agent that coordinates a team of specialists. Subagents don't inherit the main conversation's history. Each one starts with a clean context window. The only shared knowledge they all have is your root instruction file. So when you go from one agent to five parallel agents, `AGENTS.md` goes from "helpful project context" to "the only thing preventing five agents from independently making conflicting decisions about your codebase." The compressed project knowledge, the boundaries section, the gotchas — that's the shared brain. Without it, each subagent rediscovers your project from scratch. This is why the template explicitly tells subagents to read `.agents.local.md` too. They won't get it by default. They need the instruction. It's also why instruction budget discipline matters even more. If your `AGENTS.md` is 500 lines, you're paying that token cost for every subagent you spawn. Under 120 lines is a feature, not a limitation. ## Research Foundation This template is built on research from: - **LangChain** — Context Engineering for Agents: Write/Select/Compress/Isolate framework - **HumanLayer** — Writing a Good CLAUDE.md: instruction budgets, root file discipline - **GitHub** — Lessons from 2,500+ Repositories: what makes agents.md files actually work - **Vercel** — AGENTS.md Outperforms Skills: passive context vs skill retrieval eval data - **Anthropic** — Equipping Agents with Skills: three-tier progressive disclosure - **AI Hero** — A Complete Guide to AGENTS.md: cross-platform standard adoption - **Anthropic** — Claude Code Subagents: context isolation, custom agents - **GitHub** — Copilot CLI /fleet: parallel fleets with dependency-aware tasks Key finding: frontier LLMs reliably follow about 150-200 instructions. Claude Code's system prompt already uses about 50. So anything in your root file that isn't universally applicable risks getting quietly deprioritized. That's why `AGENTS.md` stays under 120 lines and uses compressed formats (pipe-delimited patterns, boundaries, gotchas). Dense beats verbose. Another key finding: Vercel's evals showed passive context (always in prompt) achieves 100% pass rate vs 53% when agents must decide to look things up. Available docs aren't the same as used docs. Put critical knowledge where the agent literally cannot miss it. ## Getting Started ### New repo from template ```bash gh repo create my-project --template YOUR_USERNAME/agent-context-system --private cd my-project chmod +x scripts/init-agent-context.sh ./scripts/init-agent-context.sh ``` ### Installed as a skill If you installed via `npx skills add`, the scripts live inside the skill directory, not at the project root. Run from there: ```bash bash .agents/skills/agent-context-system/scripts/init-agent-context.sh ``` ### Existing repo Copy `AGENTS.md`, `agent_docs/`, and `scripts/` into your project root, then run the init script. ### Publish this as your template ```bash chmod +x scripts/publish-template.sh ./scripts/publish-template.sh ``` ## After Setup 1. **Edit `AGENTS.md`.** Fill in your project name, stack, commands. Replace the placeholder patterns and gotchas with real ones from your codebase. This is the highest-leverage edit you'll make. 2. **Fill in `agent_docs/`.** Add deeper references. Delete what doesn't apply. 3. **Customize `.agents.local.md`.** Add your preferences. 4. **Work.** The agent reads everything, does the task, updates the scratchpad. 5. **Promote what sticks.** During compression, the agent flags patterns that have recurred across 3+ sessions in the scratchpad's "Ready to Promote" section. You decide when to move them into `AGENTS.md`. ## File Structure ``` your-repo/ ├── AGENTS.md # Committed. Always loaded. Under 120 lines. ├── .agents.local.md # Gitignored. Personal scratchpad. ├── agent_docs/ # Deeper docs. Read only when needed. │ ├── conventions.md # Full code patterns, naming, file structure │ ├── architecture.md # System design, data flow, key decisions │ └── gotchas.md # Extended known traps with full explanations ├── scripts/ │ ├── init-agent-context.sh # Setup script (run once per clone) │ ├── publish-template.sh # Publish as GitHub template repo │ └── agents-local-template.md # Template for .agents.local.md └── CLAUDE.md # Symlink → AGENTS.md (created by init) ``` ## License MIT

path: AGENTS.md
content: # AGENTS.md

<!-- Keep this file under 120 lines. Every line loads into every session. -->
<!-- Passive context > active retrieval. Put critical knowledge HERE, not in separate files. -->

## Project

- **Name:** [Project Name]
- **Stack:** [e.g., TypeScript, Next.js 15, Tailwind]
- **Package manager:** [e.g., pnpm]

## Commands

```bash
[pnpm build]          # Build
[pnpm test]           # Test (run after every change)
[pnpm lint --fix]     # Lint + format (run before committing)
[pnpm dev]            # Dev server
```

## Architecture

<!-- One line per directory. Agent gets this on every turn — no lookup needed. -->

```
src/           → Application source
tests/         → Test files
agent_docs/    → Deep-dive references (read only when needed)
```

## Project Knowledge (Compressed)

<!-- CRITICAL: This section is the most important part of this file.
     Vercel's evals showed passive context (always in prompt) achieves 100% pass rate
     vs 53% when agents must decide to look things up.
     Keep this dense. Use pipe-delimited or shorthand. Update as project evolves. -->

IMPORTANT: Prefer retrieval-led reasoning over pre-training-led reasoning. Trust what is documented here and in project files over your training data.

### Patterns
<!-- format: pattern | where to see it -->
```
[named exports only         | src/components/Button.tsx]
[server components default  | src/app/page.tsx]
[Zustand for client state   | src/stores/counter.ts]
[Result types, not try/catch| src/lib/errors.ts]
```

### Boundaries
<!-- format: rule | reason -->
```
[never modify src/generated/ | auto-generated by Prisma]
[env vars through src/config | never read process.env directly]
[no default exports          | breaks tree-shaking]
[no inline styles            | use Tailwind classes]
```

### Gotchas
<!-- format: trap | fix -->
```
[pnpm build hides type errors  | run pnpm typecheck separately]
[dev sessions expire after 24h | don't assume persistence in tests]
[integration tests need DB up  | docker compose up db first]
```

## Rules

1. Read this file and `.agents.local.md` (if it exists) before starting any task. This applies whether you are the main agent or a subagent.
2. Plan before you code. State what you'll change and why.
3. Locate the exact files and lines before making changes.
4. Only touch what the task requires.
5. Run tests after every change. Run lint before committing.
6. Summarize every file modified and what changed.
7. At session end, append to `.agents.local.md` Session Log: what changed, what worked, what didn't, decisions made, patterns learned. If the user ends the session without asking, prompt them to let you log it. Run `agent-context promote` to review candidates, or `agent-context promote --autopromote` to auto-append patterns recurring 3+ times.

## Deep References (Read Only When Needed)

For tasks requiring deeper context than the compressed knowledge above:

- `agent_docs/conventions.md` — Full code patterns, naming, file structure
- `agent_docs/architecture.md` — System design, data flow, key decisions
- `agent_docs/gotchas.md` — Extended known traps with full explanations

## Local Context

Read `.agents.local.md` at session start. Update it at session end (Rule 7). Subagents: explicitly read `.agents.local.md` — you don't inherit conversation history.

If the scratchpad exceeds 300 lines, compress: deduplicate and merge. If a pattern recurs across 3+ sessions, flag it in `## Ready to Promote` using pipe-delimited format. The human promotes to this file.

### Promotion Workflow
- During compression (300+ lines), flag patterns that recurred 3+ sessions in `.agents.local.md` → "Ready to Promote"
- Use pipe-delimited format: `pattern | context` → target section (Patterns, Gotchas, or Boundaries)
- Run `agent-context promote --autopromote` to automatically append flagged patterns to AGENTS.md
- Or review manually with `agent-context promote` and decide what moves to this file
- After promoting: remove the item from Ready to Promote in `.agents.local.md`
- If an item is already captured in AGENTS.md, clear it from Ready to Promote — don't duplicate


path: README.md
content: # Agent Context System

Coding agents are good at using context. They are terrible at keeping it consistent.

Tools like GitHub Copilot Memory are doing great work on the individual side. Copilot remembers your preferences, your patterns, your stack. That's a real step forward for developer experience.

But there's a layer that built-in memory doesn't cover: shared, reviewable, version-controlled project context. The stuff that lives in your repo and works across every agent your team uses. Teams still hit the same walls:

- The "rules of the repo" live in chat threads and tribal knowledge
- A new agent or subagent starts without the constraints that matter
- The agent learns something once, then you can't review it like code
- Context drifts because nobody promotes stable decisions into a shared source of truth

This project is a small, boring fix. It doesn't replace built-in memory. It complements it. Built-in memory handles what the tool learns about *you*. This handles what every agent needs to know about *your project*. It makes that context explicit, reviewable, and portable.

## What this is

Two markdown files. One committed, one gitignored. The agent reads both at the start of every session and updates the local one at the end.

- `AGENTS.md` is your project's source of truth. Committed and shared. Always in the agent's prompt.
- `.agents.local.md` is your personal scratchpad. Gitignored. It grows over time as the agent logs what it learns each session.

That's it. No plugins, no infrastructure, no background processes. The convention lives inside the files themselves, and the agent follows it.

```
your-repo/
├── AGENTS.md                    # Committed. Always loaded. Under 120 lines.
├── .agents.local.md             # Gitignored. Personal scratchpad.
├── agent-context                # CLI: init, validate, promote commands.
├── agent_docs/                  # Deeper docs. Read only when needed.
│   ├── conventions.md
│   ├── architecture.md
│   └── gotchas.md
├── scripts/
│   └── init-agent-context.sh    # Wrapper → calls agent-context init (for npx skills)
└── CLAUDE.md                    # Symlink → AGENTS.md (created by init)
```

**Note:** `agent-context` is the main CLI. `scripts/init-agent-context.sh` is a thin wrapper for backwards compatibility with `npx skills add` installs — it just calls `agent-context init`.

## Install

### OpenClaw users (ClawHub)

```bash
clawhub install agent-context
agent-context init
```

### Copilot Custom Skill

```bash
npx skills add AndreaGriffiths11/agent-context-system
bash .agents/skills/agent-context-system/scripts/init-agent-context.sh
```

Or copy `github-copilot/SKILL.md` to `.github/skills/agent-context-system/SKILL.md`.

### GitHub Template

```bash
gh repo create my-project --template AndreaGriffiths11/agent-context-system
cd my-project
./agent-context init
```

## CLI Commands

```bash
agent-context init      # Set up context system in current project
agent-context validate  # Check setup is correct
agent-context promote   # Find patterns to move from scratchpad to AGENTS.md
agent-context promote --autopromote  # Auto-append patterns recurring 3+ times
```

## How knowledge moves

<img width="955" height="502" alt="knowledge flow" src="https://github.com/user-attachments/assets/a5c29763-9eb4-48ef-878d-935797b6febe" />

1. **Write**: Agent logs learnings to `.agents.local.md` at session end
2. **Compress**: Scratchpad compresses when it hits 300 lines
3. **Flag**: Patterns recurring 3+ times get flagged "Ready to Promote"
4. **Promote**: Run `agent-context promote` to review, or `--autopromote` to auto-append to `AGENTS.md`

---

<details>
<summary><strong>The Research (Why this works)</strong></summary>

### Agents have an instruction budget (~150-200 instructions)

HumanLayer found frontier LLMs reliably follow about 150-200 instructions. Claude Code's system prompt eats ~50. That's why `AGENTS.md` stays under 120 lines.

### Available docs ≠ used docs

Vercel ran evals:
- No docs: 53% pass rate
- Skills where agent decides when to read: **53%** (identical to nothing)
- Compressed docs embedded in root file: **100%**

When docs are embedded directly, the agent cannot miss them.

### Context has a lifecycle

LangChain's framework: Write, Select, Compress, Isolate.

- **Write**: Scratchpad at session end
- **Select**: Read both files at start
- **Compress**: At 300 lines, dedupe and merge
- **Isolate**: Project vs personal (committed vs gitignored)

### Deep docs load on demand

AGENTS.md every time. `agent_docs/` only when the task needs depth.

### One file, every tool

AGENTS.md: Cursor, Copilot, Codex, Windsurf all read it. Claude Code still needs CLAUDE.md (symlink handled by init).

</details>

<details>
<summary><strong>Agent Compatibility</strong></summary>

| Agent | Setup |
|-------|-------|
| OpenClaw | `clawhub install agent-context` — reads AGENTS.md natively |
| Claude Code | `CLAUDE.md` symlink → `AGENTS.md` |
| Cursor | `.cursorrules` pointing to AGENTS.md |
| Windsurf | `.windsurfrules` pointing to AGENTS.md |
| GitHub Copilot | `.github/copilot-instructions.md` pointing to AGENTS.md |

**Claude Code note:** Auto memory (late 2025) handles session-to-session learning in `~/.claude/projects/<project>/memory/`. If you use Claude exclusively, auto memory covers the scratchpad's job. The value here is AGENTS.md itself: structured promotion pathway, instruction budget discipline, and cross-agent compatibility.

</details>

<details>
<summary><strong>Subagents: When one becomes five</strong></summary>

Claude Code has subagents. Copilot CLI has `/fleet` (experimental). Both dispatch parallel agents that don't inherit conversation history.

<img width="855" height="635" alt="subagent context isolation" src="https://github.com/user-attachments/assets/c561960b-6f87-4753-9381-8762c35cbcb6" />

Each subagent starts fresh. The only shared brain is your root instruction file. AGENTS.md goes from "helpful context" to "the only thing preventing five agents from making conflicting decisions."

This is why the template explicitly tells subagents to read `.agents.local.md` too. They won't get it otherwise.

</details>

<details>
<summary><strong>Session Logging Reality</strong></summary>

Agents don't have session-end hooks. Sessions end when you stop talking. Logging only happens if:

1. Agent proactively logs before conversation ends (rare), or
2. **You prompt it:** "log this session" or "update the scratchpad"

Claude Code handles this well with auto memory. For others, get in the habit of prompting for the log when meaningful work was done.

</details>

---

## After setup

1. **Edit `AGENTS.md`** — Fill in your project name, stack, commands. Replace placeholders with real patterns from your codebase.
2. **Fill in `agent_docs/`** — Add deeper references. Delete what doesn't apply.
3. **Customize `.agents.local.md`** — Add your preferences.
4. **Work** — Agent reads both files, does the task, updates scratchpad.
5. **Promote** — Run `agent-context promote` to see flagged patterns. Move stable ones to AGENTS.md.

## Sources

| Finding | Source |
|---------|--------|
| Instruction budgets | [HumanLayer](https://www.humanlayer.dev/blog/writing-a-good-claude-md) |
| Passive context 100% pass rate | [Vercel](https://vercel.com/blog/agents-md-outperforms-skills-in-our-agent-evals) |
| 2,500+ repos analyzed | [GitHub](https://github.blog/ai-and-ml/github-copilot/how-to-write-a-great-agents-md-lessons-from-over-2500-repositories/) |
| Context lifecycle framework | [LangChain](https://blog.langchain.com/context-engineering-for-agents/) |
| Three-tier progressive disclosure | [Anthropic](https://www.anthropic.com/engineering/equipping-agents-for-the-real-world-with-agent-skills) |

## License

MIT


path: agent_docs/architecture.md
content: # Architecture

<!-- This file is loaded only when a task involves design decisions or cross-cutting changes. -->

## System Overview

- [e.g., Monolithic Next.js app with API routes. PostgreSQL via Prisma. Auth via NextAuth.]

## Data Flow

- [e.g., Client → API route → Prisma → PostgreSQL. No direct DB access from components.]

## Key Decisions

- [e.g., We use server components by default. Client components only when interactivity is required.]
- [e.g., State management: Zustand for client state. No Redux.]

## Boundaries

- [e.g., Never modify `src/generated/` — these are auto-generated by Prisma.]
- [e.g., All env vars go through `src/config.ts` — never read `process.env` directly.]

## External Dependencies

- [e.g., Stripe for payments — webhook handler at `src/api/webhooks/stripe.ts`]
- [e.g., Cloudinary for images — helper at `src/lib/cloudinary.ts`]


path: agent_docs/conventions.md
content: # Code Conventions

<!-- This file is loaded only when a task involves writing or modifying code. -->
<!-- Keep entries specific and actionable. Prefer file:line pointers over code snippets. -->

## Naming

- [e.g., camelCase for variables, PascalCase for components, kebab-case for files]

## File Structure

- [e.g., One component per file. Co-locate tests with source files.]

## Patterns to Follow

- [e.g., Use named exports, not default exports]
- [e.g., Error handling: use Result types, not try/catch]

## Patterns to Avoid

- [e.g., No `any` types in TypeScript]
- [e.g., No inline styles — use Tailwind classes]

## Examples

<!-- Point to existing code rather than pasting snippets. Code changes; pointers are cheaper to maintain. -->

- Good component pattern: see `src/components/Button.tsx`
- Good API route pattern: see `src/api/users.ts`


path: agent_docs/gotchas.md
content: # Gotchas

<!-- This file is loaded when starting unfamiliar tasks or debugging unexpected behavior. -->
<!-- Each entry: what looks right, what's actually wrong, and how to handle it. -->

## Build & Deploy

- [e.g., `pnpm build` silently succeeds even with type errors. Always run `pnpm typecheck` separately.]

## Database

- [e.g., Prisma migrations must be run in order. Never skip a migration even if the schema looks correct.]

## Auth

- [e.g., Session tokens expire after 24h in dev but 7d in prod. Don't assume session persistence in tests.]

## Testing

- [e.g., Integration tests require the dev DB to be running. `docker compose up db` first.]

## Third-Party APIs

- [e.g., Stripe webhook signatures fail in dev unless you run `stripe listen --forward-to localhost:3000/api/webhooks/stripe`.]


path: docs/subagent-context.svg
content: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 780 560" width="780" height="560" font-family="'Segoe UI', system-ui, -apple-system, sans-serif">
  <rect width="780" height="560" fill="white"/>

  <!-- Title -->
  <text x="390" y="35" text-anchor="middle" font-size="24" font-weight="600" fill="#1e1e1e">What Subagents Actually See</text>

  <!-- AGENTS.md box -->
  <rect x="250" y="65" width="260" height="60" rx="10" fill="#b2f2bb" stroke="#22c55e" stroke-width="2"/>
  <text x="380" y="102" text-anchor="middle" font-size="20" font-weight="600" fill="#1e1e1e">AGENTS.md</text>
  <text x="380" y="145" text-anchor="middle" font-size="13" fill="#22c55e">Loaded automatically by every agent</text>

  <!-- Green arrows from AGENTS.md to subagents -->
  <defs>
    <marker id="arrow-green" markerWidth="10" markerHeight="7" refX="9" refY="3.5" orient="auto">
      <polygon points="0 0, 10 3.5, 0 7" fill="#22c55e"/>
    </marker>
    <marker id="arrow-amber-up" markerWidth="10" markerHeight="7" refX="9" refY="3.5" orient="auto">
      <polygon points="0 0, 10 3.5, 0 7" fill="#f59e0b"/>
    </marker>
  </defs>

  <line x1="310" y1="125" x2="155" y2="235" stroke="#22c55e" stroke-width="2" marker-end="url(#arrow-green)"/>
  <line x1="380" y1="125" x2="380" y2="235" stroke="#22c55e" stroke-width="2" marker-end="url(#arrow-green)"/>
  <line x1="450" y1="125" x2="615" y2="235" stroke="#22c55e" stroke-width="2" marker-end="url(#arrow-green)"/>

  <!-- Subagent boxes -->
  <rect x="50" y="240" width="170" height="50" rx="10" fill="#a5d8ff" stroke="#4a9eed" stroke-width="2"/>
  <text x="135" y="271" text-anchor="middle" font-size="17" font-weight="500" fill="#1e1e1e">Explore</text>

  <rect x="290" y="240" width="180" height="50" rx="10" fill="#a5d8ff" stroke="#4a9eed" stroke-width="2"/>
  <text x="380" y="271" text-anchor="middle" font-size="17" font-weight="500" fill="#1e1e1e">Code Review</text>

  <rect x="540" y="240" width="170" height="50" rx="10" fill="#a5d8ff" stroke="#4a9eed" stroke-width="2"/>
  <text x="625" y="271" text-anchor="middle" font-size="17" font-weight="500" fill="#1e1e1e">Debug</text>

  <!-- Divider label -->
  <text x="390" y="330" text-anchor="middle" font-size="15" font-weight="600" fill="#ef4444">What does NOT flow to subagents:</text>

  <!-- Conversation History (red, blocked) -->
  <rect x="60" y="360" width="260" height="48" rx="10" fill="#ffc9c9" stroke="#ef4444" stroke-width="2"/>
  <text x="190" y="390" text-anchor="middle" font-size="16" font-weight="500" fill="#1e1e1e">Conversation History</text>
  <text x="340" y="392" font-size="26" font-weight="700" fill="#ef4444">✕</text>

  <!-- .agents.local.md (yellow, conditional) -->
  <rect x="410" y="360" width="280" height="48" rx="10" fill="#fff3bf" stroke="#f59e0b" stroke-width="2"/>
  <text x="550" y="390" text-anchor="middle" font-size="16" font-weight="500" fill="#1e1e1e">.agents.local.md</text>

  <!-- Dashed arrow from scratchpad up to subagents -->
  <line x1="550" y1="360" x2="550" y2="300" stroke="#f59e0b" stroke-width="2" stroke-dasharray="6,4" marker-end="url(#arrow-amber-up)"/>
  <text x="550" y="428" text-anchor="middle" font-size="13" fill="#f59e0b">Only if AGENTS.md tells them to read it</text>

  <!-- Bottom line -->
  <text x="390" y="490" text-anchor="middle" font-size="15" fill="#1e1e1e">AGENTS.md is the only shared context across all parallel agents.</text>
  <text x="390" y="515" text-anchor="middle" font-size="15" fill="#1e1e1e">That's why instruction budget discipline matters ×5.</text>
</svg>


path: package.json
content: {
  "name": "agent-context-system",
  "version": "1.0.0",
  "description": "A skill for persistent local-only memory for AI coding agents. Two files, one idea: AGENTS.md (committed, shared) + .agents.local.md (gitignored, personal).",
  "files": [
    "SKILL.md",
    "agent-context",
    "AGENTS.md",
    "openclaw/**/*",
    "github-copilot/**/*",
    "scripts/**/*",
    "agent_docs/**/*",
    "LICENSE",
    "README.md"
  ],
  "repository": {
    "type": "git",
    "url": "git+https://github.com/AndreaGriffiths11/agent-context-system.git"
  },
  "author": "AndreaGriffiths11",
  "license": "MIT"
}


path: scripts/agents-local-template.md
content: # .agents.local.md — Local Agent Scratchpad

> Gitignored. Never committed. Persistent memory across agent sessions.

## Preferences

- **Style:** [e.g., Friendly, technical, peer-to-peer. No corporate jargon.]
- **Code:** [e.g., Minimal changes. No speculative refactors.]
- **Planning:** [e.g., Always state the plan before writing code.]

## Patterns

<!-- Settled truths about this project. Promote recurring session learnings here. -->

## Gotchas

<!-- Things that look right but aren't. Include WHY. -->

## Dead Ends

<!-- Approaches tried and failed. Include WHY they failed. -->

## Ready to Promote

<!-- The agent flags items here during compression when a pattern has recurred across 3+ sessions.
     The human decides when to move them into AGENTS.md's Project Knowledge section.
     Use the same pipe-delimited format AGENTS.md expects:
       pattern | where-to-see-it    → goes in Patterns
       rule | reason                → goes in Boundaries
       trap | fix                   → goes in Gotchas
-->

## Session Log

<!-- Append new entries at the END. One entry per session. Keep each to 5-10 lines. -->

### YYYY-MM-DD — Topic

- **Done:** (what changed)
- **Worked:** (reuse this)
- **Didn't work:** (avoid this)
- **Decided:** (choices and reasoning)
- **Learned:** (new patterns or gotchas)

---

## Compression Log

<!-- When this file exceeds 300 lines, compress. Log it here. -->


path: scripts/init-agent-context.sh
content: #!/bin/bash
# init-agent-context.sh
# Wrapper for backwards compatibility with npx skills install.
# All logic lives in the main CLI at ../agent-context

set -euo pipefail

SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
exec "$SCRIPT_DIR/../agent-context" init "$@"


path: scripts/publish-template.sh
content: #!/bin/bash
# publish-template.sh
# Push to GitHub and mark as a template repo. Run once.

set -euo pipefail

REPO_NAME="agent-context-system"

echo "This will create a private GitHub repo and mark it as a template."
echo ""
read -rp "GitHub username: " GH_USER
if [[ -z "$GH_USER" ]]; then
    echo "Error: Username cannot be empty."
    exit 1
fi
if [[ ! "$GH_USER" =~ ^[a-zA-Z0-9]([a-zA-Z0-9-]*[a-zA-Z0-9])?$ ]]; then
    echo "Error: Invalid GitHub username format."
    exit 1
fi
echo ""

[ ! -d ".git" ] && git init
sensitive_files=$(find . -maxdepth 2 \( -name ".env*" -o -name "*.pem" -o -name "*.key" -o -name "*.secret" -o -name "id_rsa*" \) 2>/dev/null || true)
if [ -n "$sensitive_files" ]; then
    echo "⚠️  Potentially sensitive files detected:"
    echo "$sensitive_files"
    echo ""
    read -rp "Continue anyway? (y/N) " confirm
    [[ "$confirm" =~ ^[Yy]$ ]] || exit 1
fi
git add -A
git commit -m "Initial commit: agent context system template" 2>/dev/null || true

gh repo create "$GH_USER/$REPO_NAME" \
    --private \
    --source=. \
    --remote=origin \
    --description "Template: persistent local-only memory for AI coding agents" \
    --push

gh api \
    --method PATCH \
    -H "Accept: application/vnd.github+json" \
    "/repos/$GH_USER/$REPO_NAME" \
    -f is_template=true

echo ""
echo "Done: https://github.com/$GH_USER/$REPO_NAME"
echo ""
echo "Create a new project from this template:"
echo "  gh repo create my-project --template $GH_USER/$REPO_NAME --private"
echo "  cd my-project && ./scripts/init-agent-context.sh"


Security scan verdicts — ClawScan: suspicious | static analysis:  | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)