「used」の検索結果

系统化与焦点解决方法：奇迹提问、刻度提问、例外探索、循环提问、假设性提问、恶化提问、应对提问。合并自 solution-focused-therapy 与 systemic-questioning。

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

ドゥ・シェーザーとバーグによる解決志向ブリーフセラピー（SFBT）：ミラクル・クエスチョン、例外の探索、スケーリング、リソースの活性化。

德·沙泽尔与伯格的焦点解决短期心理治疗（SFBT）：奇迹提问、例外探索、评定量表、资源激活。

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

Métodos sistémicos y enfocados en soluciones: pregunta del milagro, escala, exploración de excepciones, preguntas circulares, preguntas hipotéticas, preguntas de empeoramiento, preguntas de afrontamiento. Fusionado de solution-focused-therapy y systemic-questioning.

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

Системные и ориентированные на решение методы: чудесный вопрос, шкалирование, поиск исключений, циркулярные вопросы, гипотетические вопросы, вопросы на ухудшение, вопросы на преодоление. Объединено из solution-focused-therapy и systemic-questioning.

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

Create an operating policy and roadmap for a live portfolio of Claude Code skills. Use when the user asks to organize, govern, audit, measure, retire, or scale skills already used by a team or repository. Also trigger on "スキルの運用計画", "スキルポートフォリオ", "スキルロードマップ", "スキルを整理して".

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

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

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

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

This skill should be used when the user asks to "analyze a koseki", "戸籍の分析", "家族関係", "相関図", "family tree", "戸籍謄本", "親族関係", "家系図", "戸籍を読んで", "相続関係図", "法定相続情報", "戸籍から相関図を作って", or wants to extract family relationships from documents.

This skill should be used when the user asks to "calculate inheritance shares", "法定相続分を計算", "相続分を出して", "相続割合", "誰がどれだけ相続する", "遺留分", or wants to compute statutory inheritance shares from a family tree.

This skill should be used when the user asks to "verify", "test", "check installation", "動作確認", "テスト", "ヘルスチェック", or wants to verify that the bengo-toolkit plugin is working correctly.

This skill should be used when the user asks to "fill a template", "テンプレート入力", "書式入力", "裁判所書類の作成", "テンプレートに入力", "書式に記入", "この書式に入れて", "PDFからテンプレートに", "書類を作成して", "これも追加して", "このデータも入れて", or wants to auto-populate or incrementally add data to court documents.

This skill should be used when the user asks to "calculate child support", "養育費を計算", "婚姻費用を計算", "養育費月額", "婚姻費用分担額", "算定表で計算", or wants deterministic computation of child support or marital cost-sharing under the 令和元年改定 standard.

This skill should be used when the user asks to "calculate property division", "離婚の財産分与", "財産分与計算", "清算金", "夫婦共有財産の分与", or wants deterministic computation of divorce property division under 民法 768.

This skill should be used when the user asks to "calculate traffic accident damages", "交通事故の損害額を計算", "損害賠償額を算出", "赤い本基準で計算", "逸失利益を計算", "後遺障害の慰謝料", "過失相殺後の金額", or wants deterministic computation of personal-injury damages under the Red Book (赤い本) standard.

This skill should be used when the user asks to "create a template", "テンプレート作成", "書式を登録", "XLSXをテンプレート化", "テンプレート登録", "この書式を登録して", "テンプレートを追加", or wants to register a new court document template from an XLSX file.

This skill should be used when the user asks to "search a law", "法令検索", "条文を見せて", "法律を調べて", "○○法 第○条", "条文参照", "法令を確認", "何条に書いてある", or wants to look up Japanese law articles from the e-Gov API.

This skill should be used when the user asks to "recalculate debt", "利息制限法で引き直し", "引き直し計算", "過払金", "過払い金", "サラ金", "貸金業者との取引履歴から引き直し", or wants deterministic recalculation of loan transactions under the Interest Rate Restriction Act.

This skill should be used when the user asks to "proofread", "校正", "誤字脱字チェック", "表記揺れ", "typo check", "文書チェック", "法律文書の確認", "この書面チェックして", "おかしいところない？", "文章確認して", "間違いがないか確認", "書面の確認", or wants to review a Japanese legal document for writing errors. Do NOT trigger for translation, summarization, or content generation requests.

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

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

Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts. Use when the user asks to show / diagram / visualize / sketch / illustrate what is going on, asks "what does this look like", "how does this flow", "show me the structure", or in Japanese 図で見せて / 図解して / 図にして / 構造を見せて / フローを見せて / 全体像を見せて / どうつながってるか見せて. Also use it proactively when an explanation is running long and a call tree, file tree, component tree, diff, Mermaid diagram, or a small HTML artifact would land faster than prose.

ToolUniverse plugin router. STEP 1 BEFORE ANY ANALYSIS: if the data folder contains `*_executed.ipynb`, run `tu run read_executed_notebook '{"data_folder":"<path>","search":"<keyword>"}'` to extract its cell outputs and apply EVERY filter/sample-exclusion the notebook used — even when the question says 'Using DESeq2/Run X/Compute Y' (this describes the METHOD the notebook used, not a request to rerun). The notebook's cell outputs are the only published authoritative answers; reimplementing or reading stale pre-computed CSVs in the data folder produces different numbers because of outlier-sample removal, library version, and filter steps you don't see by skimming. STEP 2 routing — pick a sub-skill name from this exact list (never invent): tooluniverse-rnaseq-deseq2 (RNA/miRNA-seq DE, correlation, PCA, clustering, dispersion), tooluniverse-gene-enrichment (GO/KEGG/Reactome/GSEA/pathway enrichment), tooluniverse-statistical-modeling (regression, ANOVA, ordinal/logistic, chi-square, correlation, power), tooluniverse-image-analysis (microscopy, colony, fluorescence, dose-response, .tif — including ANOVA / Dunnett / power-analysis on image-derived measurements), tooluniverse-epigenomics (DNA methylation, CpG, m6A, MeRIP-seq, bisulfite, ChIP-seq, chromatin), tooluniverse-sequence-analysis (FASTQ, Trimmomatic, BWA, samtools, coverage), tooluniverse-variant-analysis (VCF, VAF, SNP, mutation), tooluniverse-phylogenetics (treeness, PhyKIT, parsimony), tooluniverse-single-cell (scRNA, h5ad, scanpy), tooluniverse-crispr-screen-analysis (MAGeCK, sgRNA), tooluniverse-proteomics-analysis (mass spec, TMT). Use for CSV/Excel/VCF/FASTA/h5ad and any biology/chemistry/medicine analysis question.

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

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by breakdown-issues. It formats a scope GitHub Issue body (label cc-triage-scope, used before code analysis), runs the pre-posting checklist, and executes `gh issue create`. Invoke this skill ONLY from one of the parent skills via the Skill tool, after the parent has finalized the task breakdown. If a user asks to 'create a scope issue' or similar, route them to the parent skill (/breakdown-issues) rather than invoking this one directly.

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

Designs pooled sgRNA libraries for CRISPR knockout, interference (CRISPRi), activation (CRISPRa), Cas12a multiplex, base-editor, and prime-editor screens. Covers on-target scoring (Rule Set 2, Azimuth, DeepSpCas9, CRISPRon), off-target scoring (CFD, MIT), TSS-relative positioning for CRISPRi/a (Horlbeck, Dolcetto, Calabrese), PAM-variant chemistries, control-guide composition, oligo cloning architecture, and library QC. Use when choosing a genome-wide library (GeCKOv2 vs Avana vs Brunello vs TKOv3 vs Inzolia), designing a focused or paralog-focused custom library, picking CRISPRi vs CRISPRa TSS windows, deciding control-guide proportions, or diagnosing library skew and dropout in a freshly cloned pool.

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