Help me keep one real project usable across AI assistants, using the attached Matty Builds It guide and starter as a reference.

Project: [name and one-sentence purpose]
Assistants I use: [for example, Claude Code and Codex]
Existing working folder or files: [path, or attach the relevant files]
Large-media location, if any: [path/service, or none]
Review device: [computer/phone]

If I leave something blank, inspect the supplied materials first and ask only for information you cannot establish. The guide describes one person's setup; adapt it to my project rather than copying every repo or tool.

FIRST, INSPECT AND PROPOSE

1. Read the supplied guide.md, starter README, existing AGENTS.md/CLAUDE.md, current state and relevant working files. Treat example values as examples, not facts. Check which file, shell and service tools you actually have. If you can only chat, give me a proposed structure and steps instead of claiming you changed anything.
2. Describe the problem this setup solves for my project and who uses it. Inventory the existing files and any uncommitted work. Preserve existing source, rules and plans. Identify one authoritative home for each kind of record so we do not create competing calendars or drafts.
3. Propose the smallest useful structure. One repo with plans/, projects/, evidence/, media/ and selected shared instructions may be enough. Keep large originals/exports in a separate media home, referenced by stable IDs, relative paths and real file hashes. Keep machine-specific paths in ignored .local/paths.json. Never fill in a pretend hash or claim a file is backed up just because it has an index entry.
4. Explain how source will sync, how media is reached or copied separately, and where review versions will live. Check current branch/changes before any Git operation. Git does not transfer browser sessions, credentials or large media. Identify the access each machine or assistant still needs. Show me the plan before changing files unless I have already approved that exact scope.

THEN, IMPLEMENT THE APPROVED SCOPE

5. Add or adapt the agreed files without replacing my working content or weakening existing instructions. Merge shared operating rules with a clear entry point for each assistant. Record actual state, decisions, source locations and the next action. Rename or omit example files so they cannot be mistaken for real records.
6. Add only skills relevant to this project. Verify their source, license, pinned version and supported discovery path for each assistant. Record actual installed skills separately from proposed ones. Shared instructions do not grant tool access. Jev is optional and is not required to use this structure. Do not make paid calls, create service accounts, publish, alter hosting/access or install external tools without my applicable authorization.
7. If phone review is in scope, explain the hosting choice and its online/access requirements. Serve only a selected export directory, not my repo or media library. Verify the chosen device can load the page, play the video and download the expected files before claiming it works there. Keep reviewed versions identifiable.
8. Inspect tracked/staged files for credentials, private data and media before committing. Preserve concurrent changes, reconcile conflicts and never force-push. Follow the approved sync workflow; do not create a public repo or remote as a shortcut.

VERIFY AND HAND OVER

9. Check that the working plan points to real source, any indexed media exists and matches its hash, and local bindings/secrets are excluded from Git. Make sure existing work survived and no second authoritative plan was created. Report checks run and missing access honestly.
10. Write a short start-here instruction for a fresh session: the exact files to read, one small next task and how to verify it. Have the next assistant complete that task from the saved files. If you cannot run that separate session yourself, give me the test and mark cross-assistant continuation unverified. Do not claim universal memory or automatic synchronization.

Start with inspection and the proposed plan.
