writing▌

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

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

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.

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

Source: obra/superpowers

$23

Create clear, user-focused documentation with step-by-step guides, screenshots, and FAQ sections. \n \n Generates four documentation types: quick-start guides, task-focused how-to articles, FAQ pages, and learning-focused tutorials \n Emphasizes visual clarity with embedded screenshots, GIFs, and structured numbered instructions designed for non-technical users \n Includes troubleshooting sections, related links, and multiple support contact methods to reduce user friction \n Follows plain-langu

$22