Blockchain

Provides comprehensive project folder structure design guidelines and best practices. Defines standard directory organizations for diverse project types including monorepos, web frameworks, backend services, libraries, and extensions. Ensures scalable, maintainable architecture through consistent file organization patterns. Specializes in separation of concerns, modular architecture, and tooling integration.Use when: designing new project structures, organizing monorepo workspaces with tools like Turborepo/Nx, structuring NestJS backend projects, organizing React/Next.js frontend applications, designing Go service architectures, creating NPM package structures, organizing VSCode extension projects, structuring Chrome extension codebases, planning directory hierarchies, migrating legacy project structures, or establishing code organization conventions for teams.

Use when writing TypeScript with strict mode - covers type definitions, generics, and declaration files

Search code by AST structure using ast-grep. Find semantic patterns like function calls, imports, class definitions instead of text patterns. Triggers on: find all calls to X, search for pattern, refactor usages, find where function is used, structural search, ast-grep, sg.

Comprehensive authentication implementation guidance including JWT best practices, OAuth 2.0/OIDC flows, Passkeys/FIDO2/WebAuthn, MFA patterns, and secure session management. Use when implementing login systems, token-based auth, SSO, passwordless authentication, or reviewing authentication security.

Comprehensive guide to building Bitcoin protocol implementation in Rust, covering cryptographic primitives, blockchain architecture, consensus mechanisms, networking, and wallet development. Use when implementing Bitcoin-compatible systems, learning Bitcoin internals, or developing cryptocurrency applications in Rust.

GitHub Actionsのジョブ出力管理スキル。ジョブ間でのデータ共有、outputs定義、依存関係設定、条件分岐、マトリックス戦略での出力集約を提供。Anchors:• Continuous Delivery / 適用: ジョブ間データフロー設計 / 目的: 信頼性の高いパイプライン構築• GitHub Actions公式ドキュメント / 適用: outputs/needs構文 / 目的: 正確な実装パターン適用Trigger:Use when sharing data between GitHub Actions jobs, defining job outputs,setting up job dependencies with needs keyword, implementing conditional workflows,or aggregating outputs from matrix strategies.

Build scalable, maintainable design systems that unify product experiences. Use when creating component libraries, design tokens, or establishing design standards. Covers atomic design, Storybook, theming, and design system governance.

This skill enables Claude to design NoSQL data models. It activates when the user requests assistance with NoSQL database design, including schema creation, data modeling for MongoDB or DynamoDB, or defining document structures. Use this skill when the user mentions "NoSQL data model", "design MongoDB schema", "create DynamoDB table", or similar phrases related to NoSQL database architecture. It assists in understanding NoSQL modeling principles like embedding vs. referencing, access pattern optimization, and sharding key selection.

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

Expert knowledge for GNU Guix package and service development. Use when creating or modifying Guix packages, system services, home services, or working with a Guix repository checkout. Handles package definitions, build systems, service types, configuration records, and development workflows.

暗号化鍵のライフサイクル管理（生成、ローテーション、失効、バックアップ）のベストプラクティスを提供するスキル。Anchors:- NIST SP 800-57 / 適用: 鍵ライフサイクル全般 / 目的: 業界標準準拠- AWS KMS Best Practices / 適用: クラウド鍵管理 / 目的: クラウド実装パターン- Continuous Delivery (Jez Humble) / 適用: 自動化設計 / 目的: ローテーション自動化Trigger:Use when implementing key generation, rotation, revocation, backup strategies, or managing cryptographic key lifecycle.encryption key, key rotation, key lifecycle, key management, cryptographic keys, HSM, KMS

ドメイン駆動設計における境界付けられたコンテキストの特定、境界定義、コンテキストマップ作成、統合戦略設計を支援するスキル。チーム責務の整理、モデルの分離、連携方式の選定を体系化する。Anchors:• Domain-Driven Design / 適用: 境界設計 / 目的: ドメイン境界の明確化• Implementing Domain-Driven Design / 適用: コンテキストマップ / 目的: 統合パターンの適用• Context Mapping (Brandolini) / 適用: 境界調整 / 目的: チーム間協調の整理Trigger:Use when defining domain boundaries, creating context maps, choosing integration strategies, or clarifying team ownership for services/modules.

Claude Code スラッシュコマンドの基本構造（YAML frontmatter/本文パターン/ファイル構造）を整理し、最小構成と設計判断を支援するスキル。frontmatter設計、本文パターン、配置ルールを一貫して整理する。Anchors:• The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: 構造設計の実務 / 目的: コマンド構造の再現性確保• 18-skills.md 仕様 / 適用: スキル構造の整合 / 目的: frontmatter規約の統一Trigger:Use when designing slash command structure, defining YAML frontmatter fields, or establishing consistent command composition patterns.command structure, YAML frontmatter, command composition, minimal command template

OAuth 2.0認可フローの実装パターンとセキュリティベストプラクティス。Authorization Code Flow、PKCE、Refresh Token Flowの正確な実装を提供。Web/SPA/モバイルアプリでの安全な認可フロー実装を支援。Anchors:• OAuth 2.0 Simplified (Aaron Parecki) / 適用: 認可フロー全般 / 目的: RFC準拠の正確な実装• Web Application Security (Andrew Hoffman) / 適用: セキュリティ設計 / 目的: 脅威モデリングと対策• RFC 6749 (OAuth 2.0 Framework) / 適用: プロトコル仕様 / 目的: 標準準拠の担保Trigger:Use when implementing OAuth 2.0 authentication, configuring authorization flows, integrating with OAuth providers, implementing PKCE for SPAs, or managing token lifecycle.oauth2, authorization code, pkce, access token, refresh token, oauth provider, google auth, github oauth

Create slash commands (/command). Use when creating files in ~/.claude/commands/ or .claude/commands/, when user asks to "create a command", "add a slash command", "make /something", or when defining new /workflows.

Defines measurable performance budgets for bundle size, API latency, database queries, and render times. Provides enforcement strategies and monitoring plans. Use for "performance budgets", "performance monitoring", "web vitals", or "optimization targets".

IEEE 830やDoc as Codeなどの標準に基づき、技術文書の構造と品質基準を整えるスキル。テンプレート適用と検証フローを通じて、再利用性と明確性を高める。Anchors:• IEEE 830 / 適用: 仕様書構造 / 目的: 標準化• Documentation as Code / 適用: 文書運用 / 目的: 継続的管理• Software Requirements (Karl Wiegers) / 適用: 要求記述 / 目的: 明確性Trigger:Use when defining documentation standards, creating SRS templates, or reviewing technical docs for consistency.documentation standards, IEEE 830, SRS, doc-as-code, documentation review

複数の要件や要望を体系的に分析・評価し、実装する項目を決定するスキル。MoSCoW分類、優先度スコアリング、影響分析を提供する。プロジェクト初期段階での要件整理から、開発中の追加要望への対応まで幅広く活用できる。Anchors:• Software Requirements (Karl Wiegers) / 適用: 要件優先順位付け / 目的: リソース最適配分• Lean Analytics (Alistair Croll) / 適用: ビジネス価値評価 / 目的: 戦略的決定支援• Prioritization Frameworks / 適用: MoSCoW, RICE, Kano / 目的: 体系的な優先順位決定Trigger:Use when triaging multiple requirements, prioritizing features, defining scope, or making resource allocation decisions.requirements triage, priority scoring, MoSCoW classification, scope management, feature prioritization, 要件トリアージ, 優先順位付け

Compose technology-specific agent identity and patterns. Invoke before spawning agents (Developer, SSE, QA, Tech Lead, RE, Investigator) to enhance expertise based on project stack. Returns composed specialization block with token budgeting.

Agent logs, reasoning, and token tracking. Use when logging interactions, saving reasoning, tracking tokens, or managing events.