「understand」の検索結果

Use when the user has merge conflicts or says "resolve conflicts". Understands conflict markers, resolution strategies, and verification workflow.

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

Use when the user wants to learn a topic or verify real understanding — rapid-competence session, error drills, learning sprint, gap probe, Feynman check. Triggers 'teach me X', 'quiz me'.

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

Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.

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

Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.

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

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

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

Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.

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

[Code Intelligence] Use when investigating what happens when code executes, understanding blast radius, or tracing frontend-to-backend flows.

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

[Fix & Debug] Use when you need to investigate and explain how existing features or logic work. Flag: --mode=explain produces a one-way developer-narrative explanation (Purpose → How → Why → Impact) tuned by coding level; use /understand for the standalone prompt-driven explainer.

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

Retrieves scientific papers from PubMed and creates plain-language research summaries. Use when users ask about medical research, scientific studies, clinical trials, disease treatments, or want to understand recent scientific literature on any biomedical topic.

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

Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.

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

FOUNDATIONAL SKILL - Analyze every prompt for underlying motivation using Golden Circle (WHY->HOW->WHAT). Runs BEFORE any other skill. No action without understanding WHY.

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

Build an evidence-backed working model of an existing codebase. Use when you must orient in a large or unfamiliar repository; explain architecture or a subsystem; trace a request, runtime, control, or data flow for a concrete question or bug; analyze a branch, commit, diff, or pull request for behavioral impact and blast radius; or assess AI-generated or changed code against requirements, contracts, invariants, tests, and runtime evidence. Default to read-only investigation. Do not trigger only because a coding task touches an existing repository; use when understanding or verification is the requested outcome or a substantial prerequisite.

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

Competitive positioning diagnostic — figures out where you actually stand relative to competitors and whether that position is defensible. Use this skill when someone needs to understand their real competitive position (not the one on the slide deck), when a new competitor has entered the market, when customers are switching and nobody can explain why, when pricing power is eroding, when a strategic investment depends on knowing whether the moat is real, or when leadership says "we're differentiated" but can't explain how. Draws on Playing to Win, Porter's generic strategies, and Blue Ocean thinking — applied as diagnosis, not planning. Based on practice by Eterdis (eterdis.com).

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

The Eterdis Strategy Diagnostic — an AI-guided conversation that helps leadership teams understand their strategic situation before committing to a direction. This is the entry point skill. It runs an open-ended discovery conversation, detects which strategic frameworks are most relevant, and produces a strategy-ready brief. Use this skill when someone asks for a general strategic assessment, when they don't know which framework they need, when they want to "figure out where we stand," or when they're preparing for a strategy engagement. This skill orchestrates other Eterdis skills — it does not replace them. Triggers on: "help me think through our strategy," "where should we start," "we need to figure out what's going on," "strategic health check," "prepare for a strategy review," or any open-ended request for strategic thinking. Based on 20 years of consulting practice by Eterdis (eterdis.com).

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

Wardley Mapping for strategic positioning — map your value chain from customer need to underlying components, plot where each component sits on the evolution curve (novel to commodity), and spot the strategic plays that movement creates. Use this skill when someone wants to understand where their industry is heading, whether they're building things they should be buying, where competitors are vulnerable, what's about to become commoditised, or why their competitive advantage is eroding. Triggers on questions about build-vs-buy, component evolution, value chain analysis, commoditisation risk, or strategic positioning relative to market movement. Three modes — full diagnostic (build a map from scratch), review (update positions and reassess), and alert triggers (set tripwires for when components move). Based on practice by Eterdis (eterdis.com).

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

Continuous environmental scanning across six PESTEL categories — Political, Economic, Social, Technological, Environmental, Legal. Not a one-time analysis but an ongoing radar. Three modes. Diagnostic mode runs a full scan and prioritises forces by impact, speed, and reversibility. Review mode checks the watch list monthly for movement and new signals. Alert mode defines concrete monitoring triggers for each top force. Use whenever someone wants to understand external forces acting on their business, assess macro risk, prepare for planning, or check whether the world has moved since last time they looked. Connects to the strategy map (forces act on the chain) and Wardley Map (forces drive component evolution). Based on practice by Eterdis (eterdis.com).

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

Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.

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

Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.

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

Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.

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

Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.

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

Deep research workflow that starts from a GitHub repo URL/slug, pulls upstream intel, then expands to Reddit + open web for community reception. Use whenever Ahmad gives a GitHub link and asks to understand it, see updates, audit the community, or compose a report. Trigger phrases include "research this repo", "report on this github", "what's happening upstream", "community reception", "compose a report on <repo>", and any message that contains a github.com URL plus a research/report ask.

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

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.

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

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.

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

This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from the graph before grepping or reading source files. Every command runs through `bin/harness graft`.

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