writing▌

Detailed implementation planning for multi-step engineering tasks with bite-sized, test-driven steps. \n \n Generates comprehensive plans assuming zero codebase context, breaking work into 2–5 minute tasks following TDD principles (failing test, minimal implementation, passing test, commit) \n Produces structured markdown documents with exact file paths, complete code snippets, and specific shell commands with expected outputs \n Designed for handoff to either subagent-driven execution (fresh ag

Authentic LinkedIn posts that establish thought leadership through genuine insight, not engagement optimization. \n \n Emphasizes authenticity over virality: real experiences, specific insights, and honest reflection resonate more than manufactured vulnerability or perfectly structured stories \n Provides five post formats (story, list, contrarian, observation, and media-based) with templates and guardrails for each, plus guidance on hooks, body structure, and closings \n Covers voice developmen

Draft publication-ready ML/AI/Systems papers for top conferences with citation verification and LaTeX templates. \n \n Supports 12 major venues (NeurIPS, ICML, ICLR, ACL, AAAI, COLM, OSDI, NSDI, ASPLOS, SOSP) with conference-specific templates, page limits, and submission requirements \n Enforces programmatic citation verification via Semantic Scholar and CrossRef APIs to prevent hallucinated references; marks unverifiable citations as explicit placeholders \n Provides writing philosophy from le

Manuscript writing with structured outlines, full-paragraph prose, and publication-ready formatting. \n \n Two-stage writing process: create section outlines with research-lookup, then convert to flowing paragraphs (never submit bullet points in final manuscripts) \n Supports IMRAD structure, alternative formats (reviews, case reports, meta-analyses), and discipline-specific terminology across biomedical, molecular, chemistry, ecology, physics, and social sciences \n Handles citations in APA, AM

Define patterns and messages that trigger contextual warnings or blocks during agent tool use. \n \n Rules are markdown files with YAML frontmatter stored in .claude/hookify.{rule-name}.local.md that match against bash commands, file edits, agent stops, or user prompts \n Supports simple regex patterns or advanced multi-condition rules with operators like regex_match, contains, equals, and starts_with \n Actions include warn (show message, allow operation) or block (prevent operation or stop ses

Framework for defining a single, customer-centric metric that aligns teams and drives product decisions. \n \n Measure value delivered to users, not revenue or internal activity; use proxy metrics like messages sent or nights booked that correlate with long-term outcomes \n Ensure simplicity and universal understanding across the company; avoid composite scores and technical jargon that obscure meaning \n Verify actionability by confirming teams can influence the metric through their work, and a

Framework-driven guidance for writing specs and design documents from seven product leaders. \n \n Determine fidelity level upfront: low-fi sketches for alignment, high-fi specs for implementation details \n Favor prototypes over static documentation; test the feel with real software rather than screenshots \n Use fat marker sketches and breadboarding to avoid getting stuck on UI details like colors or spacing \n Recognize that temporary design shortcuts often become permanent product decisions;

Help teams write focused, actionable product requirements documents using frameworks from 11 product leaders. \n \n Start with problem and context before solutions; include \"why now\" to justify timing and urgency against competing priorities \n Choose the right format for your product type: traditional PRDs for feature specs, prototypes or prompt sets for AI features, executable evals as living requirements \n Define success upfront with clear metrics and outcomes; keep documents lightweight a

Strunk's timeless rules for clearer, stronger prose in documentation, commit messages, and UI text. \n \n Covers 18 core principles from The Elements of Style including active voice, positive form, concrete language, and ruthless concision \n Includes reference files on grammar, composition, formatting, and common word misuse; most tasks need only the composition section (~4,500 tokens) \n Identifies and helps avoid AI writing patterns: puffery, empty \"-ing\" phrases, promotional adjectives, an

Professional press releases in AP style with inverted pyramid structure and fact-checking. \n \n Covers all major release types: product launches, funding announcements, partnerships, milestones, and executive hires \n Includes detailed AP style formatting rules, headline guidelines, dateline conventions, and quote attribution standards \n Provides research workflows using inference.sh CLI to verify claims, check market data, and gather industry context before writing \n Features section-by-sect