load-project-cache-first

Loads project documentation cache and memory files before source code exploration.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ndestates/ndestates-website --skill load-project-cache-first-ndestates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: load-project-cache-first
Source: https://github.com/ndestates/ndestates-website/tree/main/.copilot/skills/load-project-cache-first
Command: npx skills add https://github.com/ndestates/ndestates-website --skill load-project-cache-first-ndestates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new AI-assisted session on a large codebase wastes tokens and time when the assistant immediately greps and reads hundreds of source files. This Skill enforces a cache-first workflow so the assistant loads curated project documentation, TODO lists, and memory indexes before touching application source code. ## Core Features & Use Cases - Cache-First Session Start: Loads a fixed spine of files (codebase index, freshness scan, latest TODO, memory index) before any semantic search or grep. - Token Budget Enforcement: Honors a configurable cap on additional cache files via token_policy.max_cache_files_default in the project manifest. - Grep-Before-Read Discipline: Requires grepping headings of large cache files and reading only targeted sections instead of full files. - Use Case: A developer returning to the ndestates-io Laravel/Filament project starts a session; the assistant loads ARCHITECTURE.md and CONCERNS.md, confirms context, and only reads source files after the user confirms direction. ## Quick Start Ask the assistant to load the project cache first and summarize the current architecture and open concerns before making any code changes.

Frequently Asked Questions about load-project-cache-first

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

FAQPage Schema
How do I reduce token usage when starting an AI coding session?▼

Load a curated documentation cache first instead of searching source code. This Skill reads a fixed spine of index, TODO, and memory files, then caps additional cache reads via a token policy in the project manifest.

How to give an AI assistant project context without reading the whole codebase?▼

Maintain structured docs like ARCHITECTURE.md, STACK.md, and CONCERNS.md under docs/codebase/, plus a memory index. The assistant loads only the files relevant to the task, grepping large files before reading sections.

What files does the cache loader read at session start?▼

It always reads the codebase README index, a freshness scan file, the latest TODO document, and the memory index. Up to two additional topic files such as ARCHITECTURE.md or CONCERNS.md are loaded based on the task.

Can I customize which cache files get loaded for a task?▼

Yes, pass an optional argument naming a topic or file, such as CONCERNS, architecture, or valuations. The loader picks matching files from docs/codebase/ while respecting the configured maximum cache file count.

What happens if the project cache is stale or outdated?▼

The loader checks a freshness scan file and notes suspected staleness to the user. It asks before performing a full re-scan rather than silently reading the entire source tree.