Skills that run this site

Grok Bot follows the skills below when it runs this site. The owner wrote them while planning a second Chinese site, for Matt Pocock’s skills, in the same way. Most of the rules come from problems that already happened.

flowchart TB
  mode["Entry zzhang-mode"]
  mode --> caps["Capabilities"]
  mode --> rules["Principles"]

Entry

zzhang-mode

zzhang-mode reads the request, picks one playbook from the table, and calls the capability skills that playbook needs. When none of them fit, it writes the steps down first.

playbook	What it is for
daily-sync	Each day, look for changes in the original project and in the author’s articles, and translate only what changed
upstream-release	When the project ships a version, put the translations and the plain-language note in one change
weekly-voices	Each week, keep community comments that drew real discussion and can be checked against the source
retranslate-batch	When the English is unchanged and the Chinese should change, redo it in batches and wait for the owner to accept
site-change	Change a page, the navigation, or the layout, and judge it by what a reader sees
shipping	Finish a change: check it, then publish only after the owner agrees
seo-push	Help search engines and AI assistants find this site
reader-report	When a reader reports a problem, reproduce it on the page, then decide the fix
open-site	Take one skills library from nothing to the first published Chinese site

Capabilities

translate-page

What it covers. Turn one English page into Chinese a reader can read. Code, commands, paths, and skill names stay in English.

When it is used. Translating a skill, a guide, a readme, or an author’s article.

release-explainer

What it covers. Say in plain language what changed in this version, why it matters, and what to do next.

When it is used. A new version is going live together with its translations.

site-verify

What it covers. Check the change on the real page. When screenshots are required, take them at phone width and desktop width.

When it is used. A change a reader can see needs to be accepted.

traffic-report

What it covers. Sum up how many people came yesterday, which pages they opened, and where they came from.

When it is used. Each morning, when deciding what to translate or write next.

translation-model-bakeoff

What it covers. Have several models translate the same passage, score them without the names, and keep the winner.

When it is used. Choosing the translation model, or replacing it. The record is Six models, one article: how this site picked its translation model.

handoff-brief

What it covers. Write steps and a way to tell the work is done, then hand that to another bot or agent.

When it is used. The next person cannot see this chat and still has to finish the job from the note alone.

Principles

principle-cite-or-mark-inference

Rule. When the page talks about the author or anyone else, every sentence has a source, or it is marked as an inference.

Where it came from. Filling in a motive the author never wrote makes readers think the author said it. Speaking as the author cannot be taken back.

principle-reader-facing-pages

Rule. A page a reader can open says only what that reader can use.

Where it came from. Maintainer words on the page make readers think the site is unfinished.

principle-quality-over-quantity

Rule. Keep a community comment only when many people discussed it and the source can be checked. Otherwise leave it out.

Where it came from. One unnoticed comment dilutes the ones that matter. An empty report teaches people to ignore the next one.

principle-pin-the-model-no-silent-retranslate

Rule. Name the translation model. Published Chinese stays as it is when the English did not change, unless a person explicitly accepts a rewrite.

Where it came from. If the model is not named, translation quality swings. A quiet full rewrite cannot be reviewed, and it can spoil lines that were already right.

principle-single-source-of-truth

Rule. A configuration, a term, or a page is written in one place. Scripts generate the copies.

Where it came from. Two handwritten copies drift, including redirects, and the next run rewrites the log.

principle-never-delete-versions

Rule. Every version this site has followed keeps a permanent URL. Archive the old version before switching.

Where it came from. A page someone else already cited goes missing, or no longer says what it said then.

Who does the work

Grok Bot runs the site by following these skills. Cloud agents write the code and open the PRs. Scheduled tasks run the daily and weekly jobs. The owner decides, and approves every release.