Frame

Frame

Spec-driven development that becomes durable, structural context built on Claude Code and Codex.

The shape of software development changed, agents write the code now, but the foundation didn't: good results still come from good planning. Frame puts planning back at the center. You write a spec once, and that single spec becomes two things at once: the plan your agents follow, and the durable, shared context your project keeps across every session. Every future agent arrives knowing what was done and why no more re-explaining your architecture every time you open a terminal.

Built on Claude Code. Codex CLI work too, and because your context lives in plain, git-versioned files, it stays yours and stays readable by any tool.

---

The Problem

As projects grow with AI agents, things fall apart fast:

• Context loss — every new session starts from scratch, you re-explain the same things over and over
• No project memory — AI doesn't know your architecture, past decisions, or pending tasks
• No standard — every developer structures their AI projects differently, making collaboration and onboarding painful
• Sessions bleed into each other — working on multiple projects means context gets mixed up
• Terminal chaos — multiple windows, scattered sessions, no organization
• Tool fragmentation — Claude, Codex, and Gemini each work differently

These problems are manageable on small projects. On larger ones, they become blockers.

Frame solves all of this.

---

How Frame Works

One Standard, Every Project, Every AI Tool

Frame brings a consistent structure to every project you work on. When you initialize Frame in a project, it creates:

File	Purpose
.frame/AGENTS.md	Project rules and instructions — AI reads this automatically
.frame/STRUCTURE.json	Module map with intentIndex for fast file lookup
.frame/PROJECT_NOTES.md	Architectural decisions and context that persist across sessions
.frame/tasks.json	Task tracking with status, context, and acceptance criteria
.claude/rules/frame.md	Two lines pointing Claude Code at .frame/AGENTS.md

Everything Frame writes lives under .frame/, plus that one pointer file. Your project root stays yours: an existing CLAUDE.md, AGENTS.md or .cursorrules is never read, moved or replaced, and "Remove Frame" leaves no Frame-authored bytes behind. Needs Claude Code new enough to load .claude/rules/ — verified with Claude Code 2.1.x; run /context in a session to confirm .claude/rules/frame.md loaded.

Upgrading: update Frame before pulling a repository that has been migrated to .frame/. An older Frame looks for the meta files at the project root, finds none, and reports the project as empty — and its spec phases as unstarted.

Every project gets its own isolated session — its own context, its own task list, its own notes. Switching projects in Frame means switching to a completely fresh, project-specific AI context. No bleed-over, no confusion.

This standard works with any AI tool. Claude Code loads .claude/rules/frame.md natively at session start, which imports .frame/AGENTS.md — no launch flags, no wrapper. For Codex CLI, Frame injects the same file via a wrapper script.