「method」の検索結果

Expert-level dark matter physics covering observational evidence, candidate particles, detection methods, structure formation, and alternative gravity theories.

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

Expert-level heat exchanger design covering shell and tube, plate, air coolers, heat integration, fouling, and thermal-hydraulic design methods.

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

Expert-level aerodynamics covering subsonic and supersonic flow, lift and drag, airfoil theory, boundary layers, compressible flow, and CFD methods.

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

Expert-level astrodynamics covering orbit determination, trajectory optimization, launch vehicle ascent, re-entry dynamics, and numerical methods for space mission analysis.

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

Expert-level exoplanet science covering detection methods, orbital dynamics, planetary atmospheres, habitability, and the search for biosignatures.

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

Expert-level applied electromagnetics covering transmission lines, waveguides, antennas, microwave circuits, EMC, and computational EM methods.

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

Expert-level control systems engineering covering feedback control, PID design, root locus, frequency domain methods, state-space design, and digital control.

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

Expert-level electrochemistry knowledge. Use when working with electrochemical cells, electrode potentials, Nernst equation, electrolysis, batteries, fuel cells, corrosion, electroplating, or electroanalytical methods. Also use when the user mentions 'galvanic cell', 'electrolytic cell', 'electrode potential', 'Nernst equation', 'overpotential', 'Butler-Volmer', 'battery', 'fuel cell', 'corrosion', 'electroplating', 'cyclic voltammetry', or 'impedance spectroscopy'.

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

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

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

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

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

Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.

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

The kpopper method: a knowledge record (GROUNDING.yaml) for work that gets revisited - what is known, where each piece came from, and what would make each conclusion wrong. Use when asked what kpopper is or how to keep a record, when choosing which kpopper skill fits a moment, or when no narrower one does. The occasions have their own skills: ground (read the record before answering), record (write what the work found), map (map existing materials), annotated-doc (a standalone HTML document with evidence), hub (the record's visual home), consolidate (hypotheses and merges), watch (background checks).

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

Guides continuous improvement and change management for SMEs adopting AI. Applies Marginal Gains philosophy, Kaizen principles, and structured sprint methodologies to organizational transformation. Use when user asks about change management, continuous improvement, AI adoption strategy, team resistance, transformation roadmaps, or improvement sprints.

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

Systematic testing methodology for exhaustive branch coverage, edge case identification, and production bug prevention. Use when PR review reveals incomplete test coverage, when tests pass but users report bugs, when code changes break existing features, when verifying all branches and edge cases before merge, when analyzing "it works on my machine" issues, when planning test strategy for new features, or when debugging flaky tests and race conditions.

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

BEFORE writing/changing tests, mocks, or test-only methods on production classes — mocking-the-mock, production pollution, overfit assertions; for order, `test-driven-development` wins.

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

When the user says 'refactor this', 'rename class', or 'move method'. Safely refactors code in any language — finds all callers, updates downstream dependencies, verifies via quality tools.

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

Method for adding agent comments and work to a shared file without overlapping other agents. Creates isolated workspaces per agent with UTC timestamps. Use when told to add comments, reviews, or work to any file.

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

[Code Quality] Use when you need restructure code without changing behavior using extract method, extract class, rename, move, and inline patterns.

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

Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships. Use when output must clear two independent adversarial reviewers before it ships.

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

Analyze, design, write, revise, translate, and review empirical or technical research papers through an evidence-bounded dialectical workflow. Use when Codex must develop a research question, integrate reference papers with a user's ideas, build phenomenon-mechanism-conditions reasoning, design methods or experiments, restructure or edit a manuscript, translate Chinese academic text into restrained English, answer reviewers, or run multi-round peer-review convergence without fabricating evidence.

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

GStack retrospective method for completed workstreams, identifying what worked, what failed, process changes, and role-skill improvements.

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

GStack freeze method for pausing writes and limiting work to evidence gathering when a task is unsafe, ambiguous, or production-sensitive.

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

GStack design-review method for reviewing rendered UI, landing pages, decks, or visual artifacts for hierarchy, layout, accessibility, and polish.

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

GStack report-only QA method for checking web or UI behavior, documenting blockers, and preserving evidence without modifying code.

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