What this is
A flat staging directory (`project_cache\`) plus a manifest tracker that keeps Claude's Project Files current. Registered files get copied to the cache on one command; the user opens the folder, selects all, and drags to Project Files. It closes the gap between "the right files exist somewhere" and "the right files are loaded into every conversation."
install project-cache
The sections below are the install payload — the directives Claude reads and runs when this feature is installed. Shown here for transparency; a person browsing only needs "What this is" above.
Assess first
- Check whether `project_cache\` exists at the project root -- create it if missing (flat, no subdirectories). - Check whether the manifest exists at `trackers\data\[ProjectCode]_Project_Cache.md`. - Locate the auto-registerable files so you can register what exists and mark the rest "Not Yet Found": - `[ProjectCode]_Logo.png` in `brand\` - `Brand_Standards.md` in `brand\` - `[Entity]_Profile_Sanitized.md` in `admin\` - `AGENT_INSTRUCTIONS.md` in `admin\` - `tracker_index.md` in `trackers\` - Confirm a copy mechanism is available (Windows MCP `Copy-Item` preferred, Filesystem MCP fallback).
Ask, only if needed
- After auto-registering, offer: "I've set up the project cache with [N] auto-registered files. Want to run the first refresh now?" If yes, run it immediately. - Otherwise nothing to ask -- the auto-registration list requires no input.
Write (payload written into admin\AGENT_INSTRUCTIONS.md)
Create `project_cache\` at the project root. Create the manifest at `trackers\data\[ProjectCode]_Project_Cache.md` using the template below, auto-registering all applicable files. Update `trackers\README.md` to include the cache manifest entry. Then add this section to `admin\AGENT_INSTRUCTIONS.md`:
```
* PROJECT CACHE
Cache Directory: [project_root]\project_cache\ (flat -- no subdirectories)
Manifest: trackers\data\[ProjectCode]_Project_Cache.md
The Project Cache is a flat staging directory. Registered files are copied
here on refresh. Open the folder, select all, drag to Claude Project Files.
PURPOSE: Claude's Project Files hold the closest-in-context reference
material. The cache keeps them current without manual file hunting.
AUTO-REGISTERED FILES
[ProjectCode]_Logo.png <- brand\ (Critical)
Brand_Standards.md <- brand\ (High)
[Entity]_Profile_Sanitized <- admin\ (High)
AGENT_INSTRUCTIONS.md <- admin\ (High)
tracker_index.md <- trackers\ (Medium)
If a file isn't found at setup, register it as "Not Yet Found" and pick it
up automatically at first refresh once it exists.
COMMANDS
"refresh project cache" / "update project cache"
-> copies all registered files to project_cache\
"add [file] to project cache"
-> permanently registers; included in all future refreshes
"show project cache" -> lists registered files and current status
"scan for cache candidates" -> recursive scan for unregistered cacheable
files
REFRESH BEHAVIOR -- HARD RULES
1. Read the manifest
2. For each registered file: locate at its source path; copy if not yet
in cache; copy only if source is newer (skip if identical); if source
not found, mark Not Found and CONTINUE (do not abort the run)
3. Update the manifest with new statuses and timestamps
4. Report: N copied · N skipped · N not found
5. No manual intervention once started -- the run goes to completion
COPY RULE -- HARD
Copy only. Never move. Never modify source files. Newer source overwrites
the cached version; identical version is skipped. Mechanism: Windows MCP
Copy-Item (K:\ path) preferred, Filesystem MCP fallback. If neither can
write to project_cache\: present the file list for manual copy and flag
as a Bootstrap Reconciliation Item.
RECURSIVE SCAN ("scan for cache candidates")
Walk the project tree; flag files matching, not already in the manifest:
*.png in brand\ · *Brand_Standards* · *_Profile*.md in admin\ ·
AGENT_INSTRUCTIONS.md anywhere · tracker_index.md anywhere · any .md in
docs\reference\ · any .html in trackers\templates\. Present candidates;
user confirms -> permanently registered.
DIRECTORY CONSTRAINTS -- HARD
Flat -- no subdirectories; all files at root level only. Staging only --
never a source for edits, drafts, or production. Files here are copies;
the source of truth is always the registered source path.
User workflow: refresh -> open project_cache\ -> select all -> drag to
Claude Project Files.
MANIFEST TRACKING
Two-layer tracker. Data file in trackers\data\. Static filename; version
inside the file. Records filename, source path, type, priority, last
copied, status. Status values: Current / Updated / Not Found / Not Yet
Copied.
WHEN USER ASKS ABOUT PROJECT FILES
"Claude's Project Files are the closest-in-context storage in every
conversation. The Project Cache makes sure they stay current. Refresh
when files change -- open project_cache\, select all, drag to Project
Files. That's the full workflow."
```
Manifest template (`trackers\data\[ProjectCode]_Project_Cache.md`):
```
Project Code: [ProjectCode]
Cache Dir: [root]\project_cache\
Last Refresh: [datetime]
Version: [X.X]
| # | File Name | Source Path | Type | Priority | Last Copied | Status |
|---|-------------------------------|-------------|---------|----------|-------------|------------|
| 1 | [ProjectCode]_Logo.png | brand\ | Logo | Critical | [date] | Current |
| 2 | Brand_Standards.md | brand\ | Brand | High | [date] | Current |
| 3 | [Entity]_Profile_Sanitized.md | admin\ | Profile | High | [date] | Updated |
| 4 | AGENT_INSTRUCTIONS.md | admin\ | Config | High | [date] | Current |
| 5 | tracker_index.md | trackers\ | Index | Medium | [date] | Not Yet |
```Confirm
Confirm: your Project Cache is set up with [N] auto-registered files -- say "refresh project cache" anytime to stage your key files for Project Files. Want to run the first refresh now, install another, or is that everything for now?