데이터 분석, 머신러닝, LLM 앱, 프롬프트 설계 (9.1천건)
Use when a task needs the judgment of a Chief Data Officer — resolving conflicting metric definitions across dashboards, deciding whether a dataset should be retained or purged, assigning data ownership for a system feeding regulatory or board reporting, sizing a privacy/breach risk against a proposed data collection, or auditing data readiness before an AI/ML initiative kicks off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Clinical Data Manager — designing a CRF/eCRF and edit-check specification, writing or triaging a data query, planning database lock readiness, reconciling external data (lab, ePRO, IRT) against the clinical database, or reviewing a data management plan for a trial.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs senior auto-service-technician judgment — diagnosing a check-engine-light or drivability complaint from DTCs and live data, deciding whether a code-named part actually needs replacing or the fault lies upstream, scoping a flat-rate repair order and labor time, choosing warranty vs. customer-pay job costing, or separating a genuinely needed repair from an upsell.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a biomedical/bioengineering engineer — running a design control phase (inputs, outputs, verification, validation) for a medical device, scoring a Design FMEA and deciding whether a failure mode needs mitigation, planning a human factors/usability validation study, building a design traceability matrix, or writing a design verification or risk-mitigation report. Distinct from a regulatory-affairs-specialist (owns the submission/clearance process, not the engineering itself) and from a clinical-data-manager/biostatistician (trial data and analysis, not device design).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an astronomer — calculating exposure time or signal-to-noise for a target, writing the feasibility math for a telescope-time proposal, reducing photometric or spectroscopic data, distinguishing a systematic error floor from statistical noise, or reviewing an observational result for calibration or upper-limit red flags.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Biochemist — determining enzyme kinetics (Km/Vmax, inhibition mechanism) from rate data, choosing a structural-biology method (X-ray crystallography, cryo-EM, or NMR) for a target, designing or interpreting a binding assay (ITC, SPR, fluorescence polarization), or selecting a protein-purification strategy and diagnosing why a prep failed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a book publisher — sizing an advance against a P&L model before an acquisition auction, setting a print run from comp-title sales data, deciding whether to keep bidding or walk in a multi-house auction, valuing subsidiary rights as part of a deal, or diagnosing why a title's early sell-through is diverging from its launch plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Biostatistician — designing a clinical trial's sample size and analysis plan, choosing a survival-analysis or censoring-aware method, preparing a DSMB safety readout, or judging whether a trial's efficacy claim survives ITT vs. per-protocol scrutiny.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Biology Professor at a research university — writing or defending an NIH/NSF grant budget, deciding authorship order on a paper, navigating an IACUC or biosafety protocol, mentoring a PhD student through a stalled project, or converting a course when active-learning data doesn't match student pushback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Biologist — designing a study and identifying its true experimental unit before data collection starts, running a power analysis to size a sample, judging whether a published or preclinical finding warrants trust without independent replication, sequencing IACUC/IBC/field-permit approvals before biosafety or wildlife work begins, or scoping a grant-funded research plan against realistic funding odds.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a livestock geneticist/animal breeder — selecting a sire against EPDs or genomic data, screening a proposed mating for inbreeding risk, deciding AI versus natural service, timing an estrus-synchronization protocol, or defending a breeding-goal tradeoff to a herd owner.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an Agricultural Technician — designing a soil, tissue, or seed sampling plan, interpreting pest scouting counts against an economic threshold, calibrating spray/seeding equipment, or troubleshooting a field data discrepancy before it reaches the agronomist or scientist who acts on it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an Actuary — estimating unpaid claim reserves with chain-ladder or Bornhuetter-Ferguson methods, building or reviewing a rate indication from loss experience, applying credibility weighting to thin or volatile data, drafting a statement of actuarial opinion, or diagnosing whether a reserve or pricing assumption has stopped matching reality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a Software Design Document (SDD) defining component architecture, data contracts, API schemas, and platform compatibility before planning. Use in Tier 3 (Full Pipeline) or when modifying interfaces, hooks, databases, or multi-platform contracts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Modify asset file in the project. Use 'assets-get-data' tool first to inspect the asset structure before modifying. Not allowed to modify asset file in 'Packages/' folder. Please modify it in 'Assets/' folder.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Get detailed data about a shader asset in the Unity project. Returns shader properties, subshaders, passes, compilation errors, and supported status. Use 'assets-find' tool with filter 't:Shader' to find shaders, or 'assets-shader-list-all' tool to list all shader names.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Get asset data from the asset file in the Unity project. It includes all serializable fields and properties of the asset. Use 'assets-find' tool to find asset before using this tool.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate ScriptableObject-based systems including data containers, event channels, and runtime sets. Use when creating game data (weapons, enemies, items, abilities), cross-system events, or live object tracking. Triggers on requests like "create weapon data", "add an event system", "make a runtime set", "decouple these systems", "create item database", "add a damage event", "track active enemies", "create a config SO", "add game settings data", or any task involving ScriptableObject data containers, event-driven communication, or runtime object tracking. Reads ProjectConfig.yaml -> architecture_pattern to determine SO-first vs DI-first context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unity data-driven design architecture. ScriptableObject config hierarchies, JSON data pipelines, designer handoff workflows, data versioning and migration, Inspector attributes for self-documenting configs. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.