3,566 件 ・ 関連度順
概要と使いどころ
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me" outside an Odoo-specific context.
日本語の概要は準備中です。原文の説明を表示しています。
当用户纠结"要不要卖/换/止盈/止损"时激活。核心信号：用户用买入成本、浮盈浮亏、持仓时间作为卖出理由，或问"已经赚了X%该不该走"。也适用于纠结"持有A还是换B"的资产配置场景。不适用于：纯估值计算（交给 dcf-valuation）、判断公司好坏（交给 good-business）、情绪安抚（交给 equanimity-mindset）。本 skill 只解决一个问题——用机会成本统一买卖逻辑，消除"成本锚定"和"止盈止损"的伪决策。
日本語の概要は準備中です。原文の説明を表示しています。
Customer discovery framework using Jobs-To-Be-Done theory — uncover the functional, social, and emotional jobs customers hire products to do. Produces JTBD canvases with job statements, outcome metrics, and competing solutions. Use alongside cm-brainstorm-idea for evidence-based product decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Sync high-value dev knowledge (skills, decisions, lessons) into Google NotebookLM for cloud recall, podcasts, and flashcards. Pairs with Dockit/deep-search. Use for NotebookLM, nlm, knowledge base, skill sync, or cross-machine AI memory.
日本語の概要は準備中です。原文の説明を表示しています。
Keep Claude Code sessions grounded in prior decisions, project context, and daily handoff notes instead of starting from zero every time.
日本語の概要は準備中です。原文の説明を表示しています。
Expert pricing strategy and monetization guidance for SaaS and digital products. Use when designing pricing tiers, creating pricing pages, setting value metrics, developing bundle strategies, planning price increases, writing pricing copy, analyzing competitive pricing, or optimizing annual vs monthly positioning. Use for packaging decisions, discount policies, enterprise pricing, and behavioral pricing tactics.
日本語の概要は準備中です。原文の説明を表示しています。
Expert product strategist for vision, strategy, and market positioning. Use when defining product vision, assessing product-market fit, sizing market opportunities (TAM/SAM/SOM), competitive positioning, or choosing between build/buy/partner. Covers business model design, monetization strategy, platform decisions, and strategic roadmap planning.
日本語の概要は準備中です。原文の説明を表示しています。
CTO-level architectural advisor for AI-native development. Use this skill whenever you encounter code design decisions, architecture discussions, system resilience questions, or any work touching: "architecture", "design", "scale", "dependencies", "state", "failure", "blast radius", "refactor", "migrate", "optimize", "resilience", "consistency", "observability", "bottleneck", "coupling", "monolith", "microservices", "distributed", "concurrency", "data flow", "system design", or any prompt suggesting code-first thinking when design-first thinking is needed. This skill integrates with Claude Code to review generated code for architectural soundness, define design systems via design.md, and guide teams toward CTO-level thinking. Trigger aggressively on architectural questions—this is where AI adds the most leverage.
日本語の概要は準備中です。原文の説明を表示しています。
World-class practice research. This skill should be used when the user asks what the best in the world does about a specific problem, technique, or situation — covering product, engineering, design, marketing, compliance, operations, org design, and any other domain. Use when the goal is to understand elite-tier practice, not to make a strategic decision. Distinct from best-in-world-strategy, which is for choosing between options.
日本語の概要は準備中です。原文の説明を表示しています。
Proxy Cline CLI tasks: dispatch, monitor, relay decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a research-paper figure Skill Factory: build, patch, package, or use reusable specialized paper-figure-making skills from lawful literature/corpus evidence. Generated skills must use a specialized-skill-first workflow, full-feasible local PDF coverage where available, startup-plan-only first replies, target-paper candidate/final image isolation, mandatory image-embedded visual-structure explanation, mandatory non-target concept/modeling example display for abstract visual decisions, saved subtype/style illustration atlases, ChatGPT web Create image / ChatGPT Images 2.0 rendering, Codex $imagegen-first rendering, sample-image transfer rules, all-step/current-position state footers, and a mandatory first-round diverse candidate board followed by P6b/P6c paper-local best-practice optimization before final prompt construction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user has a meeting, call, 1:1, a person to meet, or a decision coming up and needs to walk in prepared. Assembles a one-page brief from context/, wiki/, connections, open loops, and the knowledge graph — who · what · goal · history · open loops · the ask · risks. Trigger on "/prep", "prep me for", "brief me on <person/meeting>", "what do I need to know before", "get me ready for".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture design skill: ADR records, system design checklists, scalability assessment, architecture patterns. Use for complex system design and architecture decisions.
日本語の概要は準備中です。原文の説明を表示しています。
用四步流程做出理性客观的决策：紧盯目标过滤小事→找第三选择突破选项限制→绕开认知偏误→量化打分做最终选择。适用于面临重大选择纠结不已、选项看似非此即彼、或担心被直觉误导的场景。不适用于日常低风险小决策（过度量化反而浪费时间）。关键触发信号："纠结选A还是B"、"不知道怎么选"、"两个都不满意但必须选一个"、"帮我做个决定"。
日本語の概要は準備中です。原文の説明を表示しています。
Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use before any research activity or significant decision. Reviews cognitive biases relevant to the current stage.
日本語の概要は準備中です。原文の説明を表示しています。
Render `.claude/diamonds/active.yml` as the decisions each diamond has recorded, in order, grouped by mode (discovery, delivery). Read-only. Default format Mermaid stateDiagram-v2, drawn by a script. Recommended at the end of `/mycelium:diamond-assess` so every assessment closes with a visual state-of-play. See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared render fleet conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.
日本語の概要は準備中です。原文の説明を表示しています。
Apply whenever writing or updating a project-facing document — root CLAUDE.md, `.hedgehog/core-design.md`, specs, READMEs, or similar. Ensures the file reads as a clean, current, as-is snapshot rather than a log of edits or decisions. Applies on first generation and on every later revision, including "update," "rewrite," or "clean up" requests.
日本語の概要は準備中です。原文の説明を表示しています。
Use at the start of any session on a project with a build graph (`.hedgehog/hedgehog.db`), and again at every claim/dispatch/verify cycle within it. Owns consuming the build graph — claiming task packets, delegating each to the layer's agent, running `hedgehog verify` to gate the commit, recording debt and decisions, the intent check at an intent's last layer, and when to clear context. Not for a build agent handed an already-claimed packet — that agent never claims, dispatches, or verifies; this skill is the orchestrating session's own.
日本語の概要は準備中です。原文の説明を表示しています。
Research a topic to support a decision, three ways: draft a research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), turn a finished research report into a short summary with cited sources that other skills can use directly, or run the research here with parallel web searches. Built-in research types: market, domain, technical, competitive, user-voice, academic-lit; also supports choosing between candidates, and custom types via overrides. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "literature review", or "help me choose between"
日本語の概要は準備中です。原文の説明を表示しています。
Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to flatter. Use to ideate, validate, scope, architect, or plan a product, feature, startup, or app before any code is written. Invoke by persona name or acronym to summon one expert, or with no argument to run the full lifecycle end to end.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct an adaptive interactive interview on any topic and produce a structured markdown report, summary, or implementation plan. Use when the user says "interview me", "interview me about", "run an interview on", "help me think through", or wants guided discovery on any subject. Also triggers on "talk me through", "explore X with me", "help me plan Y", or "walk me through my thinking on Z" when the user wants a guided conversation rather than a direct answer. Applies broadly — career decisions, project ideas, product direction, personal goals, research questions, team problems — not just technical topics.
日本語の概要は準備中です。原文の説明を表示しています。