技術寫作

Rust language expertise for writing safe, performant, production-quality Rust code. Use for Rust development, ownership patterns, error handling, async/await, and cargo management. Triggers: rust, cargo, rustc, ownership, borrowing, lifetime, Result, Option, traits, crates.

Apply testing philosophy: test behavior not implementation, minimize mocks, AAA structure, coverage for confidence not percentage. Use when writing tests, reviewing test quality, discussing TDD, or evaluating test strategies.

This skill automates API endpoint testing and documentation. It runs curl requests against specified endpoints, captures responses, validates against OpenAPI spec, and generates markdown documentation. Use after implementing new endpoints or when verifying API behavior.

Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts

Tailwind CSS のユーティリティ設計とパターン化を支援するスキル。レイアウト・状態・レスポンシブ対応を整理し、再利用可能なUIパターンを構築する。Anchors:• Tailwind CSS Documentation / 適用: ユーティリティ設計 / 目的: 公式ベストプラクティス準拠• Responsive Web Design / 適用: ブレークポイント設計 / 目的: モバイルファーストの整理• Class Variance Authority (CVA) / 適用: バリアント設計 / 目的: 状態と組み合わせの整理Trigger:Use when designing Tailwind UI patterns, reducing utility bloat, or standardizing responsive and state styles.tailwind css, utility classes, responsive design, component patterns, class variance

Use when the user asks to generate test cases, create test specifications, write unit tests, create QA documentation, or analyze test coverage. Triggers on keywords like "test", "test case", "unit test", "QA", "coverage", "Given When Then", "BDD", "TDD", "spec".

楽観的更新（Optimistic Updates）パターンの実装スキル。サーバーレスポンス前にUIを即座更新し、失敗時のロールバック機構を提供することで、レスポンシブなユーザー体験を実現します。Anchors:• Designing Data-Intensive Applications (Martin Kleppmann) / 適用: 分散システムにおける楽観的並行制御 / 目的: 競合検出とロールバック戦略の設計• React Query (TanStack) / 適用: onMutate/onError/onSettledフック / 目的: 楽観的更新とロールバックの自動化• SWR Documentation (Vercel) / 適用: optimisticDataとrollbackOnError / 目的: 宣言的な楽観的更新の実装Trigger:Use when implementing instant UI feedback before server response, hiding CRUD latency, implementing optimistic updates with React Query/SWR, designing rollback strategies, or handling conflict states.optimistic update, UI feedback, rollback, React Query, SWR, mutation, conflict resolution

ユースケース駆動の要件分析スキル。ユーザーとシステムの対話を構造化し、ビジネスロジックを明確にします。アクター識別から詳細シナリオ設計まで段階的に進めます。Anchors:• 『Writing Effective Use Cases』(Alistair Cockburn) / 適用: ユースケース設計 / 目的: 要件仕様の明確化• 『The Pragmatic Programmer』(David Thomas, Andrew Hunt) / 適用: 要件分析 / 目的: 実践的な品質維持Trigger:ユースケースモデリング、アクター分析、システム要件定義時に使用

Comprehensive guidance for Minecraft mod development with Fabric, including porting from other mod loaders (Forge, NeoForge). Integrates MCP servers for decompilation, documentation access, and mixin validation. Use when developing Fabric mods, porting from Forge, or working with Minecraft source code.

Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.

Guide PR authoring from creation through review completion. Use when creating/submitting/authoring pull requests, writing PR descriptions, responding to reviewer comments, or implementing review feedback. Covers the full PR lifecycle - creating PRs linked to issues, handling review comments (triaging, responding, implementing suggestions), and getting PRs merged.

A skill for writing Go tests in a TDD workflow. Follow README/Issue requirements and existing test conventions, add a balanced set of table-driven cases across behavior/boundaries/branches, and produce maintainable tests without excessive mocking or coverage-chasing.

Documentation patterns for creating clear, executable, and maintainable usage examples across APIs, CLIs, libraries, and frameworks.Anchors:• Docs for Developers (Jared Bhatti et al.) / 適用: 実践的な例示パターン / 目的: 開発者に即座に理解・実行可能な例を提供• The Documentation System (Diataxis) / 適用: チュートリアル・ハウツー・リファレンス分類 / 目的: 目的に応じた例の種類と粒度を選択• Clean Code (Robert C. Martin) / 適用: 明確な命名・単一責務 / 目的: 自己説明的なサンプルコードTrigger:Use when creating code examples, writing tutorials, documenting API usage, building sample projects, establishing example conventions, or standardizing example patterns across a codebase.example creation, tutorial writing, API documentation, sample code, documentation patterns

creating TINS-compliant README files, generating implementations from TINS READMEs, and validating TINS documentation

Use when creating or updating technical documentation, API documentation, or inline code documentation.

Use when enhancing documentation, adding code comments, creating API docs, or improving technical documentation.

API認証ドキュメント（OAuth 2.0/PKCE、API Key、JWT、トークン管理）の作成と図解を支援するスキル。認証フローの説明、トークン取得手順、セキュリティ注意点をわかりやすく整理します。Anchors:• OAuth 2.0 Simplified / 適用: フロー図解 / 目的: 正確な説明と用語整理• Web Application Security / 適用: セキュリティ注意点 / 目的: 安全な認証ドキュメント• API Documentation Best Practices / 適用: ドキュメント構成 / 目的: 読みやすさの担保Trigger:Use when writing authentication docs, creating OAuth flow diagrams, documenting token management, or preparing quickstart guides for API auth.

GLSL shader fundamentals—vertex and fragment shaders, uniforms, varyings, attributes, coordinate systems, built-in variables, and data types. Use when writing custom shaders, understanding the graphics pipeline, or debugging shader code. The foundational skill for all shader work.

Use when building GitHub-based features - Explains auth token usage, Gist reading/writing and rendering helpers.

Write and optimize Bash, Zsh, and shell scripts with best practices for error handling, argument parsing, portability, and security. Use when writing shell scripts, debugging scripts, implementing command-line tools, or improving shell script maintainability and security.