Summarize the current conversation (or part of it) in a publishable markdown file in the agent voice for the user to publish verbatim. DO NOT use this skill to ghostwrite in the user's voice or to draft original blog posts - it is strictly for summarizing a chat that already happened. Use when user asks for a write up or summary of the chat.
Collaborate with the user asynchronously through a shared markdown file in the working tree. The agent writes questions or proposals in the file and stops; the human replies at their own pace, freeform. Use when the user mentions "lazychat" or asks to "discuss in a file", when the task has several entangled decisions better thought through than chatted through, or when the user may want to step away and reply later. Do NOT use for single-question decisions, bug fixes, or when the user is actively present and driving. Requires the lazychat CLI to be installed.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Rewrite documents so AI agents follow them more reliably. Use when optimizing CLAUDE.md, AGENTS.md, READMEs, runbooks, specs, or any instructional document for AI consumption. Applies context engineering patterns: attention-aware structure, positive framing, token efficiency, canonical examples, consistent terminology, and explicit degrees of freedom. Do NOT use on code files, configs, or content that humans read but agents do not.
Extract and distill project knowledge for Claude.ai Projects. Use when the user wants to generate or update a set of files to upload to a Claude.ai Project so they can discuss the codebase in claude.ai conversations. Triggers on requests like "sync to claude project", "generate project knowledge", "update claude.ai project files", or "extract knowledge for claude.ai".
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
Verify factual claims in text before delivering it to the user. Use this skill whenever you are writing, reviewing, or editing blog posts, technical specs, tool comparisons, documentation, or any content that makes verifiable claims. Also trigger when the user mentions fact-checking, verification, AI slop, hallucination detection, or asks you to review content for accuracy. This skill should run as a final pass before presenting written content. Do not skip it just because you feel confident about the claims.