1,215 件 ・ 関連度順
概要と使いどころ
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Add a Jev-powered decision and release gate after an office assistant generates a report, proposal, spreadsheet, document, or slide deck. Use for claim-to-evidence checks, narrow requirement decisions, risk triage, and human-review routing; do not use it to generate the deliverable or claim that Jev browsed or verified a URL.
日本語の概要は準備中です。原文の説明を表示しています。
Create and composite HeyGen digital-human videos in the content workspace. Use whenever the user asks for a 数字人, 数字人5, HeyGen, AI 口播人物, 数字人小窗, 圆形头像口播, full-screen digital human, or asks to make a video that uses the existing avatar. Enforce Creator-plan CLI OAuth, the configured Digital Twin, local IndexTTS2 narration, Avatar III for an unspecified digital human but Avatar V whenever the named preset 数字人5 is requested, adaptive face measurement plus the approved human-reviewed visual-centering offset in the headroom_08 circular bottom-left layout unless full-screen is explicitly requested, subtitle-safe placement, credit-aware master reuse, final QC/archive routing, and mandatory pairing with `heygen-avatar-motion` before any motion prompt or paid generation.
日本語の概要は準備中です。原文の説明を表示しています。
dontbesilent 商业工具箱主入口。双模式：任务前路由（你的问题该用哪个 skill）+ 任务后导航（刚做完诊断，下一步该干什么）。 触发方式：/dbs、/商业、「帮我看看」、「下一步怎么走」 Main entry point for dontbesilent business toolkit. Dual mode: pre-task routing + post-task navigation. Trigger: /dbs, "help me with my business", "what's next"
日本語の概要は準備中です。原文の説明を表示しています。
Use before routing a /meta-agent request to choose single-agent-creator, team-builder, or agentlas-packager from the user's wording and available files.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding Memory Events, Memory Tickets, memory-map.json, vault-references.json, PM Soul memory ownership, or Memory Curator routing to an agent repo.
日本語の概要は準備中です。原文の説明を表示しています。
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
日本語の概要は準備中です。原文の説明を表示しています。
Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI implementation to find typography, overflow, responsive, routing, data-viz, browser-output, or native-shell defects, or to compare a render against a reference. Not for greenfield UI design (use ui-designer) or QA-program setup (use qa-expert).
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting a turn or checking Aegis skill routing.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update OMA skills in the SSL-lite human-readable format. Use when adding a new `.agents/skills/{skill-name}/SKILL.md`, converting an existing skill to the standardized Scheduling / Structural Flow / Logical Operations / References structure, or validating whether a skill has enough routing, execution, resource, and safety detail.
日本語の概要は準備中です。原文の説明を表示しています。
Create or revise OMA skills and their references. Use for skill routing, execution contracts, conditional loading, and authoring validation.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis. Uses context-aware methods such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, CBAM-style prioritization, and ADR-style decision records.
日本語の概要は準備中です。原文の説明を表示しています。
Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.
日本語の概要は準備中です。原文の説明を表示しています。
Use only after explicit Codex `$superloopy:superloopy-frontend` or Claude Code `/superloopy:superloopy-frontend` invocation for supported screen-based application UI across browser-hosted Web, interactive deployed content-led Web, desktop, mobile/tablet, embedded/hybrid, Qt, custom-rendered, or mixed targets, such a task started with a leading `loopy` or `루피`, or an active Superloopy loop explicitly routing it here. Do not activate from UI, frontend, desktop, mobile, or framework vocabulary alone, or for TV, wearable, XR, automotive, game UI, TUI, static media/document artifacts, or non-UI work.
日本語の概要は準備中です。原文の説明を表示しています。
Use only after explicit Codex `$superloopy:superloopy-research` or Claude Code `/superloopy:superloopy-research` invocation, a research task started with a leading `loopy` or `루피` (such as `loopy research`), or an active Superloopy loop explicitly routing a research deliverable here. Evidence-backed Superloopy research orchestration with automatic advisory usage targets, parallel read-only lanes, per-retrieval verdicts, graded and dated sources, empirical verification, a priced claim ledger, cited synthesis, and optional reports. Do not activate from research, investigate, look-up, summarize, deep-dive, report, or similar vocabulary alone, in any language; ordinary questions, debugging, and implementation context-gathering stay with their primary workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate coding agents through AMQ. Use for agent messages, inboxes, receipts, sessions, wake delivery, cross-project routing, managed launches, or AMQ diagnostics. Use amq-spec for collaborative design; do not use this for general message queues or single-agent work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reading, editing, or generating a Bethesda Game Studio load-order file (plugins.txt / loadorder.txt) for Fallout 4, Skyrim SE/AE/VR, Fallout 76, Starfield, or when launching xEdit with a custom plugin list. Authoritative reference for the asterisk-prefix format, official masters detection, ESL handling, and the routing rules between plugins.txt editing and xEdit daemon commands.
日本語の概要は準備中です。原文の説明を表示しています。
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first content changes, validation, cleanup proof, or durable workflow rules. Best when agents must prove the actual folder/module/scene/prefab/runtime owner before editing, especially runtime UI, generated assets, code graphs, tutorial/state flows, guided selection/action flows, overlay/dim source-bound mistakes, coordinate conversions, focus/highlight/marker/HUD alignment, predictive lead aiming, ballistic trajectories, spatial IoU verification, or repeated "fix still not visible" failures.
日本語の概要は準備中です。原文の説明を表示しています。
INVOKE THIS SKILL when your Deep Agent needs memory, persistence, or filesystem access. Covers StateBackend (ephemeral), StoreBackend (persistent), FilesystemMiddleware, and CompositeBackend for routing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding which English agriculture / environment / earth-science journal skill to invoke next, comparing fit across the 30-journal agriculture-and-environment roadmap, or routing a manuscript before venue-specific re-framing. Routes by sub-field (agronomy / plant / soil / food / environment / earth / climate), contribution type, and evidence shape (field trial / lab assay / observational survey / model / dataset).
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding whether a project is a genuine ACM MM (ACM Multimedia) contribution rather than single-modality work, choosing a thematic area, and routing between ACM MM, CVPR/ICCV, ACL/EMNLP, ICMR, MMSys, NeurIPS/ICLR, and the ACM TOMM journal by finding the cross-modal or media-systems core of the contribution.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reasoning about the ACM MM (ACM Multimedia) review pipeline — thematic-area routing to reviewers and area chairs, the OpenReview double-blind process and its single-blind track exceptions, the optional anonymous rebuttal, the meta-review and decision, and the oral/poster and award tiers, and where an author actually has leverage.
日本語の概要は準備中です。原文の説明を表示しています。
Owns Fabric Eventstream items end to end: sources, operators, destinations, routing, retention, throughput and connection strings, plus read-only topology checks. Pick it for anything that names an Eventstream, creating and listing included. Where the rows finally land is eventhouse-cli.
日本語の概要は準備中です。原文の説明を表示しています。