「aces」の検索結果

Create original short videos using the 非对称突破｜密集阻力到空间制度改变 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 延迟转身惊变｜固定走廊、轮廓污染与贴镜突破 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 气闸异境｜物理异常后空间崩坏 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 跨媒介旅伴路线｜地标换章、同步动作与共同终姿 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 二维角色｜真人接触三级反应 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 手作角色扮演｜分工亮相、道具误伤与集体和解 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 景别收紧｜从世界到眼神 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 连续拉远尺度揭危｜小型载体、扩张暗区与临界停留 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Create original short videos using the 屏中蒙太奇｜外层连续内屏切换 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and safely repair cross-runtime Skill governance: canonical-source ownership, divergent or duplicate projections, exposure scopes and budgets, lifecycle drift, quarantine, and retirement. Use when the user explicitly requests cross-runtime or cross-scope Skill governance; ignore project-local Skill inventory, product/runtime loading or enablement checks, usage statistics, and mentions/traces.

日本語の概要は準備中です。原文の説明を表示しています。

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing organizational structure (team topologies, Conway's Law alignment), mapping stakeholders by power-interest for change initiatives, defining team interface contracts (APIs, SLAs, decision rights, handoffs), assessing capability maturity (DORA, CMMC, agile maturity models), planning org restructures (functional to product teams, platform teams, shared services), or when user mentions "org design", "team structure", "stakeholder map", "team interfaces", "capability maturity", "Conway's Law", or "RACI".

日本語の概要は準備中です。原文の説明を表示しています。

Search and discover Claude Code skills and MCP servers from marketplaces, GitHub repositories, and registries. Use when (1) user asks to find skills for a specific task, (2) looking for MCP servers to connect external tools, (3) user mentions "find skill", "search MCP", "discover tools", or "what skills exist for X", (4) before creating a custom skill to check if one already exists.

日本語の概要は準備中です。原文の説明を表示しています。

Design, implement, audit, or refactor web and game-adjacent interfaces using an evidence-based Hypergryph visual language with two independent choices: product family and application depth (1 minimal, 2 moderate, 3 complex, 4 maximal). Use for Hypergryph-, Arknights-, Endfield-, Rhodes Island-, industrial sci-fi-, editorial game-UI-, or bilingual technical-interface requests; for landing pages, dashboards, menus, HUD-like panels, design systems, HTML/CSS/JS/React components, and visual QA where the result should carry this family resemblance without copying protected logos or artwork.

日本語の概要は準備中です。原文の説明を表示しています。

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

日本語の概要は準備中です。原文の説明を表示しています。

Baserow integration. Manage Workspaces, Users, Roles. Use when the user wants to interact with Baserow data.

日本語の概要は準備中です。原文の説明を表示しています。

0codekit integration. Manage Workspaces. Use when the user wants to interact with 0codekit data.

日本語の概要は準備中です。原文の説明を表示しています。

Before removing code that looks redundant, wasteful, or "wrong" based on log observations or code review instinct, grep the test suite for tests whose names describe the exact behavior you're about to remove. A test whose title literally describes the "weird" thing (e.g. "calls play() even when player reports playing", "retries even when first call succeeded", "skips cache even when fresh") is a load-bearing workaround, and the production log you're reacting to is probably the workaround working as designed — not a bug. Use when: (1) Tempted to remove a function call that "looks redundant" based on a production log, (2) About to "simplify" a conditional that seems to always take the same branch, (3) Reviewing code and thinking "why would anyone write this?", (4) A log line shows a state that seems impossible or contradictory (e.g. playing=true but positionMs=0 for seconds), (5) CI surfaces a failing test whose name describes exactly what your fix removed.

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing conversational AI chat interfaces.

日本語の概要は準備中です。原文の説明を表示しています。

Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.

日本語の概要は準備中です。原文の説明を表示しています。

Create Chinese monospaced compass-style PDCA or CAPD problem-solving cards using East-West-South-North-Center layout, full-width and half-width spaces, diagonal Unicode arrows, and strict Chinese character limits. Use when Codex needs to turn a problem, incident, decision tradeoff, root-cause analysis, improvement cycle, or CAPD/PDCA workflow into a square text diagram, Hermes/Discord-ready card, or Chinese 方位九宮圖 with center ◎, north Plan, east Do, south Check, west Action, and four diagonal transition arrows.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze failing tests to detect functional bugs in code. Takes repository and failing test output as input, analyzes execution behavior, assertions, and stack traces to identify suspicious code regions and root causes. Use when debugging test failures, investigating regression bugs, or understanding why tests fail. Explains the bug mechanism, identifies affected code, and suggests fixes based on test expectations vs actual behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks. Use when you need to debug complex issues, reproduce test cases, prepare traces for formal verification, or analyze program execution. Supports manual instrumentation points, automatic function/method instrumentation, and conditional triggers. Outputs structured JSON snapshots for debugging, replay, and verification workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Explains runtime errors and compilation failures with actionable debugging guidance. Use when Python or Java code throws runtime exceptions (NullPointerException, TypeError, AttributeError, etc.), compilation errors (syntax errors, type mismatches, import failures), or dependency issues. Analyzes error messages, stack traces, and code context to identify root causes and provide concrete fixes with examples. Distinct from test-related errors - focuses on errors during normal code execution and build processes.

日本語の概要は準備中です。原文の説明を表示しています。