penguin-harness: Skill for Claude Code

Writing for penguin.ooo

Posts, docs pages and landing copy are written by a model on the TokenDance gateway and shipped by agents. A post is written the way a person writes one: an outline first, then the whole post in one call, so its sections join; the review, the fixes, the cuts and the translation work on the whole post too, and a round of its own edits only the sentences at the headings. A long post or a docs page can fall back to section mode. This page is the contract; scripts/prose.mjs is the only way text reaches a draft, and prompts/ plus reference/ hold every word sent to the model. penguin-harness-dev/reference/authoring.md covers what is true of every post (the bilingual pair, frontmatter, where screenshots live).

1. Who writes what

The API model writes every word a reader sees: the outline and its plan, every section, the title and excerpt, every string inside a figure, alt text and captions, the second language, every docs sentence and landing string, and every later fix or cut. Each is its own API call through prose.mjs.

Agents never type a sentence into the text. They research, compile FACTS, write prompts and findings, put the model's text together, draw figures from the model's figure blocks, take screenshots, run the checks, review blind and ship. Putting the text into the manuscript is also the agent's job, and it is mechanical: write saves the draft, assemble joins section files in section mode, and strip publishes them. A wrong sentence goes back through a fix call with a numbered finding, never through an editor. The only hand edits are mechanical: frontmatter date / category, screenshot paths and their -en / -zh suffixes, whitespace, the boilerplate version note copied verbatim from an existing post, and copying landing strings into the dictionaries verbatim.

The key never enters the repo. It sits in a chmod-600 file outside the tree; the script reads TOKENDANCE_API_KEY or the file named by TOKENDANCE_KEY_FILE, never an argument, and prints neither. Raw responses (with the model's reasoning) are saved in a scratch directory and never committed.