init-context-files

Creates a structured context directory with AGENTS.md files for agent project onboarding.

Updated May 13, 2026
One-click install
npx skills add https://github.com/andrewcodesit/skills --skill init-context-files-andrewcodesit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init-context-files
Source: https://github.com/andrewcodesit/skills/tree/main/skills/context/init-context-files
Command: npx skills add https://github.com/andrewcodesit/skills --skill init-context-files-andrewcodesit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents start every session with zero knowledge of a project, forcing them to re-derive the codebase from scratch each time. This Skill builds a persistent context/ directory and AGENTS.md hierarchy so agents load only the slice of project knowledge a task needs. ## Core Features & Use Cases - Project Scanning and Classification: Reads manifests, READMEs, and config files to classify the project type (SPA, API, monorepo, serverless, CLI) before writing anything. - PROSE-Based Tree Design: Applies five architectural constraints (Progressive Disclosure, Reduced Scope, Orchestrated Composition, Safety Boundaries, Explicit Hierarchy) to keep every context file under ~8KB and scoped to one task type. - Context Map and Approval Gates: Wires a root AGENTS.md with a Context Map routing task types to the right files, plus explicit approval gates for risky operations like migrations and deploys. - Use Case: After inheriting an unfamiliar monorepo, run this Skill to generate context/project-overview.md, context/code-standards.md, an architecture decision log, and nested AGENTS.md files so any future agent session onboards in minutes. ## Quick Start Ask the agent to set up context files for this project so future sessions understand the codebase.

Frequently Asked Questions about init-context-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create context files for AI agents in my project?▼

Run the init-context-files flow: it scans your manifests, README, and configs, classifies the project type, then writes a context/ directory with project overview, code standards, and optional architecture, design, and domain files, plus a root AGENTS.md Context Map.

What is the PROSE framework for agent context files?▼

PROSE defines five constraints: Progressive Disclosure, Reduced Scope, Orchestrated Composition, Safety Boundaries, and Explicit Hierarchy. Applied to context files, it means no leaf file over ~8KB, one file per task type, linked small files, explicit approval gates, and nested AGENTS.md per subtree.

Should I use CLAUDE.md or AGENTS.md for project instructions?▼

Put the Context Map and instructions in AGENTS.md, and make CLAUDE.md a thin pointer that redirects to AGENTS.md. CLAUDE.md must never duplicate the Context Map; it exists only so Claude Code finds the canonical instructions.

How large should agent context files be?▼

Keep each leaf file under roughly 8KB, because context files are re-read on every turn of a session. Any topic projected to exceed that budget should become a directory with a thin index.md and linked leaf files split by task type.

When should I split a context file into a directory?▼

Split when the estimated content exceeds ~8KB or when a single Context Map row would point at multiple files. Create an index.md with the shared map plus one leaf per subsystem, so a task loads only the slice it needs.