1,843 件 ・ 関連度順
概要と使いどころ
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.
日本語の概要は準備中です。原文の説明を表示しています。
Generate sprint-based development tasks from a PRD. Use when asked to create tasks or break down requirements. Don't use for PRD/TAD authoring or task execution.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate multi-agent swarms with agentic-flow for parallel task execution, dynamic topology, and intelligent coordination. Use when scaling beyond single agents, implementing complex workflows, or building distributed AI systems.
日本語の概要は準備中です。原文の説明を表示しています。
15-agent hierarchical mesh coordination for v3 implementation. Orchestrates parallel execution across security, core, and integration domains following 10 ADRs with 14-week timeline.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the practical, systems-level, and commercially-driven reasoning of Thomas Edison (founder of General Electric, inventor and industrialist). Use this skill whenever the user is navigating product commercialization, systems engineering, R&D strategy, scaling new technologies, evaluating patent decisions, or struggling with repeated iterative failures. Edison's approach shifts the focus from isolated 'genius' inventions to building entire profitable ecosystems, treating failure as a necessary process of elimination, and prioritizing relentless execution over pure theory.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
This skill applies the first-principles engineering and capital allocation frameworks of Elon Musk (CEO of Tesla and SpaceX, founder of X.com / PayPal). Reach for this skill whenever the user is facing complex manufacturing bottlenecks, evaluating existential risks, debating free speech vs. censorship, dealing with bureaucratic overregulation, or trying to accelerate ambitious technical timelines. It is highly effective for situations involving hardware production, AI symbiosis, radical innovation, and aggressive execution. Use this skill proactively when discussing multi-planetary expansion, government efficiency, or scaling prototypes to mass production, even if the user doesn't explicitly name him.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate cross-phase web execution/evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Suede-affiliated marketing ideation using a structured tactic library scored for stage, audience fit, evidence, capacity, cost, and risk. Use when the user is stuck, wants options, or needs a shortlist of growth tactics before committing to a plan. NOT FOR: a comprehensive roadmap (use suede-marketing-plan), channel execution (use the relevant public Suede skill), or unattended recurring workflows (use suede-marketing-loops).
日本語の概要は準備中です。原文の説明を表示しています。
Suede-affiliated comprehensive marketing planning across acquisition, activation, retention, referral, and revenue, sized to the actual team, budget, evidence, and stage. Use when the user needs a 90-day plan, 12-month roadmap, growth plan, or go-to-market operating document. NOT FOR: isolated channel execution (use the relevant public Suede skill), uncommitted tactic brainstorming (use suede-marketing-ideas), or positioning discovery alone (use suede-product-marketing).
日本語の概要は準備中です。原文の説明を表示しています。
Delegate tasks to specialized subagents for parallel or sequential execution.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate unexpected behavior and mysterious bugs. Use when the cause of a problem is unknown and the user needs to understand WHY something is happening — symptoms like: sudden unexplained changes in metrics or behavior, works locally but not in staging/production, inconsistent or intermittent failures, correct code producing wrong results, operations succeeding but having no effect, environment-specific failures, duplicate executions, stale data, or any "why did this change?" or "why is this happening?" situation. Covers infrastructure anomalies (cache hit rates dropping, latency spikes, queue behavior shifts) as well as code bugs. The key signal is confusion about root cause, not a request to implement a known fix. Do NOT use for feature requests, known fixes, planning, or documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
CRE Asset Management analysis suite — 9 specialist skills for post-acquisition multifamily operations including annual budgeting, monthly variance analysis, rent collection, renewal decisions, lease-up tracking, capex execution, NOI improvement, hold/sell/refi scenario analysis, and quarterly asset review memos.
日本語の概要は準備中です。原文の説明を表示しています。
Develop a limit-based product strategy with convergence milestones, acceleration levers, assumptions, and phased execution.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses and fixes slow Neo4j Cypher queries by reading execution plans, identifying bad operators (AllNodesScan, CartesianProduct, Eager, NodeByLabelScan), and prescribing fixes (indexes, hints, query rewrites, runtime selection). Use when a query is slow, when EXPLAIN or PROFILE output needs interpretation, when dbHits or pageCacheHitRatio are poor, when cardinality estimation diverges from actuals, or when deciding between slotted/pipelined/parallel runtimes. Covers USING INDEX / USING SCAN / USING JOIN hints, db.stats.retrieve, SHOW QUERIES, SHOW TRANSACTIONS, TERMINATE TRANSACTION. Does NOT write new Cypher from scratch — use neo4j-cypher-skill. Does NOT cover GDS algorithm tuning — use neo4j-gds-skill. Does NOT cover index/constraint creation syntax details — use neo4j-cypher-skill references/indexes.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Unreal's Gameplay Ability System - when GAS is worth it, where the AbilitySystemComponent lives and how it is initialised on server and client, AttributeSets with correct clamping and replication, GameplayEffects and execution calculations as data, abilities with commit/end, gameplay tags, prediction, and testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an editor MCP server (unity, godot, unreal, blender) or the browser MCP shows up in your tool list - what each one can observe or change, how to check it is attached to YOUR task workspace, why the repo's tests still decide, the Blender code-execution caution, and the headless fallback when none is connected.
日本語の概要は準備中です。原文の説明を表示しています。
Use when dataframe code is slow or runs out of memory, when data outgrows pandas, or when writing pandas 3, Polars or DuckDB code — vectorisation, dtypes, Copy-on-Write, lazy and out-of-core execution, and measuring before and after
日本語の概要は準備中です。原文の説明を表示しています。
Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a need_revision bounce.
日本語の概要は準備中です。原文の説明を表示しています。
Phase C of a WinForms-to-Avalonia migration: implement platform and infrastructure adapters for dependencies discovered in Phase A/B, such as persistence, process execution, dialogs, notifications, or environment capabilities. Use only in an explicit migration when such dependencies leak into Forms/core or when the orchestrator routes here. Do not invent adapters for capabilities the product does not have, and do not implement main-window XAML.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically notify the user when long-running terminal commands finish (npm test, docker build, git push, etc.). The agent monitors command execution and sends a desktop notification on completion if the command ran longer than threshold (default 10s). Use when user asks to "notify me when done", "desktop notification when command finishes", "alert when done", or "tell me when this completes". Do NOT use for interactive commands (vim, nano, less, htop), commands that always complete in <5s, or streaming commands (tail -f).
日本語の概要は準備中です。原文の説明を表示しています。
Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to "evaluate design slop", "slop report", "is this design AI slop", "audit this landing page design", "de-slop review", or wants an objective score of how generic/machine-made a design looks. To fix text (not design), use human-ai or humanizar skills instead.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive marketing expertise combining campaign execution, strategy frameworks, psychological principles, and 140+ marketing tactics. Use when planning campaigns, developing content strategy, applying behavioral science, generating marketing ideas, or building go-to-market strategies. Covers email, social, SEO, paid ads, content, and psychology-driven optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive sales and revenue operations skill. Use when building a sales team, doing founder-led sales, hiring first sales reps, navigating enterprise deals, implementing product-led sales, designing sales compensation plans, defining ICP, mapping buyer personas, or optimizing the revenue engine (RevOps). Activates for: sales strategy, rev ops, revenue operations, sales enablement, sales compensation, ICP, ideal customer profile, buyer persona, sales process, deal execution, lead scoring, lead routing, lead lifecycle, MQL, SQL, pipeline management, CRM automation, sales qualification, BANT, MEDDIC, founder sales, enterprise sales, product-led sales, startup sales, SDR, AE, quota, ramp, commission plan.
日本語の概要は準備中です。原文の説明を表示しています。