「diagnostic」の検索結果

This skill recommends against initiating treatments aimed at normalizing cortisol or its action when only borderline biochemical abnormalities of the hypothalamic-pituitary-adrenal (HPA) axis are present without specific signs of Cushing's syndrome. Use when encountering borderline urinary free cortisol, late-night salivary cortisol, or dexamethasone suppression test results without classic Cushingoid features; triggers include borderline UFC (1-2× ULN), equivocal late-night salivary cortisol, or nondiagnostic low-dose DST.

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

Work up a patient with confirmed hypercalcemia using the PTH-dependent vs. PTH-independent algorithm — order the right second-tier tests (PTHrP, 25(OH)D, 1,25(OH)2D, SPEP/UPEP, urinary calcium/creatinine clearance ratio, TSH) to reach a diagnosis. Trigger when a clinician asks "what's causing this hypercalcemia", "how to work up high calcium", "what tests to order for hypercalcemia", "PTH is normal what next", "differential diagnosis of hypercalcemia", or shares a confirmed hypercalcemia and asks for the workup.

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

Recommends ACTH stimulation during AVS to improve success rate of bilateral selective catheterization, acknowledging unclear impact on diagnostic accuracy for laterality. Triggers include when setting up AVS and asking 'Should I administer ACTH?' or considering procedural optimization.

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

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 diagnostic testing to exclude primary adrenal insufficiency (PAI) in acutely ill patients presenting with otherwise unexplained volume depletion, hypotension, hyponatremia, hyperkalemia, fever, abdominal pain, hyperpigmentation, or hypoglycemia (especially in children). Use when clinical suspicion arises from these suggestive signs or symptoms suggestive of PAI.

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

Recommends measuring serum cortisol levels at 8–9 AM as the first-line test for diagnosing central adrenal insufficiency. Use when starting diagnostic workup for suspected adrenal insufficiency; triggers include suspected adrenal insufficiency requiring initial cortisol testing.

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

Forensic root cause analyzer for Antigravity sessions. Classifies scope deltas, rework patterns, root causes, hotspots, and auto-improves prompts/health.

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

Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.

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

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

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

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

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

Use when deciding what earns a page — the page, action and info classes stated provider-neutrally, and the rule that a page without an owner, a runbook and a first diagnostic step is malformed.

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

Quando o usuário quer auditar, revisar ou diagnosticar problemas de SEO no seu site. Também use quando o usuário menciona "auditoria de SEO," "SEO técnico," "por que não estou ranqueando," "problemas de SEO," "SEO on-page," "revisão de meta tags," ou "verificação de saúde de SEO." Para construir páginas em escala visando palavras-chave, veja programmatic-seo. Para adicionar dados estruturados, veja schema-markup.

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

Create or repair a project-local Inspector profile after INSPECTOR_PROFILE_REQUIRED, INSPECTOR_PROFILE_INCOMPLETE, INSPECTOR_PROFILE_INVALID, or PROFILE_AUTHORING_REQUIRED, using Unity component source, custom Inspector evidence, serialized surfaces, and validation diagnostics.

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

Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.

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

Use when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

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

Design and implement unit, conformance, integration, timing, boot, trace, video, audio, and regression tests for EMULATORS processors, chips, peripherals, and complete machines. Use when creating a verification strategy for a new emulator, converting hardware documentation into tests, adding diagnostic programs or golden artifacts, measuring behavioral coverage, or proving that components interact correctly.

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

Foundational ethics, authority hierarchy, and structural principles for the Predicate agent. Always-on law (composable system-prompt core): Truth>Harmony, Evidence>Authority, Halt>Assumption, Outcomes>Process — four ordered principles that govern every walk. Reference (by-moment): conflict resolution, ethics adjudication, novel situations, precedence walkthrough, entropy diagnostics, principled resistance. Trigger (reference depth): resolving rule conflicts, ethics calls, novel situations. Prompt contains: constitution, principles, precedence, truth over harmony, outcomes over process, evidence over authority, principled resistance.

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

Symptom → root-cause lookup table for nuxt-crouton's recurring failure modes — exact error strings mapped to their known cause, fix, and evidence issue. Use when you hit an error you don't recognize in this repo, before debugging from first principles. Trigger phrases and symptoms: "Cannot resolve entry module .nuxt/hub/db/schema.entry.ts", "Could not load '@fyit/crouton'", "No migrations present", "No schema files found", "$setup.t is not a function", "does not provide an export named 'Map'", "no such table: translations_ui", "collection pages 500 in production", "the build was green but the app is broken", "is this a known issue?".

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

Recreate the nuxt-crouton dev environment from scratch and survive its install/build traps — the pnpm toolchain, the cold-start sequence (why packages must build before apps prepare), the version catalog and workaround pins, the per-app typecheck rule, required env vars, and the known environment traps. Use when setting up a fresh clone/worktree, when "pnpm install" or "nuxt prepare" fails, when an app won't boot after install, when typecheck output looks insane, or when a tool "isn't available". Trigger phrases: "set up the repo from scratch", "why does typecheck show thousands of errors", "playwright install fails", "what pnpm/node version". (Exact error strings — "Could not load '@fyit/crouton'", "Cannot find module '@vue/compiler-sfc'" — route via crouton-diagnostics-index first; it points back here for depth.)

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

The case-law chronicle of this repo's major failures — symptom, root cause, evidence, status, and the rule each battle minted — so nobody re-fights a settled battle or re-proposes a rejected fix. Use when a bug/incident looks familiar ("didn't this happen before?"), when you're about to propose an approach that may have been tried and rejected (e.g. shipping a migration from a package), when someone asks "why does rule X exist" / "why is done-by-lgtm a thing" / "what was incident 988", or when a bug-archaeology run hits the shallow-clone wall and needs the pre-June-2026 history. Trigger phrases: "has this broken before", "why can't packages ship migrations", "why did graduation fail", "why is the green-build lesson a rule", "what did we learn from incident NN". (For a live "build is green but the app is broken" symptom, start at crouton-diagnostics-index. NB keep this description free of any space-then-hash sequence — an unquoted YAML scalar treats space-hash as a comment start and silently truncates.)

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

Use when adding logging, metrics, tracing, or alerting to production code, or when a past incident lacks diagnostic data.

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

VRIO resource analysis combined with Dynamic Capabilities assessment. Use this skill to identify real competitive advantages (Barney VRIO framework), then test whether the organisation can sense new opportunities, seize them, and transform itself to stay ahead (Teece dynamic capabilities). Runs in three modes — full diagnostic for deep first-use sessions, review mode for quick re-assessment, and alert triggers for defining early-warning signals. Updates company-context.md after every run. Triggers on questions about competitive advantage, defensibility, resource assessment, why competitors are gaining ground, organisational agility, or whether advantages will hold. Based on practice by Eterdis (eterdis.com).

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

Wardley Mapping for strategic positioning — map your value chain from customer need to underlying components, plot where each component sits on the evolution curve (novel to commodity), and spot the strategic plays that movement creates. Use this skill when someone wants to understand where their industry is heading, whether they're building things they should be buying, where competitors are vulnerable, what's about to become commoditised, or why their competitive advantage is eroding. Triggers on questions about build-vs-buy, component evolution, value chain analysis, commoditisation risk, or strategic positioning relative to market movement. Three modes — full diagnostic (build a map from scratch), review (update positions and reassess), and alert triggers (set tripwires for when components move). Based on practice by Eterdis (eterdis.com).

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

First-principles strategy — strip away conventional assumptions and find the theoretical maximum for your business. Three modes. Diagnostic mode runs a full session (45+ min) to define your theoretical maximum, map the gap honestly, classify constraints, invert for failure modes, set strategic intent, and work backwards to your first intervention. Review mode (15-20 min) checks whether your theoretical maximum has shifted, whether the gap has changed, and whether you're still climbing the right peak. Alert mode defines constraint-shift, peak-shift, and local-peak triggers that tell you when to reassess. Use when someone is stuck optimising incrementally, when conventional wisdom is driving strategy, when a new technology or regulation changes what's physically possible, or when you suspect the business is climbing a local peak. Integrates with company-context.md. Based on practice by Eterdis (eterdis.com).

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