「explanation」の検索結果

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.

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

Configure, repair, explain, and verify private Obsidian synchronization across Windows, macOS, GitHub, and mobile devices. 配置、修复、解释并验证 Windows、macOS、GitHub 与移动设备之间的 Obsidian 私有同步。Use for private vault repositories, Windows edit-event sync, macOS Obsidian Git sync, mobile setup, GitHub token/key guidance, Pull/Commit/Push workflow explanation, device-setting isolation, duplicate-note diagnosis, accidental deletion recovery, multi-device sync strategy, failed pushes, and end-to-end checks. 用于私有笔记仓库、Windows 编辑事件同步、macOS Obsidian Git 同步、移动端配置、GitHub Token/Key 指导、Pull/Commit/Push 工作流解释、设备设置隔离、重复笔记诊断、误删恢复、多端同步策略、推送失败和端到端检查。

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

Enforces decisive execution without confirmation requests; suppresses redundant explanations and prioritizes direct action.

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

Use for visual explanations and documents. Triggers: diagrams, charts, interactive models, HTML reports, infographics, 시각화, 그려줘, 문서 만들어줘, 보고서, PDF 생성.

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

Solve competitive programming and LeetCode-style problems with educational explanations. Use when asked to "solve this problem", "help with this leetcode", "competitive programming solution", "solve this algorithm problem", "coding challenge solution", "how to solve this coding problem", or any algorithmic problem-solving request.

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

Transform Markdown or text specifications into human-readable HTML documents with summaries, reordered structure, visual explanations, diagrams, charts, and traceability to the source. Use when asked to convert a spec, requirements document, API spec, product spec, design doc, or technical document into readable HTML, especially when the user wants summarization, restructuring, diagrams, graphs, images, or visual aids rather than a literal Markdown-to-HTML conversion.

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

Ask Kimi a read-only free-form question about the current repository. Use for prose explanations, flow tracing, module comparisons, or conceptual reasoning where Codex should delegate the answer to local kimi-code rather than perform implementation.

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

Eight tested identity approaches for Claude prompts, each shaping depth, vocabulary, reasoning style, and what Claude treats as obvious vs. requiring explanation. Use when the user wants a specific identity template — retrieving, reviewing, customizing, or building a role definition. Trigger on: "give me the Strategic Advisor identity," "show me the identity template for," "I need a Technical Architect role," "build a custom role for," "show me all available identities." Also use when reviewing a prompt's identity layer or when output lacks domain-appropriate depth. Provides 8 tested approaches across strategy, technical, research, communications, and operations domains plus a template for building custom identities. If the user is unsure which identity fits their task, use rootnode-block-selection first if available. Do NOT use for evaluating complete prompts — use rootnode-prompt-validation if available. Do NOT use for full prompt assembly — use rootnode-prompt-compilation if available.

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

Use when a concept needs practising: the user asks for an exercise, quiz, recall, or gap probe. Not for explanations: use explain-concept.

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

Use when the user wants a course, a learning workspace, or ongoing teaching across sessions, with cited lessons and retention-gated advancement. Not for one-off explanations: use explain-concept.

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

Use when a user, especially a new hire, asks for mentoring, guidance, or explanation of infrastructure or engineering practices. Not for code changes.

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

Use when asked to create an explainer document for a concept, diff, idea, or work recap. Drafts and verifies it in a scratch directory. Not for one-screen explanations: use explain-concept.

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

Use when asked to explain or teach a subsystem, module, pattern, or change in progressive layers from purpose to code depth. Not for design rationale: use why. Not for source or remote-system changes.

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

Use when the user says "wait, what", "the explanation is unclear", "say that again", or asks to restate the last response in plain language. Not for tasks that require source or remote-system changes.

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

Trace a Proto UI change through authoritative spec lifecycle, legacy explanation, dated context, implementation, executable evidence, package surfaces, and public projections. Use before deciding scope, changing behavior, reviewing a pull request, or investigating drift.

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

Create or update a readable Proto UI legacy-contract projection for explanation or an explicitly accepted uncataloged gap. Use for internal contract prose, migration banners, rationale, or synchronized readable projections. Do not use when an applicable spec entity already owns the rule or when semantics are unsettled.

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

Transform academic papers into in-depth technical articles with multiple writing style options. Use the MinerU Cloud API for high-precision PDF parsing, automatically extracting images, tables, and formulas. Optional formula explanations and GitHub code analysis, generating Markdown and HTML formats.

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

図を使ってコードを説明します。コードの動作を説明する時、コードベースについて教える時、または「これはどう動くの？」と聞かれた時に使用します。

Analysis of Competing Hypotheses — structured technique for evaluating multiple explanations against evidence. Use when facing ambiguous attribution or multiple plausible scenarios. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Runs on ungraded evidence when asked, labelled as such, unweighted, and capped at Moderate confidence.

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

Prose quality checker for Quarto (.qmd) files, grounded in William Zinsser's *On Writing Well* (30th Anniversary Edition). Checks for clutter, weak verbs, hollow qualifiers, clichés, inflated academic voice, poor leads and endings, pronoun and tense inconsistency, and unclear explanation. Produces a structured markdown report organized by document section — never modifies the source file. Use when asked to improve prose quality, tighten writing, reduce clutter, or apply Zinsser's writing principles to a draft. For grammar and punctuation, use the proofread skill. For APSA style rules, use the apsa-style skill. Supports an optional output-file argument and an optional @sec-label argument to restrict checking to one section.

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

"Apply Bhaskar's critical realism to analyze phenomena through three ontological domains (real, actual, empirical), identify generative causal mechanisms via retroduction, and examine structure-agency interplay. Use this skill when the user needs to go beyond surface correlations to underlying causes, design research that distinguishes mechanisms from events from experiences, or when they ask 'what causes this beyond the observed pattern', 'what structures enable or constrain this behavior', or 'how do I move from correlation to causal explanation'.".

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

Search, screen, deeply read, synthesize, and publish recent research papers for a user-specified topic, window, count, quality/attention balance, and language. Use for evidence-anchored literature digests, cross-paper comparisons, original-language excerpts, Chinese explanations, guided Feishu setup, or Feishu research reports.

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

Use for hands-on repository work when a quiet, risk-scaled engineering method can improve design, implementation, debugging, review, delegation, workspace lifecycle, or verification. Keep clear local changes direct, preserve the complete requested outcome, and add method only where risk or uncertainty justifies it. Do not use for general technical explanations, simple file lookup, casual discussion, or non-engineering writing.

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

Analyze budget-versus-actual or forecast-versus-actual performance and turn finance data into a management-ready narrative using variance logic, drivers, cash impact, and forward actions. Use when finance, FP&A, or business leaders need commentary, management accounts, or performance explanation. Do not use for bookkeeping entries, tax filing preparation, or legal accounting sign-off.

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