「judgment」の検索結果

Think and work like an expert Air Quality Scientist. Use when a task calls for Air Quality Scientist judgment. Reasons from source emissions through transformation, transport, and dose using SMOKE/MOVES inventories, WRF-driven CTMs like CMAQ and CAMx, PMF/ME-2 apportionment, and concentration-response functions, while treating rotational PMF ambiguity, AOD-to-PM bias in humid regions, uncalibrated low-cost sensors, and untreated wildfire exceptional events as first-class failure modes.

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

Think and work like an expert Algebraist. Use when a task calls for Algebraist judgment. Reasons from carriers, operations, and morphisms through isomorphism theorems, universal properties, exact-sequence and homological tools (Ext, Tor, snake lemma), and computational systems like GAP, Magma, SageMath, and Lean while treating silently smuggled hypotheses (commutativity, units, Noetherian, algebraically closed base), characteristic-p false friends, and noncanonical isomorphisms as first-class failure modes.

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

Think and work like an expert Applied Mathematician. Use when a task calls for Applied Mathematician judgment. Reasons from formulation-first modeling, Buckingham scaling, and asymptotics (matched expansions, boundary layers) through FEM/FVM numerics (FEniCS, PETSc, LAPACK), Tikhonov inverse problems, and ASME/Sandia V&V while treating ill-posed inversion, stiffness, and numerical diffusion as first-class failure modes.

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

Think and work like an expert Algorithms Researcher. Use when a task calls for Algorithms Researcher judgment. Reasons from separating problem, model, and cost model (comparison, word-RAM, arithmetic, online) through exchange/matroid greedy proofs, subproblem-DAG dynamic programming, max-flow min-cut and Goemans–Williamson primal-dual rounding, Karp–Rabin fingerprinting, competitive ratio and Yao's principle, PTAS/FPTAS (Williamson–Shmoys), and Instance Space Analysis over DIMACS10/MIPLIB 2017/SuiteSparse while treating amortized-versus-average-case conflation, unproven greedy killed by a 4-node counterexample, Monte Carlo without a false-match probability, DIMACS10 suite overfitting, and 'linear time' hiding word-size tricks over bit-length L as first-class failure modes.

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

Think and work like an expert Analytical Chemist. Use when a task calls for Analytical Chemist judgment. Reasons from the chemical measurement process through ICH Q2(R2) and USP <621> validation, CRM traceability, EURACHEM uncertainty budgets, and HPLC/GC/LC-MS/ICP-MS workflows while treating matrix effects, SST drift, peak tailing, and ion suppression as first-class failure modes.

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

Think and work like an expert Antenna Engineer. Use when a task calls for Antenna Engineer judgment. Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as first-class failure modes.

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

Think and work like an expert Bacteriologist. Use when a task calls for Bacteriologist judgment. Reasons from bacterial growth physiology, selective culture, Gram stain, MALDI-TOF and 16S/WGS identification, EUCAST/CLSI AST, BSL containment, contamination and VBNC, using BacDive and BV-BRC for strain metadata and pathogen genomics.

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

Think and work like an expert Automotive Engineer. Use when a task calls for Automotive Engineer judgment. Reasons from vehicle-level requirements, regulatory limits, energy/exergy budgets, and distribution-based durability through DFMEA/DVP&R, DoE calibration (INCA, CANape, HIL), Pacejka tire and multibody models, rainflow fatigue, and source-path NVH analysis while treating undocumented build-level and cal-ID deltas, unmet emissions preconditioning and OBD readiness, ADAS sensor misalignment, and cross-domain torque-arbitration conflicts as first-class failure modes.

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

Think and work like an expert Anatomist. Use when a task calls for Anatomist judgment. Reasons from homology, EPB, and von Baer principles through gross dissection, diceCT/μCT/MRI pipelines, UBERON–PATO EQ annotation, MorphoSource/oVert digitization, geometric morphometrics, and NAV/TA2 nomenclature while treating fixation shrinkage, segmentation artifacts, landmark homology error, and collection bias as first-class failure modes.

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

Think and work like an expert Antimicrobial Resistance Scientist. Use when a task calls for Antimicrobial Resistance Scientist judgment. Reasons from MIC distributions, ECOFFs, and phenotype–genotype concordance through EUCAST/CLSI AST, CARD/RGI and AMRFinderPlus resistomes, GLASS/WHONET/NARMS surveillance, carbapenemase/ESBL/MRSA mechanism panels, and heteroresistance PAP while treating breakpoint mixing, genotype-without-phenotype overclaim, selection-bias surveillance, and CARD version drift as first-class failure modes.

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

Think and work like an expert Anesthesiologist. Use when a task calls for Anesthesiologist judgment. Reasons from control of consciousness, analgesia, autonomic response, and oxygen delivery through the ASA Difficult Airway Algorithm, capnography and arterial-waveform trends, quantitative TOF monitoring, and ASRA/ERAS protocols while treating cannot-ventilate airways, local anesthetic systemic toxicity, malignant hyperthermia, and residual neuromuscular blockade as first-class failure modes.

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

Think and work like an expert Animal Geneticist & Breeder. Use when a task calls for Animal Geneticist & Breeder judgment. Reasons from additive genetic variance, response to selection (R = i h sigma_A), accuracy, and inbreeding depression through REML/BLUP and ssGBLUP pipelines (BLUPF90, ASReml, WOMBAT), economic selection indices, optimum-contribution mate allocation, and Interbull MACE while treating confounded contemporary groups, prediction bias/dispersion, popular-sire inbreeding and rising deleterious haplotypes, GxE reranking, and pedigree or genotype-calling errors as first-class failure modes.

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

Think and work like an expert Animal Nutritionist. Use when a task calls for Animal Nutritionist judgment. Reasons from NASEM/AAFCO requirements, SID amino acids and ideal protein, CNCPS MP/NE balance, and NANP feed libraries through NIR-wet chemistry validation, ileal vs fecal digestibility, pen-structured mixed models, and ARRIVE reporting while treating intake confounds, NIR calibration drift, acidosis/sorting, and pseudoreplicated pens as first-class failure modes.

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

Think and work like an expert Animal Scientist. Use when a task calls for Animal Scientist judgment. Reasons from NRC nutrient requirements, ad libitum intake, energy/protein partitioning, and genotype x environment x management through ration software (CNCPS, NDS, NRC), pen-blocked trials with mixed models (lme4, PROC MIXED), and BCS, NIR, and rumen/BHBA diagnostics while treating intake collapse, milk fat depression, acidosis, heat stress, wrong experimental unit, and violated withdrawal times as first-class failure modes.

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

Generate structured feature specifications through a collaborative product interview. Acts as a senior PM and business analyst pair — arrives with a point of view, challenges scope, proposes options at every decision. Composes the requirement-quality atom for spec quality enforcement and collaborative-judgment for surfacing genuine decisions. Produces an epic/feature hierarchy in .lattice/requirements/ that serves as direct input to design-blueprint. Use when the user says 'forge requirements', 'write requirements', 'spec this feature', 'create a feature spec', 'define this epic', 'write a PRD', 'spec out what we are building', or 'requirement forge'.

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

Run a complete design workflow -- from establishing context through four progressive design levels (Capabilities, Components, Interactions, Contracts) to an approved blueprint. Composes knowledge-priming, context-anchoring, learning-harvest, collaborative-judgment, design-first, architecture, and domain-driven-design into one process. Handles both new features (create context doc) and resuming existing work (load context doc). Level 5 (Implementation) is delegated to code-forge. Use when starting a design, planning architecture, or when the user says 'design a feature', 'blueprint', 'start designing', 'plan the architecture', or 'let's design before coding'.

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

Use Grok 4.5 as the required external design advisor when a task needs UI critique, UX critique, component-choice review, interaction-flow review, design imagery markdown, art direction, visual hierarchy judgment, design-system fit, color/type/layout suggestions, HTML mockups, SVG icons, handwritten SVG wordmarks, or file-based feedback on existing UI. Trigger on requests like "design a page", "generate design imagery", "give design advice", "optimize this UI", "improve UX", "optimize user flow", "review interaction", "check usability", "reduce friction", "choose the right component", "review this design", "create an icon", "suggest colors", "UI mockup", "visual direction", "lettering", "wordmark", "handwritten logo", or when another agent needs a second opinion on visual or interaction quality.

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

Use this skill whenever the user asks for an HTML-first visual design deliverable or design judgment: interactive prototype, slide deck, motion demo, infographic, dashboard, landing page, whitepaper, changelog, business card, social cover, brand system, design critique, multi-variant exploration, or export to MP4, GIF, PPTX, PDF, or SVG. It is optimized to make AI agents do the routing, template selection, verification, and export prep so humans spend less time prompt-engineering. Do not use for production web apps, SEO sites, backend systems, or pure copy edits.

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

GitHub issue creation skill. Analyzes the entire codebase impact based on user request, then creates a structured issue with AI-verified/human-judgment-needed/caution sections. /issue "issue description" Trigger: "/issue", "이슈 만들어", "issue 만들자", "깃헙 이슈"

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

Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.

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

MEMO-ONLY prior-work overlap advisory: surfaces the two ADVISORY taxonomy signals neither a tool nor a model can decide from the paper alone — ADV-TRIVIAL-COMBINATION (standard A+B+C / 缝合 stapling) and ADV-DUPLICATE-PUBLICATION (repackaged / duplicate submission). The executor RETRIEVES candidate prior work (DBLP fuzzy-title + boolean · WebSearch · WebFetch) from the paper's own title + contribution spans in the evidence ledger; TWO fresh cross-model codex reviewers (one per axis) LAY OUT the overlap side-by-side against each anchored contribution claim. It NEVER rules 'trivial' or 'duplicate' (that is a human judgment) and absence of a match is NOT evidence of originality. Emits novelty-duplication-advisory.memo.md + an info-only findings mirror; carries NO verdict weight — tools/adjudicate_findings.py lists it in ZERO_WEIGHT_SKILLS and caps it at info. Detect-only. Adapted from ARIS novelty-check, reframed from 'is MY idea novel' to 'here is the overlap a reviewer should weigh'. Triggers: "novelty advisory", "duplication check", "prior-work overlap", "is this stapling", "缝合", "查重", "重复发表", "duplicate submission".

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

Break out of a locked problem frame by picking one disciplined move — reframe, provocation (Po), random stimulus, SCAMPER, inversion, structured analogy, constraint play, or family traversal — and committing to it before evaluating. Use when stuck, when options feel narrow or obvious, when iterations produce variations of the same idea, or when the user says "widen this", "break out of", "think differently", "I'm stuck", "feels too obvious", "stress-test the framing", "what am I missing", or holds two related examples and asks what lies between or beyond them. Complements challenging (which evaluates) and convening-experts (which synthesizes viewpoints); this skill generates distance, not judgment.

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

Implement ReasoningBank adaptive learning with AgentDB's 150x faster vector database. Includes trajectory tracking, verdict judgment, memory distillation, and pattern recognition. Use when building self-learning agents, optimizing decision-making, or implementing experience replay systems.

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

Use when code needs a judgment about natural language that rules or regex cannot make (classify, route, triage, moderate, score, rank, match, dedupe, filter, extract, verify, or gate an action), when brainstorming where AI could fit in an app, when an LLM call exists only to pick a label, score, or yes/no, or when code uses TypeSafe AI, Jev, System One, typesafe-sdk, or @typesafe-ai/sdk.

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