Use when changing or auditing zhihu CLI commands, help text, README command examples, or bare zhihu help semantics.
Use when maintaining this repository after v3.0.1-final, deciding scope, rejecting broad rewrites, or preparing a small stabilization change.
Use when changing Markdown output, image downloading, SQLite writes, save contracts, or fetch workflow persistence behavior.
Use when modifying config schema, runtime config loading, Cookie paths, logs, browser profile paths, or local output path resolution.
Use when updating README, README_EN, CONSTITUTION, AGENTS, install docs, command examples, or governance wording.
Use when changing scraper payload parsing, typed scraper contracts, supported Zhihu URL handling, browser fallback behavior, or anti-drift tests.
This skill should be used when the user asks to "write a readme", "create readme", "generate readme", "improve readme", "audit readme", "review readme", "fix readme", "readme best practices", "readme standard", "perfect readme", or mentions README quality, documentation standards, or developer experience documentation.
README quality standards for engaging, accessible, scannable content including problem-solution hooks, plain language (no unexplained jargon), acronym context, paragraph limits (≤5 lines), benefits-focused language, visual hierarchy, and progressive disclosure. Essential for creating effective README files that welcome and guide users.