Technical Writing

Notion workspace integration. Use when user wants to read/write Notion pages, search databases, create tasks, or sync content with Notion.

Comprehensive statistical analysis toolkit for research. Conduct hypothesis tests (t-test, ANOVA, chi-square), regression, correlation, Bayesian stats, power analysis, assumption checks, and APA reporting. Use when the user asks about statistics, needs help analyzing data, or when writing methods sections that include statistical approaches.

Optimize content for AI search engines (ChatGPT, Perplexity, Google AI Overviews).Use when: (1) Auditing content for AI citability, (2) Writing content designed to becited by AI assistants, (3) Analyzing why content isn't being cited, (4) Adaptingexisting SEO content for answer engines. Spanish-language technical content focus.

Expert in codebase archaeology and documentation retrieval. Use this when starting new project phases, refactoring large modules, or integrating new frameworks.

Generate project documentation including CONTENTS.md navigation files and AGENTS.md instructions. Use when creating documentation structure, project indexes, or AI agent configuration files.

TypeScript development best practices, patterns, and conventions. Use when writing TypeScript code, reviewing .ts/.tsx files, discussing type safety, generics, utility types, or TypeScript project configuration. Triggers on mentions of TypeScript, tsconfig, type inference, generics, discriminated unions, React TypeScript.

Create comprehensive technical specification documents through interactive Q&A. Use when (1) user asks to write a Tech Spec, (2) user wants to plan a new feature, (3) user needs to create technical documentation for a feature, (4) user mentions "tech spec", "technical specification", or "feature planning document".

Follow truth-first development with focused feature work, accurate spec maintenance, clean version control, environment-based configuration, and infrastructure-as-code deployments. Use this skill when managing requirements, working in branches, handling configuration, reviewing code, maintaining documentation, or deploying with Ansible. Applies to all development activities requiring honest communication, systematic processes, dependency management, and radical transparency in documentation and decision logs.

Generate or update the methods section based on actual scripts in the pipeline. Links code directly to reproducible documentation. Use when the user types /write_methods, after completing scripts, when methods.md is out of sync with code, or before writing results.

BANKSY spatial transcriptomics analysis - comprehensive documentation with notebooks and API

Documentation of available data science libraries (scipy, numpy, pandas, sklearn) and best practices for statistical analysis, regression modeling, and organizing analysis scripts. **CRITICAL:** All analysis scripts MUST be placed in reports/{topic}/scripts/, NOT in root scripts/ directory.

Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.

Guide developers on writing BDD specifications using Gherkin syntax, feature files, and step definitions

Generate package-info.java files for Java packages. Use when the user requests to add package documentation files to Java packages, create package-info.java files, or document Java package structures. Automatically scans directories for Java packages and creates Javadoc package documentation files where they don't exist.

Provides reference documentation and examples for all of the available Flowbite TailwindCSS HTML UI Components plus the related Typography and Forms plugins.

Use when writing CSS for Discourse core, themes, or plugins - handles BEM class naming, modifiers with double dashes, block__element structure, and is-/has- state prefixes

Bilingual documentation (EN/UK), MkDocs, Ukrainian plurals for Pulse Radar.

Publishing assistant for Thomas's Astro-based GitHub Pages site (readme-pages). Creates publish-ready Markdown files for notes, recipes, and pages. Use when asked to write blog posts, articles, notes, recipes, or content for the readme-pages site at thomasrohde.github.io/readme-pages. Also use for content requests mentioning "publish", "blog", or "my site".

Semantic compression of verbose documentation into OCTAVE format achieving 60-80% reduction with 100% decision-logic fidelity. Use when converting natural language to OCTAVE, streamlining documentation, creating semantic density, optimizing agent prompts, or compressing knowledge artifacts. Triggers on: octave compression, compress to octave, semantic compression, documentation streamlining, OCTAVE optimization, compress documentation, semantic density.

ゲームの要件定義書を作成するためのスキル。漠然としたゲームアイデアを設計可能な形に変換する。使用タイミング：(1)「ゲームを作りたい」「新しいゲームを企画したい」と言われた時、(2)「ゲームのアイデアを整理したい」「要件をまとめたい」と言われた時、(3)「プレイサイクルを考えたい」「ゲームの仕様を決めたい」と言われた時。出力形式はMarkdownファイル。ジャンル別テンプレート（デッキ構築、ローグライク、RPG、パズル、アクション、タワーディフェンス、SRPG）も用意。