深度學習

SwiftUI UI component catalog. Use when implementing NavigationStack, Swift Charts, PhotosPicker, TipKit, ScrollView enhancements, animations, layouts, WebView, Liquid Glass and other UI components. Organized by feature category with OS version compatibility info. Reference for discovering available components and implementation patterns.

Android-specific code review workflow additions for Bitwarden Android. Provides change type refinements, checklist loading, and reference material organization. Complements bitwarden-code-reviewer agent's base review standards.

Provides Jest-based TypeScript testing expertise and best practices. Ensures proper test structure, mocking strategies, async handling patterns, and coverage optimization. Specializes in unit testing, integration testing, test organization with describe/it blocks, jest.mock patterns, snapshot testing, and testing library integration for UI components.Use when: writing TypeScript test files (.spec.ts, .test.ts), structuring tests with describe/it/test blocks, implementing mocks with jest.mock/jest.spyOn, testing async code with async/await or promises, creating test fixtures and helpers, implementing snapshot tests, testing React components with Testing Library, measuring and improving code coverage, or configuring Jest for TypeScript projects.

Meta-skill for Claude Code memory system (CLAUDE.md, static memory). Provides stable principles, keyword registry for documentation lookups, and navigation guidance. Use when working with CLAUDE.md files, memory hierarchy, import syntax, progressive disclosure patterns, memory organization, or best practices for static memory. Delegates to docs-management skill for current implementation details. Keywords: CLAUDE.md, static memory, memory hierarchy, import syntax, progressive disclosure, memory organization, enterprise project user memory.

Central authority for Claude Code hooks management in this repository. Automates enforcement of critical repository rules through hooks. Use when adding hooks, managing hooks, configuring hooks, troubleshooting hooks, or understanding hook behavior. Delegates to docs-management skill for official hooks documentation. Provides organization-specific patterns, configuration management, and workflow guidance.

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.

This skill should be used when the user asks to "create a skill", "write a skill", "edit a skill", "update a skill", "improve skill description", "add skill to plugin", "organize skill content", "create SKILL.md", "skill frontmatter", "skill structure", "progressive disclosure", or needs guidance on skill development, validation, or best practices for Claude Code plugins and personal skills.

Module organization patterns including ports and adapters (hexagonal), module communication, and data isolation. Use when structuring modular monoliths, defining module boundaries, setting up inter-module communication, or isolating database contexts. Includes MediatR patterns for internal events.

Plan explainable AI (XAI) requirements including SHAP, LIME, attention visualization, and regulatory explainability needs.

Central authority for Claude Code enterprise security. Covers enterprise managed policies (managed-settings.json), settings precedence hierarchy, policy file locations (macOS, Linux, Windows), unoverridable organizational policies, cloud execution security (isolated VMs, network access controls, credential protection), IDE security (VS Code, JetBrains), devcontainer security, and security best practices for teams. Assists with configuring enterprise policies, understanding precedence, and implementing organizational security standards. Delegates 100% to docs-management skill for official documentation.

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.

Validate and improve Claude Code configurations (CLAUDE.md, skills, commands, hooks). Use when auditing config quality, checking skill discoverability, organizing .claude directory, or deciding which entity type to use.

Generate comprehensive sensor health and status reports across all LimaCharlie organizations. Use when users ask about sensor connectivity, data availability, offline sensors, sensors not reporting events, or fleet-wide health queries (e.g., "show me sensors online but not sending data", "list sensors offline for 7 days across all orgs").

This skill detects hierarchical (nested) TAD structures from Hi-C contact maps (in .cool or mcool format) using OnTAD, starting from multi-resolution .mcool files. It extracts a user-specified chromosome and resolution, converts the data to a dense matrix, runs OnTAD, and organizes TAD calls and logs for downstream 3D genome analysis.

3層開示モデル（メタデータ→本文→リソース）による段階的な情報提供で、トークン効率と知識スケーラビリティを両立。スキル発動信頼性を最大化し、必要な時に必要な知識だけをロードします。Anchors:• The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: 段階的な情報開示と実践的改善 / 目的: トークン効率を維持しながら深い知識を提供• Progressive Disclosure (Jakob Nielsen) / 適用: 認知負荷の最小化 / 目的: UX設計原則のスキルメタデータへの応用• Information Architecture (Louis Rosenfeld) / 適用: 階層的知識組織化 / 目的: 遅延読み込みとインデックス駆動設計Trigger:Use when designing skill metadata, optimizing token usage, implementing progressive disclosure patterns, improving skill activation reliability, organizing knowledge hierarchically, reducing context window consumption, or creating scalable documentation structures.

優先順位付けフレームワークの専門スキル。MoSCoW法、RICE Scoring、Kano Modelを用いて、限られたリソースで最大の価値を提供するための意思決定を支援します。Anchors:• 『Inspired』（Marty Cagan） / 適用: プロダクト優先順位 / 目的: 価値最大化• Intercom RICE Scoringガイド / 適用: 定量的スコアリング / 目的: データドリブンな意思決定• Kano Model理論（Noriaki Kano） / 適用: 顧客満足度分析 / 目的: 戦略的投資判断Trigger:Use when prioritizing features, requirements, backlog items, or strategic initiatives. Apply to sprint planning, release planning, roadmap development, feature evaluation, or resource allocation decisions.

Design, build, and maintain comprehensive knowledge bases. Bridges document-based (RAG) and entity-based (graph) knowledge systems. Use when building knowledge-intensive applications, managing organizational knowledge, or creating intelligent information systems.

Generate a coverage report for all localization files using the project's check-i18n tool. Use when auditing translation completeness or identifying languages needing attention.

This skill should be used when the user asks to "create CLAUDE.md", "initialize CLAUDE.md", "sync CLAUDE.md with code", "update documentation from codebase", "create .claude/rules/", "manage modular rules", "split large CLAUDE.md", or mentions project documentation setup. Manages complete lifecycle of project instructions including creation, synchronization with code patterns, and modular organization.

SECIモデル（野中郁次郎）に基づく組織知識の形式知化と共有を専門とするスキル。暗黙知（経験、勘、ノウハウ）を形式知（ドキュメント、パターン）に変換し、体系化することで組織全体で再利用可能な知識として活用する。Anchors:• The Knowledge-Creating Company (Nonaka/Takeuchi) / 適用: SECIサイクル4フェーズ（共同化・表出化・連結化・内面化） / 目的: 暗黙知の特定・言語化・統合の理論的基盤• The Pragmatic Programmer (Hunt/Thomas) / 適用: 実践的改善とDRY原則 / 目的: 品質維持と重複知識の統合判断• Design Patterns (Gang of Four) / 適用: パターン記述形式 / 目的: 再利用可能な知識の抽象化と構造化Trigger:Use when formalizing tacit knowledge, documenting best practices, converting code review insights to reusable knowledge, managing organizational knowledge base quality, or applying SECI model workflows.Keywords: knowledge management, tacit knowledge, explicit knowledge, SECI model, documentation, best practices, pattern extraction