技術寫作

Validates PHP test files for CakePHP projects, ensuring compliance with testing standards including proper documentation format, Configure::read usage, and avoiding prohibited patterns

曖昧な指示を明確・具体的・実行可能な形式へ変換するスキル。「適切に」「よろしく」といった不明瞭な表現を、測定可能な成功基準と段階的ステップへ分解します。Anchors:• Made to Stick (Heath) / 適用: 簡潔性・具体性の原則 / 目的: 記憶に残る指示設計• The Pyramid Principle (Minto) / 適用: 論理構造 / 目的: 結論先行による理解速度向上• 5C Principle / 適用: 品質評価 / 目的: Clear, Concise, Complete, Concrete, CorrectTrigger:Use when instructions contain vague terms like "appropriately", "properly", "handle", or when steps lack clear success criteria. Apply before creating prompts, requirements, runbooks, or directive documentation.instruction clarity, vague expression, 5C principle, pyramid principle, success criteria

Go language expertise for writing idiomatic, production-quality Go code. Use for Go development, concurrency patterns, error handling, testing, and module management. Triggers: go, golang, goroutine, channel, go mod, go test, effective go.

Guidelines for creating and modifying markdown files in PooCommerce. Use when writing documentation, README files, or any markdown content.

Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes

Use when the user asks to generate comprehensive feature documentation with verified test cases, create feature README with code evidence, or document a complete feature with test verification. Triggers on keywords like "feature documentation", "document feature", "comprehensive docs", "feature README", "test verification", "verified documentation".

Convert Markdown documents (*.md files) to self-contained HTML files with embedded images. Use when you need a portable, offline-friendly single HTML file from Markdown—ideal for blog posts, essays, reports, or any content that should work without external dependencies.

MANDATORY when writing commit messages. Structures commits with type prefix, what+why body, and architectural file tree.

Generate comprehensive context-setting markdown files for coding tasks by intelligently exploring codebase and structuring work with ROLE, CONSTRAINTS, STYLE, file reading order, and structured tasks. Use proactively when the user is starting a complex dev task requiring multiple steps or file reads.

要件ドキュメントの作成・構造化・品質管理・ハンドオフを支援するスキル。カール・ウィーガーズの要求工学理論に基づき、ステークホルダーと開発チームの双方に有用な仕様書を作成する。Anchors:• Software Requirements (Karl Wiegers) / 適用: 要件管理全般 / 目的: 明確で検証可能な仕様• IEEE 830 SRS Standard / 適用: ドキュメント構造 / 目的: 標準準拠の仕様書• Don't Make Me Think (Steve Krug) / 適用: 情報設計 / 目的: 読みやすいドキュメントTrigger:Use when creating requirements documents, writing specifications, preparing stakeholder reviews, or establishing requirements traceability.requirements document, specification, SRS, stakeholder review, traceability matrix, 要件定義書, 仕様書

Two-phase workflow to keep project documentation synchronized with code changes

Enforces ventilated prose and concise technical writing standards when the user is writing or editing standalone documentation files (e.g., Markdown, AsciiDoc). This skill should not be used for code documentation or docstrings.

Claude Code の hooks 設計・実装・検証を支援し、セッション/ツール連携の自動化と品質ゲートを安全に構築するスキル。イベント（SessionStart/PreToolUse/PostToolUse/Stop）の選定、スクリプト設計、検証フローを整理する。Anchors:• Claude Code Documentation / 適用: Hook events and configuration / 目的: 正しいイベント選定• Continuous Delivery (Jez Humble) / 適用: 自動化と検証 / 目的: 品質ゲート設計• The Pragmatic Programmer (Hunt/Thomas) / 適用: 自動化と安全性 / 目的: 安全なフック運用Trigger:Use when configuring Claude Code hooks, designing pre/post tool automation, writing hook scripts, or validating hook-driven workflows.claude code hooks, pretooluse, posttooluse, sessionstart, stop, hook scripts, automation

Node.jsにおけるストリーム処理とバックプレッシャー管理の専門知識。大容量ファイルの効率的処理、メモリ使用量の最適化、Readable/Writable/Transform/Duplexストリームの適切な活用方法を提供。Anchors:• Node.js Streams API Documentation / 適用: ストリームAPI全般 / 目的: 公式APIの正確な使用• Backpressuring in Streams (Node.js official) / 適用: バックプレッシャー管理 / 目的: メモリ効率最適化• The Pragmatic Programmer (Hunt and Thomas) / 適用: 実装品質 / 目的: 保守性とテスタビリティTrigger:Use when implementing stream processing in Node.js, handling large files, managing backpressure, or building data transformation pipelines.nodejs stream, stream processing, backpressure, readable stream, writable stream, transform stream, duplex stream, pipeline, large file

CUDA kernel development, debugging, and performance optimization for Claude Code. Use when writing, debugging, or optimizing CUDA code, GPU kernels, or parallel algorithms. Covers non-interactive profiling with nsys/ncu, debugging with cuda-gdb/compute-sanitizer, binary inspection with cuobjdump, and performance analysis workflows. Triggers on CUDA, GPU programming, kernel optimization, nsys, ncu, cuda-gdb, compute-sanitizer, PTX, GPU profiling, parallel performance.

Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".

MANDATORY invocation for ALL LLM-related work. Invoke immediately when: - ANY mention of model names, IDs, or versions - ANY configuration of AI providers or APIs - ANY defaults/constants for LLM settings - ANY prompt engineering or modification - ANY discussion of model capabilities or features - ANY changes to AI-related dependencies - Reading/writing .env files with AI config - Modifying aiProviders.ts, prompts.ts, or similar - Reviewing AI-related pull requests - Debugging LLM integration issues CRITICAL: Training data lags reality by months. ALWAYS research first. Use WebSearch, Exa MCP, or Gemini CLI before making ANY LLM decisions.

プロジェクト固有のアーキテクチャ設計原則を統合するスキル。ハイブリッドアーキテクチャ（shared/features）、Clean Architecture依存関係ルール、データベース設計、REST API、テスト戦略、エラーハンドリング、CI/CD原則をエージェント設計に適用する。Anchors:• Clean Architecture / 適用: 依存関係ルールと境界設計 / 目的: アーキテクチャ層の分離と依存方向制御• Hybrid Architecture (shared/features) / 適用: ドメイン分離と再利用設計 / 目的: 循環依存回避と単一責任維持• docs/00-requirements/ / 適用: プロジェクト技術スタック仕様 / 目的: 要求仕様との整合性確保Trigger:Use when designing agents that generate project-specific files, database operations, API integrations, test strategies, error handling, or CI/CD workflows. Apply when determining file placement (shared/ vs features/), enforcing dependency rules, or ensuring architecture compliance.architecture compliance, hybrid structure, shared features, dependency rules, agent file generation, database design, REST API, testing strategy

Validate changes for factual accuracy, completeness, and intent preservation without modifications. Scope: fact-checking, verifying refactors, validating imports, checking rewrites, comparing versions, reviewing documentation changes. Triggers: "fact-check", "verify", "validate", "compare versions".

ドキュメント構造設計・リソース分割・階層設計を専門とするスキル。500行制約に基づく適切なファイル分割とトピックベース組織化により、保守性と発見可能性の高いドキュメントアーキテクチャを実現する。Anchors:• Information Architecture (Rosenfeld/Morville) / 適用: 情報組織化パターン / 目的: 発見可能性向上• Clean Architecture (Robert C. Martin) / 適用: 依存関係ルール / 目的: 責任分離設計• The Pragmatic Programmer (Hunt/Thomas) / 適用: DRY原則 / 目的: 重複回避Trigger:Use when designing documentation structure, splitting large files over 500 lines, organizing resources with topic-based structure, improving discoverability, or establishing naming conventions.documentation structure, file splitting, directory organization, hierarchy design, naming conventions, 500-line constraint