# Develop an existing checkout with ChatGPT You can study or change this game with the downloaded VCC Plus app, a local checkout and a supported ChatGPT connection. The setup below uses the public app, project files and installed documentation. ## Prepare the project 1. Download or clone the complete [public repository](https://vccplus-git.brianholman.com/VCCPlusApps/Quadrapassel) into your own writable folder. Keep the folder structure, Makefile and `vccplus-project.json` together. 2. Open the installed [VCC Plus for Mac](https://vccplus.brianholman.com/downloads/). Its bundled toolchain supplies the game's build tools; Homebrew is not needed. 3. In **Develop → C Development…**, open the existing game project and select **Release**. Read `docs/VCC_PLUS_WORKFLOW.md` before building or launching. 4. To work with ChatGPT, open the C workspace's **Assistant…** panel. Review the shared inputs and enable **Use Project Makefile** for this project's recipe. Enable **Allow Disposable Playtests** if you want isolated game tests. 5. Save the connection privately and connect it using the installed manual's supported process. Keep the app and shared workspace open. Confirm a real project request succeeds before asking the assistant to edit/build anything. The [MCP setup guide](docs/MCP_SETUP.md) distinguishes game-project access, installed manuals and the separately shared Archive Library. Grant only the scopes you intend to use. Never paste connection tokens or private grants into this repository or a conversation. ## A starting prompt Adapt this prompt to the change you want. Your working folder is your own clone; no machine-specific path or model selection is required. ```text Work on the Quadrapassel for CoCo checkout I have opened in VCC Plus. First verify the repository, branch and existing changes, then read README.md, AGENTS.md, SPECIFICATION.md and docs/VCC_PLUS_WORKFLOW.md. Use the independently written CoCo source and its behavioral specification. Do not consult or import the Linux/Mac application's implementation or emulator internals. Prefer documented standard CMOC APIs and preserve the existing narrow C graphics exception and memory bounds. Discover the connected C project's actual capabilities and verify that it matches this checkout, its current revision and the Release configuration. Verify manual access separately; use Archive Library's own connection when a historical reference is needed. Ask for a missing scope instead of inventing a private endpoint or using another project's connection. Implement this change: [describe the desired behavior here]. Preserve unrelated edits, personal disks, high scores and the normal guest session. Use disposable test media. Build the declared Release disk, inspect its diagnostics/memory check, and test the changed behavior with ordinary guest input and real screenshots. Identify what passed and anything not observed. Do not change guest memory/registers to manufacture a test result. Stop owned tests and retain their disk receipts when finished. Commit or publish only if I have requested it. ``` ## Read next - [Player's manual](https://vccplus.brianholman.com/games/quadrapassel/): the delivered game's screens, controls, scoring, settings and disk records. - [Behavioral specification](SPECIFICATION.md): implementation rules and fixtures. - [Build workflow](docs/VCC_PLUS_WORKFLOW.md): the existing C project, Release build, disk products and safe launch. - [MCP setup](docs/MCP_SETUP.md): live discovery and scoped connection checks. - [Provenance](docs/PROVENANCE.md): behavioral lineage and component notices. Dated investigation logs are historical evidence. They are not prerequisites for using the current public game, toolchain or connection workflow.