forge-setup-project
Installation
SKILL.md
Set Up or Update Project Context Infrastructure
Context is organized in three tiers:
| Tier | File(s) | Role |
|---|---|---|
| 1 — Hot memory | AGENTS.md | Always loaded. Lean, convention-dense. Only what agents need constantly. |
| 2 — Warm memory | docs/*.md | Loaded on-demand by topic. Created only when content earns its token cost. |
| 3 — Cold memory | Specs, schemas, runbooks | On-demand references for complex projects. Not created by this skill. |
Central principle: context must earn its token cost. Only include knowledge that agents cannot discover by exploring the codebase with Grep, Glob, and Read.
AGENTS.md is the only guidance file. Don't create a CLAUDE.md: Claude Code reads AGENTS.md natively when no CLAUDE.md or CLAUDE.local.md is present, so a symlink or copy only adds a second name. A CLAUDE.md is justified only for Claude-specific content the user wants kept — then it is @AGENTS.md followed by that content, never a copy.
Input
Optional project root path ($ARGUMENTS; defaults to cwd). Optional: -- <additional context> for execution guidance.