341 件 ・ 関連度順
概要と使いどころ
Stress-test a Yuzu plan against the repo's domain language, code, CONTEXT.md, and ADRs while updating docs as decisions crystallize. Use when the user says `/grill-with-docs`, asks to grill a design with docs, wants decision interrogation, or needs ADR-adjacent planning.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
日本語の概要は準備中です。原文の説明を表示しています。
Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each. Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to "try the worst case". For visual design critique use emil-design-eng; for motion use review-animations.
日本語の概要は準備中です。原文の説明を表示しています。
Apply the devil's advocate technique: structured critical thinking that stress-tests ideas, plans, and decisions. Use when you need honest critique before committing to something important.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-test a plan, decision, or idea as a dependency-aware design tree. Use for grill-me requests, assumption audits, and decision clarification before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
对法律文本——合同、法规、规章或裁判文书——进行对抗式压力测试，检验其解释上的歧义： 找出受其约束的人们日后会对其含义产生分歧的薄弱接缝，并将每一处转化为具体的争议场景， 附双方论点、可能的结果和修复方案。当有人希望对法律文件进行压力测试、红队审查、 审计，或找出薄弱点、漏洞、缺口、歧义或起草问题时使用；当起草人希望在合同、法规、 规章或裁判文书发布前将其收紧时使用；当诉讼律师希望从裁判文书或合同中挖掘论点时使用； 或当有人交来一份法律文本并询问它会在哪里引发争议或进行争点识别时使用。对合同审查、 法规歧义分析、裁判文书射程分析和起草质量检查都触发本技能——即使使用者从未说出 "压力测试"或"歧义"。
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial dialectic tool inspired by GAN. Alternates between Generator (creative advocate) and Discriminator (adversarial critic). Supports forced role selection (g/d), intensity modes (hard/soft), and multi-language output. Use for stress-testing ideas, business plans, code, and spec designs.
日本語の概要は準備中です。原文の説明を表示しています。
Normalizes and transforms RNA-seq count matrices for DE, visualization, clustering, and ML. Covers between-sample (TMM, TMMwsp, RLE/median-of-ratios, upper quartile), within-sample (TPM, FPKM/RPKM), variance-stabilizing (VST, rlog, log-CPM), GC-content correction (cqn, EDASeq), and single-cell (scran deconvolution, scanpy normalize_total). Encodes the composition-bias rationale, the "most genes not DE" assumption and its catastrophic failure modes (MYC amplification, apoptosis, viral host shutoff, prokaryotic stress), the "lengthScaledTPM is not TPM" naming trap, the "TPM is not for DE" rule, the blind=TRUE vs FALSE decision, ERCC spike-in normalization (SBN), and the single-cell zero-inflation breakdown of TMM/RLE. Use when choosing or applying normalization, debugging shifted-MA-plot diagnostics, handling zero-heavy single-cell data, or correcting GC bias.
日本語の概要は準備中です。原文の説明を表示しています。
This skill determines whether an adolescent or adult patient meets DSM-5 criteria for gender dysphoria (gender incongruence) by evaluating the presence of at least two of six specified criteria over a minimum 6-month duration, accompanied by clinically significant distress or impairment. It is triggered when a clinician queries whether the patient's reported symptoms align with gender dysphoria, such as persistent incongruence between experienced/expressed gender and designated gender.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends equipping every patient with primary adrenal insufficiency (PAI) with a glucocorticoid injection kit for emergency self‑administration and providing training on its use. Trigger when preparing a PAI patient for stress dosing, adrenal crisis prevention, or when prescribing glucocorticoid replacement and needing to ensure emergency preparedness.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends immediate IV hydrocortisone stress dosing for patients with suspected adrenal crisis presenting with severe adrenal insufficiency symptoms such as hypotension, hyponatremia, hyperkalemia, or acute abdominal pain. Use when clinician observes signs of adrenal crisis (e.g., syncope, delirium, marked abdominal tenderness) prior to diagnostic test results.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends initiating hydrocortisone replacement at a total starting dose of 8 mg/m2 body surface area per day, given in three or four divided doses, for children with confirmed primary adrenal insufficiency (PAI). Use when starting glucocorticoid therapy in pediatric PAI patients, adjusting the dose according to individual clinical response, growth, and need for stress coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Recommends adjusting glucocorticoid doses on the day of surgery based on illness severity and magnitude of surgical stress. Triggers when managing a patient requiring surgery needing perioperative glucocorticoid management, such as "patient on HC for central AI undergoing major abdominal surgery" or "patient with hypopituitarism scheduled for minor procedure".
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Validates a plan before committing to it - checks whether the ranking survives the assumptions, finds the most likely way it fails, and makes the trade-offs explicit via a Pareto frontier instead of an invented single score. Use before a launch, price change, migration, infrastructure change or major commitment, when running a premortem, when two objectives conflict, or when a decision depends on an assumption nobody has tested.
日本語の概要は準備中です。原文の説明を表示しています。
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
日本語の概要は準備中です。原文の説明を表示しています。
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
日本語の概要は準備中です。原文の説明を表示しています。
Use for a pre-mortem, or before committing to a plan, launch or migration: "what could go wrong?", "stress test this plan", "how might this fail?", "risks before we ship". Assumes failure, lists causes, ranks them and sets mitigations. Skip for explaining a failure that already happened.
日本語の概要は準備中です。原文の説明を表示しています。
Use when decomposing a company objective into team OKRs, auditing a draft OKR tree, or stress-testing an existing one for measurability and laddering.
日本語の概要は準備中です。原文の説明を表示しています。