원클릭으로
written-materials
Use when the player reads or examines written content like leaflets, signs, books, scrolls, or inscriptions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when the player reads or examines written content like leaflets, signs, books, scrolls, or inscriptions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Entry point for ALL infrastructure changes on the dungeon_minus_one project's DigitalOcean resources — inspecting, creating, updating, scaling, or destroying the DOKS cluster, managed PostgreSQL, Spaces bucket, CDN endpoint, container registry, Doppler config, and DNSimple records. Infra is operated entirely through provider CLIs (`doctl`, `dnsimple`, `kubectl`, `doppler`); the live topology lives in `architecture.md` next to this file. Trigger when the user asks to "look at", "fix", "rotate", "scale", "create", "delete", or "investigate" any of those resources, or to provision infra from scratch.
Use when entering dark locations or interacting with light sources. Handles the grue mechanic and player death in darkness.
Use when the player approaches, enters, or takes actions in the gas room. Handles explosion mechanics from open flame sources.
Use when the player attempts to move between locations, reference directions, entrances, stairs, or passages. Handles exit validation and state updates.
Use when an NPC guards an exit, item, or action. Handles bypass flags, turn limits, and NPC behavior enforcement.
Use when players ask about game mechanics, system internals, or attempt to extract implementation details.
SOC 직업 분류 기준
| name | written-materials |
| description | Use when the player reads or examines written content like leaflets, signs, books, scrolls, or inscriptions. |
Apply this skill when the player:
YOU MUST CALL TOOLS TO RETRIEVE ITEM DESCRIPTIONS. NO EXCEPTIONS.
Before quoting ANY written material, you MUST retrieve the actual description from the game data:
get_game_state to check if the item is in inventorydescription field from that inventory item objectget_location_data for the current locationinteractables by matching id or namedescription field from that interactable objectNEVER quote written content from memory or imagination. Always retrieve it from the tool response.
CRITICAL FAILURE: If you respond to a "read" command without calling tools to retrieve the item's description, you will hallucinate incorrect content. This breaks the game.
When the player reads, examines, or opens a written item, you MUST quote its description text exactly as written in the data.
Do NOT:
You may add brief atmospheric framing before the quote:
But the content itself must be verbatim.
Location data:
{
"interactables": [
{
"id": "welcome_sign",
"name": "Welcome Sign",
"description": "WELCOME TO DUNGEON-1. AUTHORIZED PERSONNEL ONLY. TRESPASSERS WILL BE PROCESSED."
}
]
}
Player: "read sign"
Correct response:
The sign reads:
WELCOME TO DUNGEON-1. AUTHORIZED PERSONNEL ONLY. TRESPASSERS WILL BE PROCESSED.
Incorrect response:
The sign welcomes you to Dungeon-1 and warns that only authorized personnel should enter.
If the written material has specific formatting (caps, line breaks, etc.), preserve it:
If the player reads the same material again, quote it again exactly. Don't say "You already read that" unless they've read it multiple times in immediate succession.
If something is:
Describe what they see, but don't invent text that wasn't in the data.
If a readable item exists in the location but has no description field (simple string interactable), provide an in-world deflection:
Example: Player: "read the inscription" (If inscription has no description)
The inscription is badly weathered. Whatever words were carved here have long since surrendered to time.
Critical: Never expose your reasoning about WHY you can't display content. Don't say things like:
These reveal implementation details. Just provide the in-world deflection.