9,862 件 ・ 関連度順
概要と使いどころ
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 6 platform targeting and build guide. Use when building for specific platforms, configuring build profiles, using platform scripting defines (#if UNITY_IOS, #if UNITY_ANDROID), optimizing for mobile, WebGL, or consoles, working with Addressables/asset bundles, or choosing between IL2CPP and Mono. Based on Unity 6.3 LTS documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, configuring, reviewing, or debugging Vite-based frontend projects, vite.config.ts, env variables, dev server proxy, HMR, plugin ordering, library mode, dependency pre-bundling, bundle splitting, or Vite build performance. Use framework-specific skills for React/Vue component architecture; Chinese triggers include Vite configuration, vite.config, Vite build, Vite performance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating editable technical diagrams with draw.io / diagrams.net sources, including architecture diagrams, ERD, UML, sequence diagrams, flowcharts, ML model diagrams, official shape lookup, brand symbols, Graphviz auto-layout, codebase structure maps, .drawio validation, or draw.io CLI export fallback. Do not use for ordinary raster image generation, freehand sketches, interactive canvas/Three.js scenes, or decorative SVG animation. Chinese triggers include draw.io, diagrams.net, editable architecture diagrams, .drawio, ER diagrams, UML, sequence diagrams, auto layout, shape retrieval, code structure diagrams.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up or reviewing Storybook component documentation, design-system presentation, isolated component state previews, stories, addons, decorators, MDX docs, component-state interaction checks, visual baselines, or Chromatic. For real-browser cross-page journeys or broader coverage planning, choose the matching testing workflow first; Chinese triggers include Storybook, component documentation, Design System, visual regression.
日本語の概要は準備中です。原文の説明を表示しています。
Use when frontend work needs to communicate data, action, state, permission, validation, or business-rule needs to backend teams without dictating endpoint design, field names, database shape, or implementation details; Chinese triggers include front-end and back-end requirements handover, back-end requirements, API requirements clarification, data requirements description.
日本語の概要は準備中です。原文の説明を表示しています。
Nuxt module for Better Auth integration with NuxtHub, route protection, session management, and role-based access
日本語の概要は準備中です。原文の説明を表示しています。
Generate a fully customized Amazon Connect AI agent PoC bundle (Lambda handlers, OpenAPI spec, AI agent prompt, Contact Flows, CloudFormation/CDK infrastructure, FAQ knowledge base) from a ~15-minute structured interview — or from a requirements doc, a flow sketch, or an existing flow/prompt you want to improve. Triggers on "amazon connect", "aicc", "contact center AI", "connect ai agent", "connect ai agents domain", "agentic cx designer", "acxd", "connect customer", "agentic cx block", "requirements document", "improve my contact flow", "flow sketch", "\uc544\ub9c8\uc874 \ucee4\ub125\ud2b8", "\ucee8\ud0dd\uc13c\ud130 AI \uc0c1\ub2f4\uc6d0".
日本語の概要は準備中です。原文の説明を表示しています。
Generate a fully customized Amazon Connect AI agent PoC bundle (Lambda handlers, OpenAPI spec, AI agent prompt, Contact Flows, CloudFormation/CDK infrastructure, FAQ knowledge base) from a ~15-minute structured interview — or from a requirements doc, a flow sketch, or an existing flow/prompt you want to improve. Use when the user wants to build, scaffold, prototype, or refine an Amazon Connect contact center, an AI voice/chat agent on Amazon Connect, or any contact-center use case that mentions Connect, Lex, Wisdom, Q in Connect, "AI agent domain", or Agentic CX Designer (ACXD, Connect Customer, the Agentic CX block — the ACXD runtime target). Also triggers on "I have a requirements document", "turn this flow sketch into a Contact Flow", or "improve my existing Contact Flow / AI prompt". Produces 6 asset packages on local disk.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a computer programmer implementing to a given specification — translating a design/pseudocode/systems-analyst spec into working code in a specified language, flagging spec ambiguity before writing code, maintaining or modernizing an existing codebase against its original contract, or writing unit tests that prove the implementation matches the spec (not designing the system the spec describes).
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an audiovisual equipment installer/repairer — diagnosing an EDID or HDCP handshake failure between a source and a display, sizing a display's screen size and brightness for a room's viewing distance and ambient light, specifying an HDMI/HDBaseT/AVoIP signal run against its rated distance ceiling, designing conference-room speaker placement and acoustics, or drawing the install-vs-programming boundary with a control-system (Crestron/Extron/AMX) integrator.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Biofuels Processing Technician — adjusting catalyst dosing for transesterification based on actual measured feedstock free fatty acid content rather than a standard fixed dose, verifying conversion completeness via actual glyceride content testing rather than visual inspection, actively monitoring fermentation temperature and pH throughout the process rather than checking only at the end, and managing byproduct quality as a distinct economic consideration alongside primary fuel yield.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a licensed acupuncturist — building a TCM pattern-differentiation-based treatment plan, choosing point combinations and needling technique for a presenting complaint, triaging a safety red flag (fainting, suspected pneumothorax, herb-drug interaction), or writing a SOAP note that justifies medical necessity for insurance. US scope-of-practice default (NCCAOM/state licensure). A reasoning aid, not medical advice.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct rigorous cross-study meta-analysis of scRNA-seq data from ENCODE, integrating multiple single-cell transcriptomic datasets for a tissue/cell type. Use when the user wants to answer "what cell types exist in my tissue and what genes define them?" by combining scRNA-seq data across donors, labs, and platforms. Follows the Mawla et al. 2019 framework for assessing cross-study reproducibility, TIN-based quality filtering, and detection-limit-aware interpretation. Handles batch correction (Harmony/Seurat), dropout awareness, cross-contamination artifacts, and platform-specific biases. Use this skill for ANY scRNA-seq integration task, cross-dataset comparison, cell atlas construction, or reproducibility assessment involving ENCODE single-cell data.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for using JASPAR transcription factor binding profiles with ENCODE ChIP-seq data. Use when users need to find TF binding motifs in ENCODE peaks, validate ChIP-seq targets with known motifs, or scan regulatory regions for TF binding potential. Trigger on: JASPAR, motif database, binding profile, PWM, position weight matrix, TF motif, motif enrichment, motif scanning, binding site prediction.
日本語の概要は準備中です。原文の説明を表示しています。
Query the Ensembl REST API for regulatory feature annotations, variant effect prediction (VEP), coordinate liftover, gene lookups, and cross-references. Use when the user needs to annotate variants with VEP (consequence, CADD, REVEL, SpliceAI), check Ensembl Regulatory Build overlap for ENCODE regions, convert coordinates between GRCh37 and GRCh38, resolve gene IDs (Ensembl ↔ symbol ↔ RefSeq), look up gene phenotype associations, or cross-reference ENCODE targets with Ensembl annotations. Also use when the user mentions Ensembl, VEP, variant effect predictor, liftover, assembly conversion, regulatory build, gene lookup, or cross-references between databases.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Query gnomAD (Genome Aggregation Database) for population allele frequencies, gene constraint scores, and variant annotations to interpret ENCODE regulatory variants. Use when the user needs allele frequencies for variants in ENCODE regulatory elements, wants to assess gene constraint (pLI, LOEUF) for ENCODE target genes, needs population-specific frequencies for GWAS variants overlapping cCREs, wants to filter variants by rarity before functional annotation, or is interpreting ENCODE CRISPR/MPRA results in the context of population genetics. Also use when the user mentions gnomAD, allele frequency, pLI, LOEUF, constraint, rare variants, population frequency, ExAC, or variant filtering.
日本語の概要は準備中です。原文の説明を表示しています。
Detect drift in .arkhe/roadmap/ context files and regenerate them from the current codebase state. Scaffolds context directory if missing. Use when user runs /roadmap:refresh, mentions "refresh context", "update context", "init roadmap", "stale context", or "scaffold roadmap".
日本語の概要は準備中です。原文の説明を表示しています。
Verify code-review or security-review findings for false positives using deep codebase tracing, framework-aware analysis, and web research. Produces a .verified.md report alongside the original. Use when a review report has been generated and needs independent verification, or when user runs /verify-findings, mentions "verify review", "check false positives", or "validate findings".
日本語の概要は準備中です。原文の説明を表示しています。
Synthesize project documentation and codebase into comprehensive roadmap status, gaps analysis, and blockers. Use when assessing project health, identifying blockers, tracking progress, comparing plan vs reality, documenting risks, or planning next milestones. Triggers: "roadmap", "project status", "blockers", "risks", "progress", "next milestone", "gaps", "what's done".
日本語の概要は準備中です。原文の説明を表示しています。
Spring Modulith 2.0 implementation for bounded contexts in Spring Boot 4. Use when structuring application modules, implementing @ApplicationModuleListener for event-driven communication, testing with Scenario API, enforcing module boundaries, externalizing events to Kafka/AMQP, building a modular monolith, defining module dependencies, managing inter-module events, or organizing DDD modules as packages. Covers package-based module boundaries, named interfaces, event publication, and Scenario API testing. For architecture decisions, see domain-driven-design skill.
日本語の概要は準備中です。原文の説明を表示しています。
Install Tilt and scaffold or audit Tiltfile + tilt/ configurations with ecosystem-aware templates. Auto-detects Java/Gradle (Spring Boot), Next.js, Python/uv, and external infrastructure; recommends single-file or modular tilt/*.star + service-config.yaml + environments.yaml patterns based on project complexity. Bakes in production-context safety guards, PVC persistence toggles, JDWP debug ports, and optional Prometheus/Grafana/Traefik scaffolds. Use when user runs /devtools:tilt-setup, mentions "tilt setup", "setup tilt", "scaffold tiltfile", "audit tiltfile", "tilt configure", "tilt project setup", "Tiltfile", "local kubernetes dev", or "kubernetes development environment".
日本語の概要は準備中です。原文の説明を表示しています。