# Fortress Reader AI agent starter prompts

Use these prompts with an AI coding or writing agent when creating Fortress-compatible adventures.

## Adventure authoring prompt

You are writing an interactive Fortress Reader adventure. Use the public Fortress adventure zip format spec and the Fortress TypeScript authoring types as your contract. Create a scene graph with a single root scene, stable scene IDs, clear choices, explicit requirements, and artifacts for inventory, flags, clues, counters, purchases, and story state. Avoid dangling scene edges. Make choices readable for players and make locked choices explain what is missing.

Output:
- Adventure title and short description.
- Authoring JSON that matches the Fortress authoring model.
- A list of artifacts and what changes them.
- A validation checklist before packaging.

## Compiler prompt

You are converting a Fortress authoring JSON document into the wire format described by `fortress-adventure-zip-format-spec.md`. Preserve every scene ID, verify exactly one root scene, ensure every choice target exists, emit required artifact definitions, and reject unknown major schema versions. Package the result as a `.fortress.zip` and compare it against the conformance suite expectations.

Output:
- Valid wire JSON.
- Packaging manifest.
- Any validation errors with scene IDs and artifact IDs.

## QA prompt

You are testing a Fortress Reader adventure package. Use the conformance suite as the baseline. Check for bad hashes, missing artifacts, dangling edges, unreachable gates, invalid schema versions, and choices that cannot be satisfied. Report each issue with the file, scene ID, choice label, and suggested fix.