writing▌

CSF3-compliant Storybook stories that showcase component variations with type safety and consistent structure. \n \n Enforces Component Story Format 3 with TypeScript type annotations, default meta exports, and story object syntax \n Covers story organization patterns for buttons, forms, layouts, data-driven components, and responsive designs \n Includes best practices for extending stories, using decorators for context, and adding descriptive parameters for documentation \n Identifies anti-patt

Apply Strunk's timeless writing rules to improve clarity and professionalism across all prose. \n \n Covers 18 core rules spanning grammar, punctuation, composition principles, and common usage mistakes \n Emphasizes active voice, positive framing, concrete language, and ruthless word elimination as key clarity drivers \n Designed for documentation, commit messages, error messages, UI copy, reports, and any prose humans will read \n Includes token-efficient subagent dispatch pattern: write a dra

Framework for writing job descriptions that attract the right candidates by defining business impact. \n \n Start with 12-month success: define what changes in the business after the hire, not a list of daily tasks \n Identify the spike: determine one or two areas where the candidate must excel, rather than seeking a generalist \n Replace proxies with outcomes: frame requirements around specific capabilities and progress, not years of experience or tool lists \n Use polarizing language intention

Techniques for writing effective fuzzing harnesses across languages and frameworks. \n \n Covers harness fundamentals for C/C++, Rust, Go, and Python, including entry point signatures, input validation, and structured data extraction using FuzzedDataProvider and arbitrary crate \n Includes step-by-step guidance from identifying entry points through testing and iteration, with practical patterns for integer casting, complex inputs, and interleaved fuzzing of multiple operations \n Provides tool-s

Define patterns and messages that trigger Claude warnings or blocks on specific agent actions. \n \n Supports four event types (bash commands, file edits, agent stop, user prompts) plus an \"all\" catch-all, each with regex or multi-condition matching \n Rules use markdown files with YAML frontmatter stored in .claude/hookify.{name}.local.md ; changes take effect immediately on next tool use \n Two matching modes: simple pattern field for single-condition rules, or advanced conditions array for

Structured framework for writing blameless postmortems that drive organizational learning from incidents. \n \n Provides templates for standard postmortems, 5 Whys analysis, and quick incident reviews, with sections for timelines, root cause analysis, detection gaps, and action items \n Emphasizes blameless culture by shifting focus from individual blame to systemic failures and conditions that enabled incidents \n Includes facilitation guide for postmortem meetings, anti-patterns to avoid, and

Create clear, comprehensive technical documentation for specs, architecture, runbooks, and APIs. \n \n Provides templates and step-by-step guidance for five document types: technical specifications, architecture documents, runbooks, API documentation, and changelogs \n Includes audience-specific writing strategies for developers, operations teams, managers, and end users with tailored content focus \n Offers visual aid support via Mermaid diagrams, flowcharts, tables, and code examples with synt

Comprehensive implementation plans for multi-step tasks, breaking down specs into bite-sized, testable steps. \n \n Decomposes requirements into focused tasks (2–5 minutes each) following TDD: write failing test, verify failure, implement, verify pass, commit \n Maps file structure upfront with clear boundaries and responsibilities, ensuring each file has one purpose and files that change together stay together \n Includes exact file paths, complete code samples, and specific commands with expec

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.

Generate Architectural Decision Records (ADRs) following the MADR template with systematic completeness checking.