Technical Writing

Automatically detect and analyze scientific data files across 200+ formats, generating detailed markdown reports with quality metrics and analysis recommendations.

Creates, updates, or optimizes an AGENTS.md file for a repository with minimal, high-signal instructions covering non-discoverable coding conventions, tooling quirks, workflow preferences, and project-specific rules that agents cannot infer from reading the codebase.

Generate polished code snippet images with syntax highlighting, supporting PNG, SVG, and WebP exports via the snipgrapher CLI.

Creates, structures, and reviews technical documentation using the Diátaxis framework, organizing content into tutorials, how-to guides, reference material, and explanations.

Designs and documents structured incident response playbooks aligned with NIST SP 800-61r3 and SANS PICERL frameworks, covering playbook structure, decision trees, escalation criteria, RACI matrices, and SOAR integration.

Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.

Develop and implement OT-specific incident response playbooks aligned with SANS PICERL framework, IEC 62443, and NIST SP 800-82 that address unique ICS challenges including safety-critical systems, limited downtime tolerance, and coordination between IT SOC, OT engineering, and plant operations teams.

Builds a structured ransomware incident response playbook aligned with the CISA StopRansomware Guide and NIST Cybersecurity Framework, covering preparation, detection, containment, eradication, recovery, and post-incident phases with actionable checklists.

Build a vulnerability exception and risk acceptance tracking system with approval workflows, compensating controls documentation, and expiration management.

Replace heavy UX deliverables with hypothesis-driven design, collaborative sketching, and rapid experiments to learn what users actually need.

Manage software complexity through deep modules, information hiding, and strategic programming, with a scoring framework for evaluating design quality.

Classify customer support tickets, emails, or chats by category and priority, draft responses, and document next steps.

Search and fetch Notion pages, synthesize findings, and publish structured briefs, summaries, comparisons, or reports with citations and source links.

Convert Notion specs into implementation plans, tasks, and progress tracking with linked Notion pages.

Extracts specifications from existing codebases by analyzing structure, data flows, and observable behaviors to document requirements in EARS format.

Design REST and GraphQL APIs with OpenAPI 3.1 specifications, resource modeling, versioning strategies, pagination patterns, and error handling standards.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Generates, formats, and validates technical documentation including docstrings, OpenAPI specs, JSDoc annotations, documentation sites, and user guides.

Write changelogs and release notes that users actually read, with guidance on categorization, user-facing language, visuals, and distribution.

Write compelling B2B case studies using the STAR framework, with research, data visualization, and distribution formats.

Write developer-focused technical blog posts with structured templates, code formatting rules, and audience-specific guidance for tutorials, deep dives, postmortems, and architecture posts.

Turn rough notes, workshop content, or prompt dumps into compliant, publish-ready SKILL.md files that pass validation and integrate with repo documentation.

Provides paragraph-level structural blueprints for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys, including page allocation, writing patterns, and venue-specific checklists.

Build and review high-quality technical documentation, including agent instruction files and contributor-governance files, with support for audits, multilingual parity, and sub-agent orchestration.

Write clear, helpful UI copy including microcopy, error messages, empty states, and CTAs that guide users and reinforce product voice.

Plan and govern product content: audit existing material, define content models, establish voice and tone, and set ownership workflows.

Structure a pattern library entry with problem context, solution pattern, usage examples, and related patterns.

Establish clear naming conventions for design assets, components, and tokens to make design systems predictable and maintainable.

Write clear design rationale that connects decisions to user needs, business goals, and principles.

Breaks down technical topics into plain-English explanations covering who, what, where, why, and when.

Maps a codebase into feature-grouped flowcharts, identifies duplicated concerns across features, and proposes a unified architecture with handoff prompts for refactoring.

Generates a comprehensive narrative report analyzing a project's entire development history from claude-mem's persistent memory timeline.

Guide a visible, verified code walkthrough in Neovim with Terminal Control and Navi, optionally recording the presentation with OBS or retaining terminal evidence.

Turns a GitHub pull request into a code-change explainer video with changelog, feature reveal, or refactoring walkthrough built from the diff, commits, and files.

Turn a weekly changelog markdown into a branded square video with animated UI mockups, voiceover, and captions.

Defines the high-level motion law for multi-scene videos, ensuring seamless transitions and continuous camera movement through vector rules, carriers, causal motion, and seam enforcement.