'plan' 검색 결과

Simulate transcription factor perturbation effects on cell state in silico with CellOracle and Dynamo, and predict transcriptional responses to genetic perturbations with GEARS, scGen, and CPA. Covers the direction-not-magnitude principle, local-linear validity, the GRN/velocity error it inherits, baseline discipline (mean and additive baselines), and the validation gap. Use when predicting TF knockout or overexpression effects, ranking driver TFs for fate transitions, or planning perturbation experiments. For GRN construction see multiomics-grn; for experimental Perturb-seq see single-cell/perturb-seq.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Query the Ensembl REST API for gene/transcript/protein lookup, sequence retrieval, comparative genomics (Compara), variant effect prediction (VEP), regulatory features, and cross-species ortholog/paralog calls. Use when pulling Ensembl-native data (Ensembl Gene IDs, version-pinned releases, archive endpoints for reproducibility), gene/transcript/exon structure with stable IDs, or VEP for variant annotation. Encodes the 15 req/sec rate limit, archive (e110.rest.ensembl.org) for reproducibility, Ensembl divisions (vertebrates / plants / fungi / metazoa / bacteria), and the symbol-vs-ID stability problem.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Calls HLA class I and class II alleles at 2/4/6/8-field resolution from WGS/WES/RNA-seq/long-read data using OptiType, HLA-LA, T1K, Polysolver, HLA-HD, arcasHLA, StarPhase, or HIBAG imputation. Use when typing for HSCT, solid-organ transplant, neoantigen prediction, PGx screening (B*57:01, B*15:02, etc.), or disease-association studies, with reconciliation across tools and IPD-IMGT/HLA version mismatch handling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs adaptive clinical trials including group-sequential (O'Brien-Fleming, Pocock, Lan-DeMets spending), sample-size re-estimation (blinded Friede-Kieser, unblinded Cui-Hung-Wang, Mehta-Pocock promising zone), seamless Phase 2/3 with treatment-arm selection, population enrichment, and response-adaptive randomisation. Covers FDA 2019 Final Adaptive Designs Guidance, FDA 2022 Master Protocols, and ICH E20 Step 2b/3 draft (June 2025, NOT final). Use when planning interim analyses, sample-size re-estimation, or master/platform-trial designs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validates docked / generated protein-ligand poses using PoseBusters physical-validity tests, strain energy quantification, geometric checks (planarity, vdW overlap, bond/angle distortion), and pose-energy reasonableness. Filters AI-docking outputs (DiffDock, EquiBind, NeuralPLexer) where ~50% of poses fail physical-validity tests. Use when QC-ing docking results, comparing classical vs ML docking outputs, or filtering pose lists before SAR analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs PROTACs, molecular glues, and bivalent degraders with explicit handling of E3 ligase choice (VHL, CRBN, IAP, MDM2, KEAP1), linker design (length, composition, rigidity), ternary complex prediction (PRosettaC, DeepTernary, AlphaFold3 with constraints), cooperativity (alpha), DC50 / Dmax characterization, hook effect, and prediction-experiment reconciliation. Use when designing targeted protein degraders, planning linker SAR, predicting ternary complex stability, or building generative degrader workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyzes chemical libraries by scaffold using Bemis-Murcko scaffolds, generic frameworks, cyclic skeletons, matched molecular pair (MMP) analysis via mmpdb, R-group decomposition, Free-Wilson analysis, scaffold hopping, and chemotype-aware ML train/test splits. Use when identifying chemotype clusters in a library, deriving SAR transformation rules, decomposing series into R-groups, performing scaffold-balanced QSAR splits, or planning analog campaigns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when users need bioinformatics analysis on the NCPGR cluster, especially when converting analysis requests into local software choices, resource plans, and LSF job scripts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks about getting/maintaining motor carrier operating authority — USDOT number, MC number, BOC-3 process agent, insurance filing (MCS-90, BMC-91/91X), Unified Carrier Registration (UCR), International Registration Plan (IRP), International Fuel Tax Agreement (IFTA), state-level permits (NY HUT, KY weight distance, OR weight-mile, NM weight distance), new entrant safety audit, intra vs interstate, for-hire vs private. Cite 49 CFR 365, 387, 390.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a driver has been involved in a crash — regardless of preventability or injury — and the carrier needs to handle the immediate, post-investigation, and return-to-work phases. Covers trauma response, post-accident testing under 49 CFR 382.303, paid time off, retraining, light duty, and re-entry planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks the cost of pulling a Motor Vehicle Record (MVR) in a specific state, or wants to compare MVR fees across multiple states, or is budgeting annual compliance costs for a multi-state fleet. Reference the canonical fee table below; flag that fees change (re-verify with state DMV before annual budget planning).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when an owner-operator (1099 or LLC/S-corp) asks how to lower their tax bill, what they can deduct, per diem treatment, depreciation choices (Section 179, bonus, MACRS), quarterly estimated payments, S-corp salary vs distributions, retirement plan options (SEP-IRA, Solo 401(k)), or recordkeeping requirements. Covers federal income tax + self-employment tax basics; not state-specific.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to understand the International Registration Plan (IRP). Covers when you need to register apportioned, how it differs from IFTA, and quarterly fees.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks about hazardous materials (hazmat) transportation under 49 CFR 171-180 — placarding requirements, segregation tables, hazmat employee training (49 CFR 172 Subpart H), Hazmat Safety Permit (HMSP), shipping papers, packaging groups, emergency response phone, security plans, hazmat endorsement on CDL, and bulk vs non-bulk distinctions. Cite specific 49 CFR section.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to understand the geographic patterns of FMCSA inspections. Covers high-inspection states, why they're high-inspection, and operational planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a driver has been disqualified or is at risk of disqualification — major offense convictions (DUI, leaving the scene, drug trafficking with CMV), serious traffic violations, RR-grade-crossing violations, imminent-hazard out-of-service, or Clearinghouse positive-test prohibited status. Also use when planning a return-to-duty pathway, SAP process, or reinstatement timeline. Covers 49 CFR 383.51, Part 40 Subpart O, and Part 391.15.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when discussing the mobile apps drivers use day-to-day — load boards (DAT, Truckstop), route planners (Trucker Path, CoPilot Truck), expense and per diem apps (Per Diem Plus), parking apps (Park My Truck), maintenance / DVIR apps, and how these stack with the carrier's ELD app.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a fleet manager or owner asks when to replace tractors and trailers, optimal trade cycle age, total cost of ownership analysis, residual value timing, dealer-vs-auction sale strategy, and how trade cycle affects driver retention and operating cost.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks about the agricultural exemption from Hours of Service (HOS) rules under 49 CFR 395.1(k) — what qualifies as agricultural commodity, the 150-air-mile radius rule, state-declared planting/harvest seasons, livestock hauling specifics, and how to document operations under the exemption. Cite 49 CFR 395.1(k) and 49 USC 5117.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan and diagnose FIPA-style ontology-service interactions while keeping declared ontology relations, provider capability, and application authorization separate. NOT for treating an ontology mapping as provider authority or guaranteed interoperability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Structure persuasive speeches and formal arguments in forensic, legal, policy, and competitive debate styles. Use when the user needs to prepare talks, opening or closing arguments, policy pitches, public explanations, debate speeches, or mentions 'forensic speech', 'formal argument', 'persuasive speech structure', 'debate speech', 'opening statement', 'closing argument'. Turns structured claims into audience-tuned persuasive delivery.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for sensemaking, frame revision, anomaly handling, questioning strategy, and ambiguity diagnosis with the Data/Frame model before action is chosen. NOT for deterministic classification, settled execution planning, or situations where the frame is already stable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.