「how to」の検索結果

The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.

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

Assess and improve cloud portability — identify lock-in, prioritize abstraction, and design migration paths. Use when asked "how locked in are we", "reduce vendor lock-in", or "plan a cloud migration".

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

Audit existing resilience — identify untested failure modes and chaos engineering gaps. Use when asked "how resilient are we", "what failure modes are untested", or "find our chaos engineering gaps".

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

Jurisdiction comparison for a legal requirement or contract clause. Use when asked "how does this differ by jurisdiction", "compare GDPR and CCPA on this", or "run a state law comparison".

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

Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.

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

Survey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues. Use when asked "how accessible is our codebase", "find accessibility debt", or "where are our a11y gaps".

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

Call datagrok_show_entities after any MCP tool result that returns entity data (files, scripts, queries, connections, projects, spaces, groups, users). Always use the tool — never list entities as plain text, markdown links, or bullet lists.

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

Following what organisms do — behavior, metamorphosis, host-plant relationships, social dynamics, and the long-form ethograms that reveal how species actually live. Covers the vocabulary of ethology, the structure of a life cycle, the classic categories of species interaction, the discipline of recording behavior without premature interpretation, and the gap between a single observation and a statistically useful record. Use when the task is to understand or record what a species does rather than what it is.

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

Vygotsky's Zone of Proximal Development and scaffolding as a working framework for learning support. Covers the ZPD definition, the distinction between independent and assisted performance, the six scaffolding functions (recruitment, reduction in degrees of freedom, direction maintenance, marking critical features, frustration control, demonstration), fading, sociocultural mediation, and the relationship between ZPD and deliberate practice. Use when deciding how much help to give, designing collaborative learning, or assessing a learner's ceiling rather than just their current floor.

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

Media literacy and critical analysis of media messages across platforms and formats. Covers media ecology (McLuhan), encoding/decoding (Hall), news literacy, digital media analysis, propaganda techniques, algorithmic curation, visual rhetoric, and ethical media consumption. Use when analyzing media messages, evaluating news sources, understanding how media technology shapes communication, detecting propaganda, or studying the relationship between medium and message.

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

Stellar structure and life cycles from birth to endpoint. Covers the Hertzsprung-Russell diagram, hydrostatic equilibrium, main-sequence physics and the mass-luminosity relation, nuclear fusion stages (pp-chain, CNO cycle, triple-alpha), nucleosynthesis, post-main-sequence evolution through red giants and the horizontal branch, and stellar endpoints — planetary nebulae, white dwarfs and the Chandrasekhar limit, supernovae, neutron stars, and black holes. Use when placing a star on the HR diagram, estimating its lifetime, predicting its fate from its mass, or teaching how a star lives and dies.

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

The creative process in art from idea to exhibition. Covers five phases of creative work (inspiration, incubation, exploration, execution, reflection), sketchbook practice, artist statements, critique methodology (formal and conceptual), portfolio development, and the studio as a working environment. Use when guiding students through project development, facilitating critique sessions, developing artist statements, curating portfolios, or understanding how professional artists structure their creative practice.

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

Periodic phenomena and frequency analysis. How repetition creates structure — from simple oscillation to Fourier decomposition.

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

Functions, categories, and information. How mathematical objects relate to each other — morphisms, entropy, signal processing.

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

当用户写出的内容读起来像产品公告/官方更新(如"我们发布了X""支持Y功能""效果很好")，需要翻译成读者能拿走的外部语言时调用。也适用于:用户问"怎么把公告式表达改成强推文""这条推文为什么没人理"(若原因是只讲自己不讲读者)、"怎么把功能介绍写得吸引人"。Trigger 词:公告式表达/内部语言/外部语言/帮助式表达/announcement tone/helpful expression/show don't tell/translate to reader value。不适用于:从零起草新内容(用 x-short-content-craft)、检查内容五件套完备性(用 x-five-piece-checklist)、评估内容值不值得发(用 x-four-saves)。

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

用户要找对标账号/分析竞品爆款/找差异化选题时;或问"怎么做AI工具赛道的差异化""how to find benchmarks / differentiate"时。按5步走:找3-5个低粉高爆对标(搜索from:xxx min_faves:10)→分析90天爆款抓隐性需求→学互动策略→拆变现模式→三公式变形(场景细化/人群聚焦/观点反转)出差异。不适用于:已有定位日常发内容(→x-short-content-craft)、纠结选IP还是泛流量(→x-positioning-tradeoff)、检查草稿(→x-five-piece-checklist)、纯信息查询。

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

用户要起草一条 X 短内容(推文/帖子)、不知道用什么结构或类型时;或问"怎么发一条教人用 XX 的帖""怎么排版推文能让更多人收藏""what structure should I use for a tweet / how to write a tutorial post"时。先按目标指标选四类型之一(故事→涨粉 / 列表→收藏 / 观点→互动 / 教程→忠诚),再用 Hook-Body-CTA 三段骨架起草;资源/工具类可套爆款公式(工具+场景+三步)。不适用于:已有草稿想检查五件套完备性(→x-five-piece-checklist)、想把公告腔改写成帮助式语言(→x-three-translations)、想按读者功能分类预测传播上限(→x-content-archetypes)、纯信息查询(如推文字数上限)。

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

Show the active SkillNote collection and the skills synced into this project for Codex. Use when the user says "skillnote", "what skills do I have", "show my collection", or wants a SkillNote status/dashboard.

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

Self-evolution workflow for the agent. Before substantive work, recall past outcomes from evolution memory; while editing, detect improvement signals; at task end, record the outcome; when reusable, distill or search the EvoMap network for proven genes/capsules. Use when the user starts non-trivial work (a feature, a fix, a refactor) or asks the agent to "evolve", "learn from this", or "remember how this went".

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

Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code. Use OpenCover format with ReportGenerator for Risk Hotspots showing cyclomatic complexity and untested code paths.

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

Show details about a specific storage bucket. Requires authentication. Use for Agentuity cloud platform operations

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

Initialize or improve AGENTS.md files that define how coding agents operate in a repo. Use when asked to set up or replace an agent init command (Codex, Claude), standardize multi-agent behavior, or audit an existing AGENTS.md for clarity, commands, boundaries, and repo-specific context. For Claude Code, also create CLAUDE.md as a symlink to AGENTS.md.

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

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

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

Turns a target someone has already committed to (a board plan, an annual plan, a contract) into a plan the team can measure: KPIs in three tiers with a guardrail for each, a baseline from real data, monthly pacing with lag and seasonality, and two or three channels chosen from how your ICP actually searches and buys. Writes context/goals/MMYY-scope.md and context/goals/measurement.md. It never invents the target. Triggers: "set our goals", "what are our KPIs", "revenue target and pacing", "which channels and what targets", "write the scope file", "are we on track". Run after /funnel-strategy. Not for designing funnel stages (use /funnel-strategy).

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