「rca」の検索結果

This skill suggests using denosumab rather than an intravenous bisphosphonate for adults with hypercalcemia of malignancy. It is triggered when a clinician questions which antiresorptive to choose first or seeks guidance on drug selection for HCM.

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

The skill suggests adding a calcimimetic for hypercalcemia of malignancy due to parathyroid carcinoma that persists after intravenous bisphosphonate or denosumab therapy. It is triggered when a clinician notes refractory HCM despite antiresorptive therapy and considers adding a calcimimetic.

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

This skill categorizes hypercalcemia of malignancy (HCM) severity using albumin‑adjusted serum calcium into mild (<12 mg/dL), moderate (12‑14 mg/dL), or severe (>14 mg/dL). Use it when a clinician needs to stage HCM to guide initial therapy choices, such as deciding between observation, IV bisphosphonate/denosumab, or calcitonin‑based combination regimens.

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

Recommends adding intravenous bisphosphonate or denosumab when hypercalcemia due to parathyroid carcinoma is not adequately controlled with a calcimimetic. Consider this adjunct when a clinician notes persistent HCM despite calcimimetic therapy and asks about next-step therapy.

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

The guideline suggests checking serum magnesium and phosphate levels and repleting if low in patients receiving antiresorptive therapy for hypercalcemia of malignancy. Clinicians should consider this when they note electrolyte abnormalities or inquire about supportive care during bisphosphonate or denosumab treatment.

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

Computes albumin‑adjusted (corrected) serum calcium using total calcium and albumin to adjust for hypo‑ or hyperalbuminemia. Triggered when a clinician notes hypoalbuminemia and requests corrected calcium to assess true hypercalcemia of malignancy severity.

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

Determines the appropriate IV pamidronate dose (60‑90 mg) and infusion duration (2‑24 h) for adults with hypercalcemia of malignancy based on renal function. Triggered when a clinician orders pamidronate and asks how to adjust for kidney dysfunction (eGFR < 60 mL/min/1.73 m²).

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

Determines the appropriate zoledronic acid dose (3‑4 mg IV) and infusion duration based on renal function. Triggered when a clinician prepares to prescribe zoledronic acid for hypercalcemia of malignancy and asks about renal‑adjusted administration.

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

Calculates salmon calcitonin dose based on patient weight for rapid calcium lowering in hypercalcemia of malignancy. Triggered when a clinician considers rapid calcium lowering and asks about weight‑based calcitonin dosing.

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

Recommends adding intravenous bisphosphonate or denosumab in adults with hypercalcemia of malignancy due to tumors with high calcitriol levels (e.g., lymphoma) who remain severe or symptomatic despite glucocorticoid therapy. Use when managing lymphoma‑related HCM on steroids and considering escalation of antiresorptive therapy.

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

Adjusts intravenous bisphosphonate dosing and infusion duration for patients with hypercalcemia of malignancy and renal insufficiency (creatinine clearance <60 mL/min). Triggered when a clinician encounters renal impairment and asks how to modify zoledronic acid or pamidronate infusion rates.

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

Recommends checking and managing vitamin D according to Endocrine Society guidelines to avoid hypocalcemia in patients receiving bisphosphonates or denosumab for hypercalcemia of malignancy. Use when a clinician notes risk factors for hypocalcemia (e.g., low 25‑OH vitamin D, renal insufficiency) and asks about baseline labs before antiresorptive start.

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

Recommends initiating intravenous bisphosphonate or denosumab for adults with hypercalcemia of malignancy compared with no treatment. Use when a clinician asks about first‑line pharmacologic therapy for HCM or when deciding to start antiresorptive agents.

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

Recommends combination of calcitonin and an intravenous bisphosphonate or denosumab as initial treatment for severe hypercalcemia (serum calcium >14 mg/dL). Indicated when a clinician notes severe HCM or seeks rapid calcium lowering in symptomatic patients.

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

Cycle-end retrospective converting recurring judgment failures into durable enforcement. Reviews the cycle's friction — repeated user corrections, guard trips, RCA themes, integrate failures — and turns each recurring one into a landmines.md entry, then proposes graduation candidates up the enforcement funnel (landmine → advisory hook → hard gate). Pairs with standup: standup says what shipped and what's next; retrospective says what kept going wrong and how to stop it structurally. Writes only memory entries and a report — graduation proposals are advisory and require the normal seed.md amendment path to become enforcement. Invoke at the end of a release cycle, an epic, or any stretch of work with repeated friction.

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

Draft or revise English prose for any brief — documentation body, intake problem statements, spec context, RCA summaries, marketing copy, README sections, PR descriptions. Mandatorily invokes `Skill(humanizer)` as the final pass on every draft. Conditionally invokes `copywriting` for persuasive register, `documentation` for reference docs, `technical-tutorials` for tutorials. Used when any phase needs human-readable prose written or rewritten. Composition only — research and register-picking happen in the caller's context.

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

Marc Andreessen-mode decision and productivity skill. A blunt, market-first operator that pressure-tests ideas, ventures, features, and career bets through Andreessen's actual frameworks — market dominates team and product; the only milestone that matters is product/market fit; bias to build over deliberate. Use when the user says 'andreessen', 'pmarca mode', 'should I build this', 'is there a market', 'are we at product/market fit', 'pmf check', 'pressure-test this idea', 'be brutal about this venture', 'market-first take', or wants a no-disclaimers, no-hedging, confidence-leveled verdict on whether something is worth pursuing. Also provides the 3x5-card + Anti-Todo personal productivity routine. Runs on a fixed anti-sycophancy operating prompt: leads with the strongest counterargument, never validates premises, uses explicit confidence levels, never apologizes for disagreeing. Not for polite brainstorming — this skill exists to tell you the market is dead when it is.

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

Up-to-date Zig programming language patterns for version 0.17.0-dev (0.16.0 stable APIs plus the 0.17 deltas). Use when writing, reviewing, or debugging Zig code, working with build.zig and build.zig.zon files, or using comptime metaprogramming. Critical for avoiding outdated patterns from training data - especially std.net→std.Io.net (requires Io instance), std.time timestamps removed (use clock_gettime), std.Thread.Mutex/Condition/sleep removed (use pthreads), std.crypto.random removed, build system APIs (root_module, Compile methods→Module methods), I/O APIs (buffered writer pattern), container initialization (.empty/.init), allocator selection (DebugAllocator), ArrayList now unmanaged by default, @typeInfo lowercase fields (.@"struct" not .Struct), and removed language features (async/await, usingnamespace). Also covers 0.17.0-dev deltas: b.args→run_cmd.addPassthruArgs(), std.gpu→std.spirv, @bitCast logical-bit (endian-agnostic) semantics, build configurer/maker split, and the zig-pkg/ package directory. Also covers quality tooling Zig does not ship: coverage with kcov (and why in-file tests wreck the denominator), detecting unused private functions (neither the compiler nor zlint's unused-decls finds them), duplicate detection with jscpd, zlint (NOT the same-named X.509 linter in Homebrew), and the built-in fuzzer whose testOne now takes *std.testing.Smith rather than []const u8.

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

Quando o usuário quer planejar, avaliar ou construir uma ferramenta gratuita para fins de marketing — geração de leads, valor em SEO ou conscientização de marca. Use também quando o usuário menciona "engenharia como marketing", "ferramenta gratuita", "ferramenta de marketing", "calculadora", "gerador", "ferramenta interativa", "ferramenta de geração de leads", "construir uma ferramenta para leads" ou "recurso gratuito". Esta competência conecta engenharia e marketing — útil para fundadores e profissionais de marketing técnico.

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

Kit de ferramentas de liderança estratégica de produto para Head of Product incluindo geração em cascata de OKRs, análise de mercado, definição de visão e escalabilidade de equipes. Use para planejamento estratégico, alinhamento de objetivos, análise competitiva e desenho organizacional.

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

Skill de pesquisa profunda alimentado por NotebookLM MCP. Conduz pesquisa estruturada em múltiplas fontes (análise de mercado, inteligência competitiva, análise de tendências, pesquisa de prospects) usando Google NotebookLM como mecanismo de pesquisa, depois entrega briefs formatados e artefatos opcionais de estúdio (slides, podcasts de áudio, vídeos, infográficos, relatórios, mapas mentais).

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

Crear, ampliar o actualizar documentación técnica de EMULATORS en formato DOCX usando la plantilla oficial del repositorio, con portada parametrizada, índice, prólogo, capítulos de contenido, anexos, listas de ilustraciones y ecuaciones, marca de agua del autor y pie Página X | Y. Usar cuando Codex deba documentar subsistemas, arquitecturas, dispositivos, modelos, herramientas, compilación, uso, pruebas o cualquier otro aspecto del emulador y el resultado deba conservar la identidad visual de docs/UserGuide.docx.

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

インシデント調査で根本原因を特定するためのなぜなぜ分析ファシリテーター。推測を避け、ユーザーの発言を記録し、マインドツリーで全体を可視化する。障害発生後の原因究明、ポストモーテム、再発防止策の策定に使用する。Do NOT use for 定期的なサービス健全性チェック（health-checkを使用すること）。

Perform root cause analysis on a bug fix. Use when the user says 'run RCA on [commit/PR]', 'root cause analysis', or 'analyze what caused this bug'. Accepts a commit SHA, PR number, issue, or description of a fix.

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