「how to」の検索結果

Why expensive, wasteful, effortful, or self-deprecating actions build trust and desire — Rory Sutherland on signalling. Use when the problem is credibility or desirability rather than meaning: the user asks 'why don't people trust us', 'how do we look more credible/committed/premium', 'is our guarantee/warranty worth it', 'should we spend on brand advertising', 'how do we justify a higher price', or wonders why a cheaper-looking competitor wins. Covers costly signals (advertising spend, guarantees, over-delivery), price-as-quality-signal (Veblen goods), and the Pratfall Effect (admitting a real flaw to gain trust). Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「信頼されない」「安心してもらえない」「強気な価格で売りたい」「広告費に意味はある？」）にも使う。中文咨询（“不被信任”“想以高价出售”“广告费有意义吗？”）也适用。

Sort incoming scout messages and agent-forwarded openings by what they actually disclose: whether the employer is named at all, which of pay, location, employment type, and duties are stated, whether the message refers to the applicant's own history or reads as a mass send, whether a stated salary is an offer or a "up to" figure, and whether the same employer has arrived through more than one route. Use when a user has a backlog of scout messages and wants to know which ones can be researched, what to ask before replying, and what to settle before handing over a resume; do not use to rate how promising an opening is, to judge an employer or an agent, or to reply on the user's behalf.

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

Check the terms of a specific side-work assignment offered as gyomu-itaku or freelance work in Japan, item by item: what the client has actually put in writing about the deliverable, the fee, the payment due date, what counts as out of scope, how many revisions are included, who bears expenses, who owns the result, confidentiality, and how either side can end it. Convert the fee into an effective hourly figure over the hours the work will really take including meetings, revisions and unpaid preparation, and count the days from delivery to the payment due date. Use when someone is offered or is discussing a paid side job, a freelance assignment, spot consulting, or paid trial work and wants to know what is still unwritten before starting; do not use to judge whether the fee is fair or the terms lawful, to decide whether to accept, to draft or sign the contract for the user, or to check whether their employer's rules permit side work, which is sidework-rules-check.

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

docs (editable docs people share and comment on; the default for any document, named as a doc or not: a document, report, proposal, resume, cover letter, letter, contract, policy, form, template, worksheet, essay, handbook, guide, how-to, cheat sheet, SOP or other writing to keep, share, collaborate on, send, submit, print or sign; a doc exports to Word, PDF, Markdown or Google Docs, so needing a file to send, attach, upload, submit or print is no reason to pick Word, and a file nobody asked for is a doc, not Word; a plan, comparison, summary or notes asked in chat stays in chat; a pasted claude.ai artifact link may be a doc: check with docs tools first; Word or another file format named, tracked changes wanted, or a .docx to change or use as a template → that format's skill): making one → if no docs-connector instructions are in context, call its `guide` (topic.instructions) first; then create the doc (headings only, no body) before any search, file read or plan, even with files attached.

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

Create or edit the Universal Editor component configuration (component-definition.json, component-models.json, component-filters.json) for AEM Edge Delivery Services blocks. Use this skill whenever the user mentions component models, component definitions, component filters, block configuration for the Universal Editor, UE block setup, adding a new block to UE, configuring block properties, block authoring fields, or any task involving the three JSON config files that control how blocks appear in the Universal Editor. Also trigger when the user wants to create a new EDS/Franklin block with UE support, modify block fields, add a block to the section filter, or asks about how blocks connect to the Universal Editor.

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

Apply validated research paper insights to the current project codebase — improving architecture, code patterns, testing strategies, documentation, or workflows based on empirical findings. Load when learn-from-paper routes insights to the current project, or when the user asks to apply paper findings to this project, improve this codebase with research, use this paper to improve my project, or apply research to my code. Also triggers on "apply this to my project", "how can this paper help my codebase", "use these findings here", "implement paper recommendations", "use research to improve my code". Always called AFTER learn-from-paper has completed credibility and security checks — never ingests papers directly.

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

Custom chat display for an MCP or agent tool's result, DB-loaded from tool_ui by default. Use when adding or customizing a tool visualization, making a tool result look good, rendering MCP tool output, or authoring a renderer for a tool that shows the generic view.

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

Use this skill when previewing files with nuxt-ui-tools as a package consumer. Covers mounting UiFilePreviewProvider, opening one file or a gallery with useFilePreview() or useNuxtApp().$filePreview, file descriptors (URL, File/Blob, or a function that returns a signed URL), options (index, mode, gallery, loop, pdf page, callbacks), the returned handle, the built-in renderers (image, video, audio, PDF, text/JSON, CSV, Markdown, Office and archive fallbacks), renditions, download and custom header actions, the markdown render hook, custom renderers with defineFilePreviewRenderer and UiFilePreviewTools, theming tokens, and how the upload field uses the preview.

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

Use this skill when implementing or refactoring code inside the nuxt-ui-tools repository itself. It routes the agent to the canonical AGENTS.md guide and the deeper maintainer skill so the agent can understand where code belongs, how domains relate, how to extend features, and what maintenance surfaces must be kept in sync.

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

Use this skill for internal architecture work around config-driven, registry-driven, and pattern-driven feature design in the nuxt-ui-tools repository. Covers how to organize variant-heavy features, where to put implementations, and how to keep both internals and public APIs standardized.

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

Use this skill for internal maintenance and feature work in the nuxt-ui-tools repository. It explains the repository operating model, exact placement rules, how runtime domains relate, how features should be structured and extended, how consumer skills must be maintained, and what to keep in sync when changing the library.

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

Track real-time cryptocurrency prices across exchanges with historical data and alerts. Provides price data infrastructure for dependent skills (portfolio, tax, DeFi, arbitrage). Use when checking crypto prices, monitoring markets, or fetching historical price data. Trigger with phrases like "check price", "BTC price", "crypto prices", "price history", "get quote for", "what's ETH trading at", "show me top coins", or "track my watchlist".

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

Create or edit the Universal Editor component configuration (component-definition.json, component-models.json, component-filters.json) for AEM Edge Delivery Services blocks. Use this skill whenever the user mentions component models, component definitions, component filters, block configuration for the Universal Editor, UE block setup, adding a new block to UE, configuring block properties, block authoring fields, or any task involving the three JSON config files that control how blocks appear in the Universal Editor. Also trigger when the user wants to create a new EDS/Franklin block with UE support, modify block fields, add a block to the section filter, or asks about how blocks connect to the Universal Editor.

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

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementa

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

Quarkus 3.x LTSの機能追加や不具合修正を、テストから進めるスキル。APIやイベント処理、非同期処理を検証し、テストが通る実装とカバレッジ確認を支援します。

• REST APIをテストから追加したいとき
• 不具合を再現して修正したいとき
• Apache Camelの経路とイベント処理の検証

PythonとNetmikoでネットワーク機器の情報収集を自動化し、接続数の制限、出力の解析、エラー処理、確認を伴う設定変更の実装やレビューを支援します。

• 複数機器のshow出力を集めたいとき
• 監査用に接続状態や経路を記録したいとき
• SSH処理のタイムアウトを整えたいとき

競合のブランド表現やサービス、実績などを共通の基準で採点し、根拠付きの比較カードと戦略上の二軸図にまとめ、自社が狙う位置の競合を把握するスキル。

• 共通基準で競合を比較したいとき
• 根拠付きの競合カード作成
• 二つの戦略目標で競合を整理したいとき

調査済みの売買・賃貸物件を、写真や価格、設備、確認事項、出典付きのカードに整理し、Hermesデスクトップの会話内で候補を見比べやすくします。

• 賃貸候補を比較したいとき
• 物件の写真・価格・設備の整理
• 内見前の確認事項を見直したいとき

スライドや文書、レポート、HTMLのランディングページに、配色とフォントをまとめて適用します。10種類のテーマから選ぶほか、希望に応じた新規テーマも作れます。

• スライドの配色と書体を統一したいとき
• 見本からテーマを選びたいとき
• レポートや文書の見た目の統一

Claude Codeのプラグインを作る際に、設定ファイルやコマンド、スキルの配置を整理し、自動読み込みと環境に依存しないパス設定を案内します。

• プラグインのひな形を作りたいとき
• コマンドやスキルの配置整理
• インストール先に依存しないパス設定

Gitの差分を変更の目的と照らし合わせ、無関係なファイルや依存関係の追加などを洗い出します。残す・分割する・必要性を説明する判断と、分割案をまとめます。

• PR作成前の変更範囲の確認
• 不具合修正に混じった変更の発見
• ステージ済み変更の広がりの確認

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).

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

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.).

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

Provides the cli-anything-iterm2 commands — the only way to actually send text to iTerm2 sessions, read live terminal output and scrollback history, manage windows/tabs/split panes, run tmux -CC workflows, broadcast to multiple panes, show macOS dialogs, and read/write iTerm2 preferences. Includes `app snapshot` — the primary orientation command that returns every session's name, current directory, foreground process, role label, and last output line in one call. Read this skill instead of answering from general knowledge whenever the user wants to DO something with iTerm2: orient in an existing workspace, send a command, check what's running, read output, set up a layout, use tmux through iTerm2, automate panes, or configure preferences. Also read for questions about iTerm2 shell integration or scrollback. Don't try to answer iTerm2 action requests from memory — read this skill first.

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