データ分析、機械学習、LLMアプリ、プロンプト設計（9,090 件）
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 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 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 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 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 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 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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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'.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Unity ScriptableObject patterns for data management, configuration, and runtime systems.
日本語の概要は準備中です。原文の説明を表示しています。
Unity 6 ECS/DOTS development guide. Use when working with Entity Component System, data-oriented design, Jobs system, or Burst Compiler. Covers Entities, IComponentData, ISystem, EntityManager, baking, Jobs, and Burst. Based on Unity 6.3 LTS documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Unity 6 AI and navigation guide. Use when working with NavMesh, pathfinding, NavMeshAgent, NavMeshSurface, NavMeshObstacle, off-mesh links, or Unity Sentis (ML model inference). Covers AI navigation package, runtime NavMesh baking, and common AI patterns like state machines and behavior trees. Based on Unity 6.3 LTS documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Unity 6 physics development guide. Use when working with Rigidbody, colliders, raycasting, triggers, collisions, joints, or physics simulation. Covers PhysX 5 (3D) and Box2D (2D) physics, FixedUpdate timing, layer masks, and contact data. Based on Unity 6.3 LTS documentation.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a feature before writing any code. Use this skill at the START of non-trivial feature work — when the user says they want to "add", "build", "implement", "create", "develop", or "ship" a feature, endpoint, component, page, service, or capability. Especially trigger when the user's prompt is short or under-specified ("add a dashboard", "build an auth flow", "let's do user activity reports") — those need planning, not direct execution. The skill walks through requirements clarification, codebase exploration, sketches a Mermaid architecture/flow diagram of the proposed design, and produces a plan.md document the user can hand off to a fresh AI session for execution. Skip only when the change is genuinely trivial (typo fixes, single-line tweaks, renames). When in doubt, plan.
日本語の概要は準備中です。原文の説明を表示しています。