3,529 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.
日本語の概要は準備中です。原文の説明を表示しています。
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
日本語の概要は準備中です。原文の説明を表示しています。
Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Unity NPC behavior design-to-code translation. Perception system architecture, decision layer patterns, action execution pipeline, faction & relationship systems, NPC memory & forgetting, crowd & squad coordination. DESIGN INTENT format: INTENT/WRONG/RIGHT/SCAFFOLD/DESIGN HOOK. Based on Unity 6.3 LTS.
日本語の概要は準備中です。原文の説明を表示しています。
Unity 6 graphics and rendering guide. Use when working with render pipelines (URP, HDRP, Built-in), shaders, Shader Graph, materials, textures, cameras, post-processing, or rendering optimization. Covers Render Graph, batching, draw call optimization, and GPU instancing. Based on Unity 6.3 LTS documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze thermal-fluid engineering systems, experiments, CFD, and correlations with explicit assumptions, validity limits, uncertainty, and mechanism-based interpretation. Use for heat transfer, fluid mechanics, phase change, HVAC, energy systems, turbomachinery, piping, or thermal management.
日本語の概要は準備中です。原文の説明を表示しています。
Apply source-aware mechanical-engineering judgment to research, analysis, coding, writing, teaching, research identity, and release work. Use for thermal-fluid systems, heat transfer, fluid mechanics, thermodynamics, HVAC, energy systems, turbomachinery, piping, multiphase flow, experiments, correlations, CFD, reduced-order models, AI/ML, uncertainty, engineering datasets, literature reviews, citations, manuscripts, reviewer revisions, Overleaf packages, figures, proposals, research software, reproducibility, public releases, engineering teaching materials, or a research-project logo and visual identity.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an English Language and Literature Professor — backward-designing a first-year composition or literature syllabus against a shared outcomes rubric, deciding whether an AI-detection or plagiarism flag on a student essay warrants an integrity case, reading where a tenure case's monograph actually sits in a university press's pipeline, or handling a content complaint about an assigned literary text.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Dredge Operator — selecting cutterhead, hopper, or mechanical dredge type for a given sediment/depth/environmental profile, classifying dredged material for open-water vs. confined disposal from sediment-testing results, tuning hydraulic slurry density against pipeline critical velocity, verifying channel controlling depth against project depth and overdepth tolerance, or setting turbidity-monitoring response during active dredging.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Derrick Operator (derrickhand) — running the monkeyboard during a pipe trip, reading trip-tank volume against calculated displacement for a swab or kick signature, calculating a barite weight-up in sacks, deciding whether a volume anomaly warrants stopping the trip for a flow check, or running the mud circulating system (shakers, desander, degasser) between trips.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a DevOps/Site Reliability Engineer — designing deployment pipelines, setting SLOs/error budgets, responding to or reviewing an incident, or making infrastructure/reliability tradeoffs. Distinct from a backend software engineer role — this one owns the system's operational health across all services, not one service's feature code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a bioinformatics technician — running or QC-gating a next-generation sequencing pipeline, triaging a failed or borderline sequencing run, deciding whether a variant call set is clinically/research reportable, or writing a sample-level QC report.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Advertising Sales Agent — pricing an ad-inventory package against a client budget, building a media-kit pitch, protecting yield on scarce inventory while moving remnant, or forecasting close rate on a sales pipeline. Sell-side: this role sells a publisher's or station's own ad space/time to advertisers, the opposite side of the table from a buyer-side advertising-promotions-manager who purchases media on a client's behalf.
日本語の概要は準備中です。原文の説明を表示しています。
Cross-reference ENCODE data with PubMed, bioRxiv, ClinicalTrials.gov, Open Targets, GTEx, ClinVar, GWAS Catalog, gnomAD, Ensembl, and other scientific databases. Use when the user wants to find publications, preprints, or clinical trials related to ENCODE experiments, chain ENCODE data with other scientific MCP servers, or build translational pipelines from genomic data to clinical application.
日本語の概要は準備中です。原文の説明を表示しています。
Track exact provenance for every operation on ENCODE data — tool versions, reference files, scripts, parameters, and timestamps — to enable publication-ready methods writing. Use when the user processes ENCODE files, runs any bioinformatics tool, creates filtered/merged datasets, runs pipelines, performs liftover, uses R/Python/Bash for analysis, or needs to document their analysis chain for reproducibility and publication. Also use when the user says "write me methods" to auto-generate methods sections from the provenance log. This skill implements comprehensive provenance documentation: every tool, every version, every reference file, every parameter, every accession — no shortcuts. Use this skill for ANY processing step, ANY file transformation, ANY analysis operation on ENCODE data.
日本語の概要は準備中です。原文の説明を表示しています。
Use ENCODE functional genomics data for disease mechanism research. Use when the user wants to connect GWAS variants to regulatory elements, annotate disease-associated loci with functional data, identify therapeutic targets from epigenomic data, build disease regulatory models, cross-reference with clinical trials and drug databases, or conduct any disease-focused, pathology-driven, or clinical variant interpretation workflow. Covers the full pipeline from disease-tissue mapping through GWAS variant annotation, heritability enrichment, cancer epigenomics, drug target identification, and clinical trial cross-referencing. Integrates ENCODE with Open Targets, PubMed, ClinicalTrials.gov, and bioRxiv.
日本語の概要は準備中です。原文の説明を表示しています。
Master defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts with POSIX compliance, modern Bash 5.x features, and comprehensive error handling. Use when writing shell scripts, bash automation, CI/CD scripts, system utilities, or mentions "bash", "shell script", "automation", "defensive programming", or needs production-grade shell code.
日本語の概要は準備中です。原文の説明を表示しています。
Automate semantic versioning releases with CHANGELOG validation, comparison link management, GitHub Actions workflow triggering, and monitoring. Scaffold release infrastructure for new projects. Use when user runs /release command, mentions "release version", "cut a release", "create release", "publish release", "tag release", "release setup", or "scaffold release pipeline".
日本語の概要は準備中です。原文の説明を表示しています。
Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality stack", "what tools am I missing", "setup eslint", "setup detekt", "add coverage", "add ruff", "configure CI quality pipeline", "scan project tools", "tooling audit", "android tooling", "android quality", "compose testing", "kmp testing", or "screenshot testing".
日本語の概要は準備中です。原文の説明を表示しています。
Use this when the user wants to generate, normalize, verify, deduplicate, or export training datasets for Codex, Antigravity, or Claude Code from topics, URLs, reference material, web research, or existing JSONL/CSV files. Supports SFT and DPO workflows, custom export schemas, and deterministic local pipeline scripts.
日本語の概要は準備中です。原文の説明を表示しています。