2,659 件 ・ 関連度順
概要と使いどころ
Use ExecuTorch to export PyTorch models to edge runtime artifacts, build host/device runtimes, choose delegates, profile/debug execution, and operate specialized Qualcomm, Cortex-M, LLM, and binary-size workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use detrex for detection-transformer configs, training/evaluation, demos, model zoo conversion, and package API debugging.
日本語の概要は準備中です。原文の説明を表示しています。
Use EasyR1 for multimodal LLM RL post-training, dataset/reward preparation, core API debugging, and checkpoint export workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building, debugging, testing, or maintaining Plotly Dash applications, callbacks, server backends, component packages, renderer internals, and Dash repository workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Operate Core ML Tools workflows for model conversion, Core ML artifact I/O, optimization, MIL debugging, and platform-aware troubleshooting.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for maintaining, migrating, debugging, and safely operating Microsoft AutoGen Python 0.7.x applications, including AgentChat, Core runtimes, extensions, Studio, Magentic-One, AG Bench, and pyautogen compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
Build, debug, serialize, and integrate Albumentations 2.x augmentation pipelines for images, masks, bboxes, keypoints, volumes, and PyTorch-style datasets.
日本語の概要は準備中です。原文の説明を表示しています。
Use AdalFlow to build, debug, evaluate, optimize, trace, and operate LLM task pipelines, RAG systems, agents, tools, and structured-output workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose failing tests with screenshots, replays, and logs
日本語の概要は準備中です。原文の説明を表示しています。
Validate, lint, audit, or debug Ansible playbooks, roles, inventories, FQCN, tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix Kubernetes pods, CrashLoopBackOff, Pending, DNS, networking, storage, and rollout failures with kubectl.
日本語の概要は準備中です。原文の説明を表示しています。
Research and advise on the best way to approach a software project, including architecture, tech stack, implementation strategy, pricing/operating-cost tradeoffs, benchmark research, and comparisons with similar real-world projects. Use before building, mid-build, or after completion when the user asks for project strategy, optimal approach, research comparables, similar projects, stack selection, vendor/service choice, repo analysis, architecture critique, implementation feedback, or a prioritized improvement plan. Avoid for narrow single-bug debugging or isolated file edits unless the user asks for broader project direction.
日本語の概要は準備中です。原文の説明を表示しています。
Main app Jetpack Compose UI patterns (WooTheme, Fragment hosting, composeView/legacyComposeView helpers, preview annotations, WC components). Use when writing, editing, exploring, debugging, or reviewing Compose UI in the store management app. NOT for POS (WooPos*) code — use the `pos` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
POS (Point of Sale) architecture and patterns. Use when writing, editing, exploring, debugging, fixing bugs, implementing features, or reviewing WooPos-prefixed classes or files under ui/woopos/. POS uses a different architecture than the main app — plain ViewModel (not ScopedViewModel), pure Compose (no Fragments), Compose Navigation (no nav graphs), parent-child SharedFlow event bus. Loading this skill prevents applying main-app patterns that would be wrong for POS. For analytics use `pos-analytics`, for tests use `pos-tests`.
日本語の概要は準備中です。原文の説明を表示しています。
Main app ViewModel patterns (ScopedViewModel, Hilt, StateFlow, triggerEvent, navArgs, savedState flows, events). Use when writing, editing, exploring, debugging, or reviewing ViewModels in the store management app. Covers navArgs, combine+asLiveData, sealed state hierarchies, custom events, init blocks, and companion object placement. NOT for POS (WooPos*) code — use the `pos` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Main app unit testing patterns (BaseUnitTest, BDD naming, mockito-kotlin, AssertJ, StateFlow/LiveData capture, coroutine dispatchers). Use when writing, editing, exploring, debugging, or reviewing unit tests in the store management app. For POS (WooPos*) tests, use the `pos-tests` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
POS unit testing patterns (WooPosCoroutineTestRule, runTest, advanceUntilIdle, mockito-kotlin, event bus mocking, analytics verification). Use when writing, editing, exploring, debugging, or reviewing unit tests for POS (WooPos*) code. NOT for main store app tests — use the `store-tests` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Main app analytics tracking patterns (AnalyticsEvent enum, AnalyticsTrackerWrapper, KEY_*/VALUE_* constants). Use when writing, editing, exploring, debugging, or reviewing analytics tracking in the store management app. NOT for POS (WooPos*) code — use the `pos-analytics` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
POS analytics tracking patterns (WooPosAnalyticsEvent sealed class, WooPosAnalyticsTracker, WooPosAnalyticsEventConstant). Use when writing, editing, exploring, debugging, or reviewing analytics tracking in POS (WooPos*) code. NOT for main store app — use the `store-analytics` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Triage a raw, vague issue or bug report into a structured document that names what is known, what is missing, and what to do next. Use when an incoming issue, bug report, or problem description is too vague or incomplete for investigation or planning, and recommend the right next han skill. Does not investigate root causes or trace code paths — use investigate for debugging, diagnosis, and root cause analysis. Does not plan features or build solutions — use plan-a-feature or plan-implementation for that.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use code-review for auditing changes or post-code-review-to-pr for posting review feedback to GitHub. Does not assess architectural health or structural risk — use architectural-analysis for architectural concerns. Does not research open-ended options, prior art, or how something works when nothing is broken — use research for that. Does not plan the structural change a root cause calls for — use plan-a-change. Does not map bounded contexts or domain boundaries — use ddd-analysis. Does not capture feedback on Han's own skills — use han-feedback for that.
日本語の概要は準備中です。原文の説明を表示しています。
Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the resulting investigation report to a user-specified Confluence location. Use when the user wants something debugged, diagnosed, or root-caused AND the findings posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not investigate to a local file only — use investigate. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.
日本語の概要は準備中です。原文の説明を表示しています。
Instrument AI agents with tracing, token metrics, latency, and cost visibility. Use for reliability and debugging.
日本語の概要は準備中です。原文の説明を表示しています。
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
日本語の概要は準備中です。原文の説明を表示しています。