BUILD WITH AI · LOCAL TOOLS, YOUR GAME

Your game.
A new way to play.

Give your local coding agent a starting point for an Archipelago integration. The Peliarch toolkit brings the skill, shared client and bridge together. You bring the game and the idea.

Get the toolkit Copy the starter prompt

Pinned release · October 15, 2026 · Source toolkit

THE STARTING MATERIALS

A toolkit to build on.

Download the whole bundle so the skill and its code stay together. These references all point to the same release.

01 / THE COMPLETE BUNDLEPeliarch toolkit Release notes and the pinned source archive, with the SDK, templates and tools.Open the release 02 / YOUR AGENT’S GUIDEAgentic APWorld skill A workflow for researching the game, designing its world, implementing hooks and checking the result.Read the skill 03 / THE SHARED CLIENTUniversal client SDK Build a companion around the existing protocol runner, durable storage and Windows GUI.Explore the client workflow 04 / THE LOCAL CONNECTIONFile bridge guide Connect a game mod to the shared client using a versioned local transport based on Baconspaceman’s Universal Archipelago SDK.Read the bridge guide

FROM AN IDEA TO A WORKING CONNECTION

Start local. Build something playable.

Your agent’s tools run on the computer where the game is installed. The AI model may still use an online service; this page does not run code on your computer.

01 / UNPACK

Open the toolkit with your agent

Extract the bundle into a development folder. Use a local coding agent that can read files, inspect your installed game and run build tools. Ask it to read the bundled skill first.

02 / MAKE IT YOURS

Describe the run you want

Edit the prompt below with your game, version and install path. Explain what should count as a check, which rewards should arrive, and what finishes the run. Your agent researches the available hooks.

03 / BUILD & VERIFY

Connect the full loop

The agent builds the world and companion, then tests checks, item delivery, native effects and completion through the actual client and server wherever feasible. Expand from a working slice toward your intended scope.

YOUR FIRST MESSAGE

Give your agent a clear start.

Edit the bracketed details, then copy the prompt into your local coding agent with the extracted toolkit open.

Build an Archipelago integration for my game using this Peliarch toolkit.

Game: [name]
Platform and exact game/port version: [platform, version]
Installed game folder: [local path]
Checks: [events or discoveries that should send items]
Rewards: [items, abilities or changes the game should receive]
Goal and intended scope: [what finishes the run; what I want supported]

Read .agents/skills/agentic-apworld/SKILL.md and docs/agents/BUILD-AN-INTEGRATION.md in the extracted toolkit first. Follow the repository instructions and preserve unrelated work.

Inspect the actual game and any existing integration before choosing a route. Reuse an existing APWorld’s contract when applicable. Research shipped APIs and mod interfaces; verify native hooks instead of guessing them. Record the supported game build and unresolved questions.

Implement the APWorld and game-specific companion using the existing shared client SDK, runner, storage and GUI. Use the file bridge where it fits, or preserve an existing working transport. The bridge still needs real game hooks and effects.

Automate the full production path wherever feasible: game event → bridge/client → AP check → received item → native effect, plus progression and goal completion. Check duplicates, reconnect and save/restart persistence. State exactly which boundaries each test proves; synthetic callbacks alone do not prove normal gameplay. Do not interrupt an active game. Trust my choice of save without adding repeated confirmations or save-isolation chores.

Carry the work through implementation and appropriate verification. A working slice is a milestone toward the requested scope. Package the world and companion with pinned component versions and clear setup instructions, including required development tools. Include original integration code and permitted dependencies only; exclude game assets. Report usable artifact paths, tested scope and remaining gaps. Keep publication as a separate decision.