write-scroll
Write markdown content for in-game scrolls in the Head over Heels remake, matching the tone and conventions of the existing manual files
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Write markdown content for in-game scrolls in the Head over Heels remake, matching the tone and conventions of the existing manual files
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Take a set of local feature branches/worktrees all the way to merged PRs — discover unmerged work, fix commit-time hygiene, push, raise PRs, watch CI, auto-fix mechanical failures, merge on green, and cascade-rebase the rest. Use when the user says "shepherd PRs" or wants several branches driven to merge autonomously.
Read BEFORE invoking `playwright test` in any form, for any reason — running e2e, visual regression, room snapshots, or verifying a change 'via e2e'. Covers required project scoping (chromium-desktop, matching CI), the sandbox browser-build bridge, and the pnpm webServer failure. Also load on these failure signatures: every test failing at browserType.launch, 'Executable doesn't exist at /opt/pw-browsers/...', or 'Process from config.webServer was not able to start'.
Run the true-site-size GitHub Action locally via `act` inside the Claude Code web sandbox, to measure the game/editor cold-load journey byte cost without a CI round-trip. Use when asked to measure or verify build/wire size, or to check a byte-saving change, in the sandbox.
Fetch a campaign from the Supabase DB and save as local JSON. Use when the user asks to load, download, or fetch a campaign from the database.
Drive the Head over Heels remake's UI via the chrome-devtools MCP. Use this skill when the user asks for browser automation, capturing localStorage, dispatching game actions, or anything that involves driving the running game on localhost.
Run Docker — and tools that need it, like `act` (local GitHub Actions) — inside the Claude Code web sandbox, where image pulls and in-container networking collide with the egress proxy. Use when `docker pull` returns 403 on image layers, when a container can't reach the network, or when running `act`/CI-in-docker locally (e.g. the `act-true-site-size.sh` script).
| name | write-scroll |
| description | Write markdown content for in-game scrolls in the Head over Heels remake, matching the tone and conventions of the existing manual files |
| argument-hint | ["description of what the scroll should say"] |
Write markdown content for an in-game scroll. The user will describe what the scroll should convey; your job is to write it in the correct style.
The writing style is dry, matter-of-fact British English with understated humour. Absurd details are delivered deadpan as though perfectly reasonable. Sentences are short and punchy. Paragraphs are brief (1-3 sentences typically).
Read the existing manual files in src/manual/ for reference, especially:
src/manual/historyOfTheBlacktoothEmpire.md - world-building tonesrc/manual/theGame.md - mission briefing tonesrc/manual/theEmperorsGuardian.md - in-world character voicesrc/manual/teleportBack.md - example of an in-world note from a charactersrc/manual/returnOfTheEmpire.md - sequel storylineUse curly/smart apostrophes (\u2019) not straight ones, matching the existing manual files.
Scrolls can optionally include sprite images using this syntax:
Text starts here on the same line
Text with image floated right
Multiple classes separated by &
With background colour
Common texture names: texture-crown_blacktooth, texture-crown_bookworld, texture-crown_egyptus, texture-crown_penitentiary, texture-crown_safari, texture-teleporter, texture-head_walking_right_2, texture-heels_standing_towards, texture-animated-dalek, texture-cyberman_towards, texture-blacktooth_wall_armour_left, texture-blacktooth_wall_shield_away, texture-bag, texture-hooter, texture-doughnuts, texture-animated-helicopterBug, texture-hushPuppy, texture-spring_released, texture-fish_1.
Only include images if they are relevant and the scroll is long enough to warrant them. Short notes (like teleportBack.md) may have one or none.
Write the scroll content as markdown. After the user approves the content, suggest they use /md-to-json-string to convert it for embedding in room JSON.