writing▌

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

This skill provides end-to-end support for writing high-quality computer science research papers. It focuses on constructing clear, compelling technical narratives while adhering to field-specific conventions.

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

Structured B2B case study creation with STAR framework, metrics visualization, and research integration. \n \n Follows the Situation-Task-Action-Result framework with templates for headline, snapshot box, challenge, solution, and results sections \n Emphasizes quantified metrics and before/after comparisons across time, money, efficiency, growth, and satisfaction categories \n Includes guidance on customer quotes, data visualization via Python charts, and industry research using search tools \n

Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in .claude/hookify.{rule-name}.local.md files.

Write professional press releases with research and fact-checking via inference.sh CLI.

Create compelling B2B case studies with research and visuals via inference.sh CLI.

本技能提供党政机关公文写作的完整指南，涵盖格式规范、常用模板、写作技巧和质量检查，确保公文格式正确、语言规范、结构清晰。