「measurement」の検索結果

Adopt declscope on an existing Go codebase and drive its diagnostics to zero. Read this when introducing declscope to a repository, when choosing its configuration, when running declscope shrink for the first time, or when clearing a declscope baseline. Covers sizing each rule before enabling it, reading the diagnostics as structure, the remedy for each shape, and the measurement traps that produce false confidence. For writing new code in a repository that already runs declscope, use declscope-authoring.

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

Performance profiling principles. Measurement, analysis, and optimization techniques.

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

Abductive reasoning about causes. Takes a phenomenon, separates observations from interpretations, then spawns diagnosticians applying different reasoning lenses (technical, human-factors, process, incentive-structure, environmental, temporal, measurement-artifact, statistical) in isolation. Orchestrator evaluates candidate causes for fit-against-evidence, calibrates confidence honestly, and reports leading candidate(s) with distinguishing evidence needed. Produces feedback only — no code, no tickets, no artifacts.

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

Use when assessing body fat percentage from skinfold measurements, calculating body density, or interpreting body composition results using Durnin-Womersley or Jackson-Pollock equations.

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

Runtime profiling with multi-metric measurement, instrumentation, and performance map generation

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

Measurement-driven code refactoring — profile before changing, measure after, keep only if metrics improve. Covers complexity reduction, extraction patterns, and bulk refactoring for mechanical changes across many files.

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

Use when the user asks to measure command execution time or optimize a feedback loop. Records explicit measurements and recommends faster alternatives such as unit tests versus integration tests. It is opt-in; it does not run on every command.

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

Ask Claude, ChatGPT, and Gemini a question and capture the full trace behind the answer (the search queries each engine ran, the pages it retrieved, and the sources it cited, span by span). Use when asked to "trace an AI answer", "see what AI engines cite", "check AI citations", "which sources does ChatGPT/Claude/Gemini use", "why does the AI recommend X", or for any GEO (Generative Engine Optimization) measurement.

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

Content-addressed baseline-archive epoch partitioning. Partition baseline_archive.jsonl + the self-improving hub's baseline serving by a HASH of the full baseline-production+measurement spec — when the spec (margin_rule, fitness/margin logic version, the 4 roles' model+source, rubric/dim-set, bench, seed-pool identity) changes, the hash changes → a new epoch series (like seed-gen gen-*). Triggered by "baseline epoch", "baseline 아카이빙", "epoch partition", "spec hash", "content-addressed", "margin_rule namespace", "production logic 구분", "baseline 하위 서빙" keywords.

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

Design, implement, or evaluate GEODE's GEO capability with source-grounded stage diagnosis, frozen measurement contracts, and no-model preflight before live engine runs.

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

Ground GEODE design and evaluation work in Stanford CS329A Parts 2 and 5. Use for test-time compute, planning, multi-step reasoning, deep research, LATS, independent subplans, best-of-N, repair depth, measurement replication, verifier authority, and GEODE/Eco²/SIL/Crucible comparisons.

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

Treats a ctDNA assay as a molecule-counting experiment at the Poisson edge and builds its analytical-validation case the measurement-science way. Covers the genome-equivalent currency (~330 haploid copies/ng), the lambda = input_GE x VAF sampling ceiling (lambda>=3 for ~95% detection), the error-suppression ladder (raw NGS ~1e-3 -> single-strand UMI ~1e-4/1e-5 -> duplex <1e-7), the CLSI EP17 LoB/LoD/LoD95/LoQ framework, the per-locus-vs-panel-integrated LoD distinction that lets bespoke MRD reach ppm, contrived/SEQC2 reference standards, and honest LoD reporting conditioned on input mass + consensus depth + replicate detection rate. Use when stating or trusting a sensitivity claim, designing a dilution-series validation, deciding how many genome equivalents are needed at a target VAF, choosing a single-locus vs panel-integrated LoD, or auditing a "detects 0.1% VAF" claim.

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

Use when CPU usage is high, memory grows unboundedly, goroutines leak, mutex contention shows in traces, or escape analysis suggests excess heap allocation. Triggers: net/http/pprof endpoint exposure, go tool pprof analysis, flamegraph generation, allocs vs inuse_space heap profiles, runtime/trace event timeline, mutex profiling, block profiling, goroutine dumps, GC pressure measurement. NOT for non-Go languages, distributed tracing (use OpenTelemetry skill), or production telemetry pipelines.

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

Determines whether bone mineral density (BMD) measurement is indicated when patients have osteoporosis risk factors or have discontinued sex hormone therapy following gonadectomy. Clinical triggers include documented osteoporosis risk factors (e.g., low body weight, glucocorticoid use, prior fracture) or cessation of sex hormone therapy after surgical gonadectomy.

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

This skill recommends measuring late-night salivary or serum cortisol to screen for Cushing's disease recurrence in patients with eucortisolism after transsphenoidal surgery, including cases where eucortisolism was established by medical treatment prior to surgery. Use when postoperative follow-up shows eucortisolism (normal morning cortisol/UFC) but concern for recurrence exists.

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

This skill outlines monitoring of mineralocorticoid replacement in primary adrenal insufficiency, focusing on clinical assessment of salt craving, postural hypotension, or edema alongside serum electrolyte measurements. It is initiated when evaluating patients on fludrocortisone therapy to ensure adequate dosing and avoid over- or under-replacement.

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

Recommends against using a random cortisol level to diagnose adrenal insufficiency. Triggers when considering a random cortisol test for AI evaluation (e.g., "random cortisol measurement being considered for AI diagnosis").

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

Applies serum cortisol cutoffs (<3 μg/dL indicates central adrenal insufficiency; >15 μg/dL likely excludes it) when evaluating morning cortisol for suspected adrenal insufficiency. Triggers include morning cortisol measurement in suspected AI and use when interpreting morning cortisol levels for adrenal insufficiency workup.

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

Mint a new YYYY-MM-DD-exact-coding-baseline snapshot under research/workflow-dev/export/. Detects the current best correctness- oriented workflow from research/workflow-dev/workflow-construction.md (or takes an explicit source-workflow argument) and transforms it from a lab workflow into a consumer-ready one on three axes: strips lab-only measurement content, re-enables human-in-the-loop checkpoints, and converts auto-loading config into an explicitly-invoked skill. Supports both promoted EXACT Coding lines: Opus/Hybrid and SOL/Predictive TDD. Exports Claude Code, pi, OpenCode, cursor-agent and, for SOL, Copilot. Trigger when the user says "exact-coding baseline export", "neue exact-coding baseline", "exact-coding-baseline-export", or asks to refresh the baseline snapshot.

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

Expert-level quantum mechanics knowledge. Use when working with wave functions, Schrodinger equation, quantum states, operators, uncertainty principle, quantum tunneling, spin, angular momentum, perturbation theory, or quantum entanglement. Also use when the user mentions 'wave function', 'Schrodinger', 'Heisenberg', 'quantum state', 'eigenvalue', 'superposition', 'tunneling', 'spin', 'Hilbert space', 'Dirac notation', 'commutator', or 'quantum measurement'.

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

Write what the work found into the project's knowledge record, so the next session inherits it instead of re-deriving it. Use the moment something worth keeping exists: a fact taken from a source, a rule worked out, a decision or conclusion, a measurement, a correction to a recorded value, or a question left open - and check for unrecorded findings before implementation, handoff (including a PR), or finishing work. Record within the user's write authorization. The first write creates GROUNDING.yaml. Covers one-report update, add, set, review, same and distinct, judgments with a falsifier, and background capture.

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

Measure real frontend performance — Core Web Vitals (LCP, CLS, INP), page-load traces, CPU and network throttling, Lighthouse accessibility/SEO scores, and heap growth — using chrome-devtools-mcp against a live browser. Trigger when asked "is the page fast enough", "measure Core Web Vitals", "why is this route slow", "run Lighthouse", "check for a memory leak", before any performance-gated certification (Built for Shopify, Core Web Vitals thresholds, store listing review), and before any launch or traffic-multiplier event. Measurement only — this skill never drives functional journeys.

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

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do...

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

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do ...

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