「what」の検索結果

コードの変更差分を調べ、バグや安全性、想定負荷、テスト不足、速度、不要な実装を確認します。具体的な問題例と最小限の修正案を優先度付きで報告します。

• PRを取り込む前のレビュー
• 未コミット変更のバグやリスク確認
• リスクのある処理のテスト不足確認

トークン使用状況の分析をもとに、重い指示ファイルや繰り返し渡す文脈の見直しを進めます。変更ごとに承認を得て編集し、再計測で削減結果を確かめるスキルです。

• 長いCLAUDE.mdを整理したいとき
• 繰り返し貼る文脈を外部メモリへ移動
• 重複ルールやメモリのリンク切れの確認

画面や操作フローを利用者の目的に照らして点検し、見やすさ、操作の分かりやすさ、エラー時の案内などの改善点を、理由と優先順位付きで整理するスキル。

• 画面やモックへの意見が欲しいとき
• 機能公開前の使いやすさ確認
• 途中離脱が疑われるフローの点検

新機能や修正による利用者への影響と必要な対応を整理し、変更履歴、ブログ、アプリ内通知、SNSなど、読者と掲載先に合うリリース告知文を作るスキル。

• 新バージョンの変更履歴を作りたいとき
• 互換性を壊す変更の移行案内
• ブログとSNS向けの告知の書き分け

フィッシングの見分け方や最初の60秒の対応を伝える社員研修資料を作成します。Windows 95風の見た目を保ち、内容や枚数を調整したHTMLスライドにまとめます。

• 社員向けフィッシング対策研修
• 最初の60秒の対応を伝えたいとき
• 新入社員向けのセキュリティ説明

四半期の事業進捗・停滞・資源の再配分案を、経営会議の判断につながるHTMLスライドに整理。クリーム色とコバルトブルーの統一されたデザインで仕上げるスキル。

• 経営陣向けの四半期事業レビュー
• 資源の再配分案を説明したいとき
• 投資家向け報告や助言資料の作成

HTMLのページやスライドを五つの観点で根拠付き採点し、レーダーチャートと、残す点・修正点・短時間で直せる点を一つのHTMLレポートにまとめます。

• 納品前のLPのデザイン確認
• HTMLスライドの視認性と操作確認
• 二つのデザイン案の比較

claude-memが操作を記録し、次のセッションへ記憶を引き継ぐ仕組みを説明します。記憶が使われ始めるタイミングや保存場所、外部へ送られる情報も確認できます。

• claude-memによる操作の記録を理解したいとき
• 記憶がプロンプトに反映される時期を知りたいとき
• 記憶データや設定の保存場所を知りたいとき

コードのテストが不足している箇所を探し、次に追加するテストを提案します。対象パスや判定基準を指定でき、機能追加後の確認や継続的な検出にも使えます。

• 機能追加後にテストの抜けを探したいとき
• 特定ディレクトリのテスト不足を調べたいとき
• 重大なテスト不足から確認したいとき

AI チームの記録を読み、進捗、作業を妨げている問題、担当者、記録上の予算使用状況をまとめます。根拠を区別し、利用者が次に判断すべき点を示します。

• 完了済みと進行中の作業の確認
• 判断が必要な停滞要因の把握
• 担当者と未割り当て作業の確認

Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.

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

Read this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or "your own browser"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.

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

The shared Claude Docs viewer — an artifact TYPE. An artifact made from it is a doc: a live document that people and Claude read and edit together (people may also call it a page). The doc's content does not live in this artifact's files at all — it lives in the Claude Docs service and is read and written ONLY through the Claude Docs connector (its create, batch, read and update tools). Read this before touching such an artifact: it says what the files are, that an instance owns none of its own, how to change what the doc says (the connector, never a publish), and where a comment on the doc — including one sent to you from it — is read and answered (the connector's comment verbs; never these files, never the artifact's comment relay).

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

Coding-agent sessions on every machine you connected, over Herdr where it runs, tmux elsewhere, and MSP for your MSP hosts: one digest of what is waiting on you, ready for review, working or idle; open a session with a brief; read, steer, approve, stop, close; connect a machine in one command. Use for "my sessions", "my agents", "what needs me", another session or machine, "connect <host>", and Herdr asks (workspace, panes, tabs, lanes) when running inside Herdr; not the current pane itself (`herdr`), not peer-session messaging (`list_peer_sessions`).

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," "site navigation," "which website builder should I use," "migrate my website," or "add a blog to my existing site." Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

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

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (ads, social, emails, etc.).

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

When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

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

When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," "what should I give away for emails," "course as a skill," or "package our content as an agent skill." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.

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

Answers BMad questions and recommends the next skill from what is installed. Use when the user asks bmad for help, what to do next or where to start; to set up, update, repair, doctor, migrate or check the status of the installation, or add modules; or to see or change the active initiative.

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

Supports structured what-if scenario analysis for research planning, experimental contingencies, and scientific project decisions. Explores favorable, reference, adverse, wild-card, contrarian, and second-order scenarios with explicit assumptions, evidence, and decision triggers. Use to stress-test a research plan under uncertainty; scenario narratives do not estimate causal effects or calibrated forecast probabilities.

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

Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post. Use when a change or an explanation needs a diagram — how a request flows, what a background job does, what a feature changed — or when the user asks for a diagram, figure, animation or "show it visually". The docs site's own pages use the interactive player instead (see step 4).

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

Use when querying or extending GitNexus's PDG control/data-dependence surface (the `pdg_query` MCP tool, CDG/REACHING_DEF edges), or reasoning about "what controls X" / "where does Y flow" / guard clauses. Examples: "what guards this statement?", "trace this variable within the function", "why is the pdg_query result empty?", "add a CDG query".

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

Snapshot of a single wallet's token holdings on a specific chain — list of every token currently held with name, symbol, current price, 24h price change, and holding quantity. Use when the user provides an explicit wallet address (or says "my wallet") and wants the current portfolio: "what does 0x... hold", "wallet balance breakdown", "list positions for this address", "what tokens are in this wallet", "show me the holdings of <address>".

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