菜单
Use when assessing feature completeness, auditing UX or onboarding, or judging whether a feature is "done" — especially gap analyses, SOTA comparisons, and first-run/cold-start reviews.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Process raw-extracted JSON files from PDF book extractions into clean, well-structured markdown. Use this skill whenever a user uploads a raw-extracted.json (or similar JSON with metadata and chunks arrays) from a PDF text extraction pipeline, or when they mention cleaning up, formatting, structuring, or organizing extracted book text. Also trigger when the user mentions OCR output, pypdf extraction, book chapters, or converting messy PDF extractions into readable markdown. This skill handles books with varying extraction quality — from clean text to garbled OCR — and adapts its approach accordingly.
This skill should be used when the user invokes /code-documentation, or asks to "write/generate/audit/update documentation", "write a README", "document this API or codebase", "write a tutorial / how-to / runbook", "write user help docs", "generate docstrings", "write an ADR or RFC", "create a changelog", "produce llms.txt or AGENTS.md", or "turn these docs into a doc site". Produces first-class documentation for any audience (end users, API consumers, contributors, operators, evaluators, AI agents) across all four Diátaxis modes, for the full lifecycle — authoring, generating from a codebase, auditing, and maintaining. Emits publish-ready Markdown or structured content for Docusaurus, MkDocs, Sphinx, Starlight, Mintlify, or Volume.
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture.
Use when the user wants to brainstorm blog topics, generate or score article ideas, review/approve content ideas, track article status, or manage editorial planning — including mentions of "content calendar", "editorial calendar", "blog ideas", "article pipeline", "content backlog", or "publishing schedule".
Checklist for auditing architecture contracts in a develop-by-contract environment. Covers the failure modes most commonly found during contract review: status drift, AI-invented decisions, cross-contract fact drift, stale feature references, missing state specs, and business policy gaps.
Use when analyzing, auditing, reviewing, or explaining a codebase, system, or project state — whenever written claims could mix observed fact with interpretation.
基于 SOC 职业分类
| name | usability-is-existence |
| description | Use when assessing feature completeness, auditing UX or onboarding, or judging whether a feature is "done" — especially gap analyses, SOTA comparisons, and first-run/cold-start reviews. |
This skill defines a non-negotiable usability invariant:
A feature does not meaningfully exist unless at least one realistic interaction pathway allows a first-time user to discover and use it without prior knowledge.
This skill is authoritative and applies across UX, product, and implementation work.
This skill applies whenever an agent:
A feature MUST NOT be considered usable if:
At least one valid pathway MUST:
If no such pathway exists:
Technical existence alone is insufficient.
If an agent claims a feature is “present” or “complete” without a valid user-discoverable pathway:
This skill exists to prevent:
