3,708 件 ・ 関連度順
概要と使いどころ
Call accessible chromatin regions from ATAC-seq BAM files using MACS3, MACS2, Genrich, or HMMRATAC. Use when identifying open chromatin from aligned ATAC-seq, choosing between point-source vs HMM peak callers, applying ENCODE-style pseudoreplicate IDR, removing blacklist regions, or fixing 501bp consensus peaks for downstream differential analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a single FASTA file (nucleotide or protein), compute sequence-level metrics (GC, ORFs, MW, pI, GRAVY, secondary-structure fractions) with Biopython, and write a Markdown report plus structured JSON for downstream chaining.
日本語の概要は準備中です。原文の説明を表示しています。
If CGM is not available, continue monitoring blood glucose with point-of-care testing as an alternative option. Trigger phrases include: "CGM is not available, what should we use for glucose monitoring?
日本語の概要は準備中です。原文の説明を表示しています。
Suggests initiating inpatient continuous glucose monitoring (CGM) for select hospitalized patients at high risk for hypoglycemia, combined with periodic point-of-care glucose checks for accuracy. Triggers include planning glucose monitoring for inpatients with prior severe hypoglycemia, renal or hepatic dysfunction, or age 65 years or older.
日本語の概要は準備中です。原文の説明を表示しています。
Screen a hypercalcemic patient for medication- and supplement-induced causes — thiazides, lithium, vitamin D, vitamin A/retinoids, antiestrogens, theophylline, milk-alkali, SGLT2 inhibitors, immune checkpoint inhibitors, denosumab rebound, teriparatide/abaloparatide, foscarnet, ketogenic diet, aluminium. Trigger when a clinician asks "is this hypercalcemia drug-induced", "thiazide hypercalcemia", "lithium hypercalcemia", "denosumab rebound hypercalcemia", "vitamin D toxicity", "milk-alkali syndrome", "SGLT2 hypercalcemia", or any new hypercalcemia where medication review is needed.
日本語の概要は準備中です。原文の説明を表示しています。
Oracle-bound spec-review check that every structured Rollout prerequisite binds to an enforcement-type acceptance criterion. A prerequisite whose `enforced-by` is missing, dangling, or points at a non-enforcement AC is a BLOCKER (hard-blocks implementation entry via the checker fan-out verdict); a prerequisite left in free prose is ADVISORY. Read-only. Runs in the spec-review fan-out before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
The primary tool for code-navigation questions in ANY language (frontend or backend) — walk the structural graph from an entry point (page, route, handler, command, `main`) down through imports to the IO boundary (network call, query, file read). Use this skill, in preference to the Explore agent or global grep, whenever the user asks "where does X come from?", "what API/data populates Y?", "what renders or wraps the Z panel?", "which file for feature F?", "how is this wired up?", or any code-navigation question mapping a UI element, route, or feature concept to source files. Also reverse queries ("what uses /api/foo?", "who consumes this service?"). Keyword search routinely picks up unrelated flows sharing a domain word and produces wrong answers; the walk follows the actual graph. The JS/TS `walk.mjs`/`discover.mjs` are an optional accelerator, not required — the walk is language-agnostic.
日本語の概要は準備中です。原文の説明を表示しています。
Use RoutIR — call a running endpoint with the client, stand up a local server that mixes locally-hosted services with services proxied from a remote master server, and extend RoutIR with new bi-encoders, rerankers, and document collections by writing a small config (and optionally one Python file referenced via `file_imports`). No checkout of the routir source is required.
日本語の概要は準備中です。原文の説明を表示しています。
Use for systems thinking, or when a change may ripple beyond its target: "what are the side effects?", "why does this keep coming back?", "how do these teams or services affect each other?". Maps loops, delays and leverage points. Skip for single-step fixes.
日本語の概要は準備中です。原文の説明を表示しています。
SAM: zero-shot image segmentation via points, boxes, masks.
日本語の概要は準備中です。原文の説明を表示しています。
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a written implementation plan to execute in a separate session with review checkpoints
日本語の概要は準備中です。原文の説明を表示しています。
REST/GraphQL API testing with automated validation — test endpoints, validate responses, check status codes, and ensure API contracts
日本語の概要は準備中です。原文の説明を表示しています。
Create, read, edit .pptx decks, slides, notes, templates.
日本語の概要は準備中です。原文の説明を表示しています。
Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.
日本語の概要は準備中です。原文の説明を表示しています。
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
日本語の概要は準備中です。原文の説明を表示しています。
Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Event Hubs SDK for Python streaming. Use for high-throughput event ingestion, producers, consumers, and checkpointing.
日本語の概要は準備中です。原文の説明を表示しています。
Provide comprehensive techniques for penetration testing AWS cloud environments. Covers IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence techniques for red team operations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive REST API design review with automated linting, breaking-change detection, and design scorecards. Catches inconsistent conventions, missing versioning, and design smells before APIs ship. Use when reviewing a PR that adds or changes API endpoints, auditing an existing API for v2 migration, or establishing API standards for a team.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
日本語の概要は準備中です。原文の説明を表示しています。
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.
日本語の概要は準備中です。原文の説明を表示しています。
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
日本語の概要は準備中です。原文の説明を表示しています。