769 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute effective sprints using Agile methodologies. Define sprint goals, estimate user stories, manage sprint backlog, and facilitate daily standups to maximize team productivity and deliver value incrementally.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning with fixed deadline or target outcome, working backward from future goal to present, defining milestones and dependencies, mapping critical path, identifying what must happen when, planning product launches with hard dates, multi-year strategic roadmaps, event planning, transformation initiatives, or when user mentions "backcast", "work backward from", "reverse planning", "we need to launch by", "target date is", or "what needs to happen to reach".
日本語の概要は準備中です。原文の説明を表示しています。
Create detailed buyer personas and Ideal Customer Profiles (ICP) for B2B and B2C marketing. Generates comprehensive profiles with demographics, psychographics, pain points, goals, objections, and messaging strategies. Use when defining target audience, creating ICP, or developing customer profiles.
日本語の概要は準備中です。原文の説明を表示しています。
Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.
日本語の概要は準備中です。原文の説明を表示しています。
Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a module boundary — through a discovery pass, an options document with one recommendation, a question round, and an adversarial validation round, with every element of the contract justified from one stated goal. Use when you want to design, shape, decide, or nail down an interface, contract, signature, or API change for a capability you can already describe, sized for roughly one pull request. Produces a design document and changes no code. Does not specify what a feature should do — use plan-a-feature. Does not plan delivery or sequencing — use plan-implementation. Does not assess the architecture of existing code — use architectural-analysis. Does not write the code — use tdd. Does not restructure existing code — use refactor. Runs its rounds without pausing for review; to review each round as it lands, use pairing.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes an existing codebase using strategic Domain-Driven Design to discover bounded contexts, surface ubiquitous language and semantic collisions, find places where code boundaries diverge from domain boundaries, and produce an evidence-backed domain and context map. Use when the goal is DDD-specific: bounded context discovery, ubiquitous language analysis, domain model discovery, or mapping contested ownership and responsibility. The entire repository is a valid scope; no module or directory must be named first. Does not assess architectural coupling, cohesion, or technical debt — use architectural-analysis. Does not design service communication, integration patterns, or deployment topology — use architectural-analysis or plan-a-feature. Does not refactor code, diagnose bugs, or review code quality — use refactor, investigate, or code-review.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the reasoning, principles, and frameworks of Jürgen Schmidhuber (LSTM co-inventor and deep learning pioneer). Reach for this skill whenever tackling problems involving sequence learning, artificial curiosity, intrinsic motivation, reinforcement learning architectures, or predicting long-term technological and cosmic evolution. Use this when discussing AGI timelines, the history and attribution of AI breakthroughs, data compression as learning, or when designing autonomous agents that must set their own goals. Trigger this skill for topics like recurrent neural networks, algorithmic information theory, open-source AI democratization, and evaluating true existential risks versus media hype.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the reasoning, principles, and mental models of Sebastian Thrun (robotics and self-driving cars pioneer, founder of Google X, Waymo, Udacity, Stanford University). Reach for this skill whenever Claude is asked to advise on hardware/software systems engineering, autonomous vehicles, moonshot ideation, probabilistic robotics (SLAM), or leading high-stakes engineering teams. Trigger this skill for discussions on democratizing education, regulating AI, transitioning from academic research to product development, or managing technical teams with empathy. Use it to shift focus from incremental component debates to end-to-end execution and audacious goals.
日本語の概要は準備中です。原文の説明を表示しています。
Assembla integration. Manage Organizations, Leads, Deals, Pipelines, Users, Goals and more. Use when the user wants to interact with Assembla data.
日本語の概要は準備中です。原文の説明を表示しています。
API Ninjas integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with API Ninjas data.
日本語の概要は準備中です。原文の説明を表示しています。
Apiary integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Apiary data.
日本語の概要は準備中です。原文の説明を表示しています。
Apex 27 integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Apex 27 data.
日本語の概要は準備中です。原文の説明を表示しています。
Agiled integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Agiled data.
日本語の概要は準備中です。原文の説明を表示しています。
AgencyZoom integration. Manage Organizations, Leads, Users, Goals, Filters. Use when the user wants to interact with AgencyZoom data.
日本語の概要は準備中です。原文の説明を表示しています。
Accelo integration. Manage Organizations, Leads, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Accelo data.
日本語の概要は準備中です。原文の説明を表示しています。
ActiveCampaign integration. Manage Users, Organizations, Leads, Projects, Goals, Filters. Use when the user wants to interact with ActiveCampaign data.
日本語の概要は準備中です。原文の説明を表示しています。
Discover and integrate RuV Stack projects when the user asks where to begin with ruvnet, which RuV tools fit a goal, or how the stack fits together.
日本語の概要は準備中です。原文の説明を表示しています。
Extract exactly 8 context-sensitive keywords from Chinese, English, or mixed text and turn them into a distributed weighted Graph View with no center goal node. Use when Codex needs keyword extraction, blacklist filtering, co-occurrence edges, node definitions/notes, weighted graph JSON, or an online Graph View tool for text analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and explain why Isabelle or Coq proofs fail, identifying the root cause such as type mismatches, missing assumptions, incorrect goals, unification failures, or inapplicable tactics. Use when the user encounters proof failures, error messages in formal verification, stuck proof states, or asks why their Isabelle/Coq proof doesn't work.
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured proof skeletons with tactics, strategies, and intermediate lemmas for theorems in Isabelle/HOL or Coq. Use when users need to: (1) Create proof outlines for theorem statements, (2) Generate proof structure with tactic placeholders, (3) Identify key lemmas needed for a proof, (4) Plan proof strategies (induction, case analysis, forward/backward reasoning), (5) Scaffold proofs with intermediate steps and subgoals, or (6) Convert theorem statements into detailed proof templates. Supports both Isabelle/HOL and Coq equally.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze failed or stuck proofs and propose auxiliary lemmas to help complete the proof in Isabelle/HOL or Coq. Use when encountering proof failures, stuck proof states, unprovable subgoals, or when needing to strengthen induction hypotheses. Identifies missing lemmas, suggests proof strategies, and generates helper lemmas with appropriate statements and proof sketches. Supports inductive proofs, case analysis, rewriting, and complex proof obligations.
日本語の概要は準備中です。原文の説明を表示しています。
Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.
日本語の概要は準備中です。原文の説明を表示しています。
ACTIVATE when building executive dashboards, tracking business metrics, creating executive scorecards, monitoring organizational KPIs, setting up health metrics, building dashboards for real-time monitoring, or establishing systems to track and measure business performance. Critical for any executive who needs to monitor company health, make data-driven decisions, or track progress toward strategic goals.
日本語の概要は準備中です。原文の説明を表示しています。