Technical Writing

Generate comprehensive Enterprise AI Product White Papers using existing product documentation from Google Drive as source material. Use when users request "create a product white paper", "generate a white paper for [product]", or similar requests for enterprise-grade product documentation for SaaS, hardware, or service offerings.

Use when reviewing commit messages for compliance with the seven rules from cbea.ms/git-commit - checks subject line length, imperative mood, line wrapping, and that the message explains what and why

Best practices for writing high quality production grade Python code

Generate comprehensive documentation from codebase analysis - creates README sections, API docs, migration guides, and examples from code

Claude Codeで作業をする際に、docsディレクトリ内にmarkdown形式で作業ログを記録します。作業開始時、重要な変更時、作業完了時に自動的に使用されます。

docs/plan.md内のTODOリストを管理します。TODO項目の追加、完了マーク、整理を行います。ユーザーがplan.mdの更新、TODO管理、計画の進捗確認を依頼したときに使用してください。プロジェクト固有のTODO形式ルール（フラット構造、エピック化など）を遵守します。

This skill should be used when the user asks to "confluence page", "create documentation", "tech design", "write to confluence", "read from confluence", "link confluence", "create TDD", "write runbook", "meeting notes", "release notes", "architecture decision", or needs guidance on creating, managing, and organizing documentation in Confluence with integration to Jira workflows.

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

Guide for implementing features using Test-Driven Development (TDD) methodology. Use when: (1) User requests to implement a feature using TDD, (2) User asks to write tests first before implementation, (3) User mentions Red-Green-Refactor cycle, (4) Starting a new feature that requires systematic testing. This skill provides step-by-step TDD workflows, concrete test patterns, and best practices for writing tests before implementation in TypeScript/React projects using Vitest.

Generate user-friendly release notes from git commits. Use this when preparing releases, writing changelogs, or summarizing development progress.

This skill should be used when the user asks to "search Notion", "find in Notion", "search my Notion workspace", "create Notion page", "make a Notion page", "update Notion page", "edit Notion page", "query Notion database", "get Notion database", "read Notion page", "get page content from Notion", "list Notion pages", or mentions Notion integration, Notion workspace, or Notion API access.

Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

Use this skill when you need to write lib functions in `srs/lib` for the Next.js app

Create user-centric product definitions by analyzing the repository, inferring product goals and user needs, clarifying ambiguities through structured questioning, and generating comprehensive product.md documentation. Use when the user mentions "product definition", "define product", "product strategy", or needs to document user personas, pain points, and user journeys.

Comprehensive Python programming guidelines based on Google's Python Style Guide. Use when Claude needs to write Python code, review Python code for style issues, refactor Python code, or provide Python programming guidance. Covers language rules (imports, exceptions, type annotations), style rules (naming conventions, formatting, docstrings), and best practices for clean, maintainable Python code.

Orient to current project by reading CLAUDE.md and architecture docs. Auto-invokes when Claude detects a new or unfamiliar repository. Can also be triggered by "orient me", "what is this project", or "prime session".

Safe filesystem operations for agents, including path normalization vs resolution, temp file handling, atomic replacement, and spooled buffers. Use when reading/writing user-supplied paths, staging outputs, or managing temporary files; triggers: filesystem, os.path, tempfile, path normalization, realpath, atomic write.

Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.

Run dotnet test, capture failed test cases, and generate a rerun filter plus a markdown failure summary. Use when test runs fail and you need a focused rerun command or a compact failure report.

nextjs expert with self-populating documentation