「orr」の検索結果

Identify differentially accessible chromatin regions across conditions using DiffBind, csaw, DESeq2, or edgeR. Use when comparing ATAC-seq accessibility between treatment groups, choosing between consensus-peak vs sliding-window approaches, picking the correct normalization (full library vs reads-in-peaks), correcting batch with SVA/RUVseq, or interpreting log2FC and FDR thresholds in a chromatin context.

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

Analyze TF motif accessibility variability across samples or single cells using chromVAR. Use when identifying TF motifs whose accessibility correlates with conditions, computing per-sample motif z-scores after matched background correction, comparing to ArchR / Signac equivalents, or distinguishing motif-accessibility signal from per-site footprinting.

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

Classify the severity of hypercalcemia at the bedside — mild, moderate, or severe — by combining the corrected/ionized calcium level with the acuity and symptom pattern, and decide whether the patient needs urgent therapy. Trigger when a clinician asks "is this hypercalcemia severe", "how bad is this calcium level", "when to admit for hypercalcemia", "is this hypercalcemic crisis", "how to grade hypercalcemia", or shares a calcium level and asks how worried to be.

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

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.

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

Expert-level communications engineering covering modulation, channel capacity, error correction, wireless systems, OFDM, MIMO, and 5G technologies.

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

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'.

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

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

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

Paste a URL/snippet before you borrow it — detects its license, runs the derived compatibility policy, and drafts a provenance ledger entry — even before any code is written, not after

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

Otimize Core Web Vitals (LCP, INP, CLS) para melhor experiência de página e ranking de busca. Use quando solicitado para "melhorar Core Web Vitals", "corrigir LCP", "reduzir CLS", "otimizar INP", "otimização de experiência de página" ou "corrigir deslocamentos de layout".

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

Discipline for repairing a false claim once it has propagated: select what depends on it, produce a replacement, and accept with an expiring verdict. Trigger when: - A claim, citation, premise, or documented fact is found wrong and its downstream consequences must be traced and fixed. - A refutation, a failed re-run, a retracted external source, or a human correction lands against something already closed or already promoted. - Prompt contains: /remediation, remediation, retraction, false claim, propagated error, scrub, correction propagation, born-false, became-false, currency verdict, impeachment queue.

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

Deploy MISP (Malware Information Sharing Platform) to aggregate, correlate, and distribute threat intelligence feeds from multiple sources for centralized IOC management and automated SIEM integration.

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

Build effective detection rules using Splunk Search Processing Language (SPL) correlation searches to identify security threats in SOC environments.

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

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports. Activates for requests involving SBOM analysis, software composition analysis, supply chain security assessment, dependency vulnerability scanning, CycloneDX/SPDX parsing, or CVE correlation.

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

Leverages Splunk Enterprise Security and SPL (Search Processing Language) to investigate security incidents through log correlation, timeline reconstruction, and anomaly detection. Covers Windows event logs, firewall logs, proxy logs, and authentication data analysis. Activates for requests involving Splunk investigation, SPL queries, SIEM log analysis, security event correlation, or log-based incident investigation.

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

システムログを分析してエラーの根本原因を特定し、段階的に深堀りしていくデバッグ専門家スキル。 アプリケーションログ、システムログ、クラウドサービスログなど様々な形式に対応。 5 Whys、タイムライン分析、Fishbone分析などのRCA（根本原因分析）手法を用いて 問題の本質を突き止め、再発防止策まで提案する。 Use when analyzing system logs to find error root causes, debugging application issues, or performing technical post-mortem analysis with log data. For organizational incident management processes (post-incident review, corrective action plans, incident reports without log data), use incident-rca-specialist instead. Triggers: "analyze this log", "find the root cause", "debug this error", "why is this failing", "log analysis", "what caused this crash", "troubleshoot this issue"

Use this skill for critical code review that focuses on whether the code actually works correctly and achieves the expected results - not just whether it matches a design document. This skill assumes designs can be wrong, finds bugs the design didn't anticipate, and verifies end-to-end correctness. Triggers include "critical code review", "deep code review", "verify this implementation works", "find bugs in this code", or reviewing implementation against requirements. NOTE - Security review is OUT OF SCOPE; use a dedicated security review skill for that purpose.

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

Use when diagnosing a repeated conceptual mistake and designing a targeted correction loop to replace the faulty mental model.

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

Review+fix protocol with optional pre-core git diff review and safety guardrails (unsoundness, invariants, footguns, incidental complexity). Use when prompts say "/tw-fix this PR", "fix current branch", "fix this diff", "repair CI red", or "apply a minimal patch", and when crash/corruption/invariant-break issues need correction with a validation signal. Stop only after self-review exhausts actionable changes, each full cycle reaches post-self-review rerun plus terminal diff-review closure, and two consecutive zero-edit full cycles are clean.

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

METAINFORMANT rules for directory cursorrules. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.

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

Ordnet Büroaufgaben, Korrespondenz und Fristen ohne Bindung an eine bestimmte Office-App.

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

Builds a DRAFT month-end, quarter-end or year-end close checklist and status table for a finance team from the close calendar, the open items list and last month's close issues that the user attaches, pastes or the agent can reach, marks every task on time, due, late, at risk or blocked, and flags dependency chains and repeat issues. Use when the user asks to "build the close checklist", "where are we on the month-end close", "what is late or blocked in the close", "refresh the close tracker as of today" or "prepare the close status note". Do not use for a project tracker or weekly project status, use project-status-tracker instead; for corrective actions from audits or NCRs, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

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

Coach German writing and conversation with minimal corrections, persistent root-cause mistake tracking (FehlerDNA), mistake-based spaced repetition with a new sentence every time, roleplay whose words return in spaced reviews, continuing preparation for real-life goals across sessions, and an honest progress profile. Use for German correction, personalized review, vocabulary, progress, roleplay, or preparation for an interview, presentation, appointment, or other concrete event; do not use for translation-only requests without learning or feedback.

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

Use WooCommerce's customer and session APIs correctly — WC ships its own session handler (WC_Session_Handler, single wp_woocommerce_sessions table for both guests and logged-in users) and its own customer object (WC_Customer via WC()->customer), separate from $_SESSION / native PHP sessions / wp_get_current_user. AI consistently reaches for $_SESSION (breaks with page caching, setcookie (no signing, no namespacing), or user_meta for guests (impossible). The correct path is WC()->session->set/get for ephemeral per-visitor data, WC()->customer->get_billing_* for the active customer context including guests, and new WC_Customer($user_id) for one-off loads. Important — WC()->session is auto-initialized only on frontend requests (incl. admin-ajax); REST, cron, and WP-CLI must call wc_load_cart() explicitly. Use when storing per-visitor state, reading the current visitor's billing data, or debugging session loss across page caches / REST / cron. Triggers on WC_Session, WC_Session_Handler,...

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

Audits WordPress plugin or theme PHP code for internationalization (i18n) correctness — text-domain consistency, use of escaped translation helpers (esc_html__, esc_attr__, esc_html_e), correct placeholder helpers (sprintf with translator comments, _n for plurals, _x for context), no variable text-domains, no concatenation inside __() calls, presence of load_plugin_textdomain or load_theme_textdomain, and matching declared Text Domain in the plugin/theme header. Use before plugin/theme release, when reviewing contributor PRs, when adding new strings, when migrating to a new text domain, or when a translator reports issues with the .pot file.

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