slaguru666andClaude Sonnet 4.6
3fbf9892f9
- projects/general.md — catch-all engineering context - projects/foundry-dev.md — FoundryVTT/zero-engine development - projects/infrastructure.md — VPS, Docker, CI/CD - projects/rpg-creative.md — SLA Industries, Stormbringer, convention work - projects/README.md — setup guide and sync workflow Each file includes Graphiti session-start instruction so web conversations have access to live memory from Claude Code sessions. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
Claude.ai Projects — Setup Guide
These files are the custom instructions for claude.ai Projects. Each Project gives the web/browser surface the same context that Claude Code gets from CLAUDE.md and memory files.
Projects to create
| File | Project name | Use for |
|---|---|---|
general.md |
General Engineering | Catch-all: scripting, tooling, anything that doesn't fit another project |
foundry-dev.md |
FoundryVTT Dev | zero-engine, modules, Foundry system/module work |
infrastructure.md |
Infrastructure | VPS, Docker, Gitea, CI/CD, server work |
rpg-creative.md |
RPG & Creative | SLA Industries writing, Stormbringer, convention prep |
How to set up a Project
- Go to claude.ai → Projects → New Project
- Name it (use the names in the table above for consistency)
- Open Project Instructions and paste the contents of the relevant
.mdfile - Save
Keeping Projects in sync
When CLAUDE.md or domain knowledge changes:
- Update the relevant file in
projects/ - Run
./sync.shto commit and push - Manually paste the updated file into the Project's instructions on claude.ai
There's no API to push instructions automatically — this step stays manual.
Why Graphiti matters here
Each instruction file starts with a Graphiti session-start call. Graphiti MCP is already connected to claude.ai, so every Project conversation has access to live memory — facts, decisions, project state — that Graphiti learned from Claude Code sessions. This is what makes the web surface dynamic rather than just static context.