'unit' 검색 결과

Run Unity Test Runner and report detailed results. Use for EditMode/PlayMode tests, change verification, or failure diagnosis.

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

Find or inspect Unity GameObjects, especially objects the user currently selected in the Hierarchy. Use for details, components, tags, layers, or name/path searches.

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

Use when Unity Editor is not running or needs a clean restart.

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

Clear Unity Console entries. Use before compile, tests, or debugging when stale logs would hide the current result.

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

Simulate keyboard input in PlayMode through Unity Input System. Use for key presses, holds, releases, and game controls such as WASD or Space.

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

Control Unity Editor Play Mode. Use to start, stop, or pause Play Mode for runtime behavior checks and frame inspection.

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

Execute C# with Unity APIs when existing uloop tools cannot inspect or edit enough. Use for scene, prefab, SerializedObject, AssetDatabase refresh/.meta generation, menu, or PlayMode automation.

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

Read current Unity Console entries from a running Editor. Use during bug investigation after compile, tests, PlayMode, or dynamic code to inspect logs, warnings, errors, and stack traces.

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

Get the Unity scene hierarchy as a structured tree. Use for parent-child structure, descendants, roots, or subtrees under objects the user currently selected.

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

Build kokoro-js-jp and run its real-browser e2e suite (Worker + WASM openjtalkjs g2p + ONNX kokoro-js synthesis, English and Japanese). Use when asked to verify this package actually works in a browser, to check whether a change broke synthesis, or to add browser-level regression coverage for a bug in the g2p/synthesis pipeline that vitest's pure-function tests can't catch. Not for typecheck/lint/unit-test requests — use npm run typecheck / npm test for those.

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

Use when preparing Australian managed-fund or ETF annual-tax-statement, AMIT/AMMA attribution and unit cost-base adjustment workpapers.

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

Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers, implementing Sanctum auth flows, building Livewire components, optimising Eloquent queries, or writing Pest/PHPUnit tests for Laravel features.

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

Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invokes strict typing, PHPStan level 9, async patterns with Swoole, and PSR standards. Creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects, sets up dependency injection, and scaffolds REST/GraphQL APIs. Use when working with Eloquent, Doctrine, Composer, Psalm, ReactPHP, or any PHP API development.

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

Compare cell-type composition and spatial features across conditions in IMC/MIBI cohorts with the patient as the experimental unit, covering pseudoreplication, per-patient aggregation, mixed models, compositional (Dirichlet/scCODA) differential abundance, diffcyt, per-image-to-patient spatial differential testing (SpaceANOVA), batch covariates, and FDR. Use when testing whether a cell type or spatial niche differs between groups, avoiding cell-level pseudoreplication, choosing a differential-abundance method, or correctly powering an IMC cohort comparison.

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

Assesses genetic health of populations for conservation with Ne estimation across time horizons (LDNe NeEstimator V2 option-file API + SNeP physical-linkage correction; recent trajectory via GONE/GONE2; deep history via Stairway Plot 2 / dadi / fastsimcoal2 / PSMC), F-statistics, runs of homozygosity binned by length class to date inbreeding, genetic-load decomposition (Bertorelle 2022 realized vs masked), the modern 100/1000 Ne rule (Frankham 2014), Ne/Nc 2-6 orders of magnitude in marine fish (Hauser & Carvalho 2008), tree-sequence forward simulations (SLiM 4 + pyslim + tskit), and the Sukumaran-Knowles caveat against MSC methods for management-unit definition. Use when estimating Ne by time horizon, detecting inbreeding via F_ROH, decomposing genetic load, justifying conservation thresholds, distinguishing ESU/MU/DPS, configuring NeEstimator V2, or correcting LDNe physical linkage.

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

Designs genomics experiments so technical nuisance variation (batch, lane, plate, flow cell, operator, reagent lot, processing day) is balanced against the biological variable of interest and therefore estimable rather than confounded, using constrained sample-to-batch assignment (designit, OSAT), the confounder/mediator/collider distinction, and the principle that no post-hoc correction recovers a fully confounded design. Covers detecting hidden batches with surrogate variable analysis, a decision table for downstream correction (ComBat-seq, RUVSeq, SVA) whose execution is deferred to differential-expression/batch-correction, and reproducibility metadata. Use when assigning samples to sequencing batches/lanes/plates, avoiding batch-condition confounding, deciding whether a design is salvageable by correction, choosing a correction method, or estimating the number of hidden batches. For the experimental unit, randomization, and blocking concepts see experimental-design/randomization-blocking.

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

Differential abundance (DA) and differential state (DS) analysis for flow and mass cytometry - tests which cell populations change in frequency or marker expression between conditions using diffcyt (edgeR/voom/GLMM for DA, limma/LMM for DS), with cydar, CITRUS, and compositional methods (sccomp, scCODA, DCATS) as alternatives. Covers the sample-is-the-experimental-unit principle, design/contrast and mixed-model formulas, compositionality of cluster proportions, and FDR across clusters. Use when comparing populations between groups, choosing a DA method, handling paired/batch designs, or deciding whether compositional correction is needed.

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

Visualize biological networks (PPI, gene-regulatory, co-expression, pathway) with layout algorithm choice (ForceAtlas2, Fruchterman-Reingold, Kamada-Kawai, hive plots), edge bundling, community-based coloring, and reproducible seeds using NetworkX, PyVis, igraph, and Cytoscape automation. Use when rendering biological networks for static publication, interactive HTML exploration, or Cytoscape-format export.

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

Generate a structured test plan for a feature or module — covers unit, integration, contract, and edge cases without writing implementation code.

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

Use when writing tests of any kind — unit, slice, or integration. Covers test structure, naming conventions, Mockito patterns, @WebMvcTest, @DataJpaTest, and Testcontainers setup.

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

Generate a structured test plan for a feature or module — covers unit, integration, contract, and edge cases without writing any implementation code.

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

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.

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

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

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

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

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