2,013 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Define database models with clear naming, appropriate data types, constraints, relationships, and validation at multiple layers. Use this skill when creating or modifying database model files, ORM classes, schema definitions, or data model relationships. Apply when working with model files (e.g., models.py, models/, ActiveRecord classes, Prisma schema, Sequelize models), defining table structures, setting up foreign keys and relationships, configuring cascade behaviors, implementing model validations, adding timestamps, or working with database constraints (NOT NULL, UNIQUE, foreign keys). Use for any task involving data integrity enforcement, relationship definitions, or model-level data validation.
日本語の概要は準備中です。原文の説明を表示しています。
This skill applies consistent corporate branding and styling to all generated documents including colors, fonts, layouts, and messaging
日本語の概要は準備中です。原文の説明を表示しています。
Apply the four published expert-consensus clinical scenarios to manage GI adverse events in complex GLP-1 receptor agonist patients — persistent nausea mid-titration, GERD/heartburn after up-titration, elderly with sarcopenia risk, and insulin-treated elderly with CKD plus diarrhoea. Use when a clinician describes a patient resembling one of these archetypes, or asks "how to manage GLP-1 in an elderly patient with CKD", "patient on liraglutide developed reflux", "sarcopenia worry on semaglutide in 80-year-old", or "persistent nausea on semaglutide despite escalation". Grounded in Gorgojo-Martínez 2023 Table 4.
日本語の概要は準備中です。原文の説明を表示しています。
This skill recommends that all patients with Cushing’s syndrome receive monitoring and adjunctive treatment for cortisol-dependent comorbidities including psychiatric disorders, diabetes, hypertension, hypokalemia, infections, dyslipidemia, osteoporosis, and poor physical fitness. Apply when managing any CS patient to address associated health issues; triggers include confirmed or suspected hypercortisolism, preoperative evaluation, postoperative follow‑up, or persistent hypercortisolism despite treatment.
日本語の概要は準備中です。原文の説明を表示しています。
Determines successful catheterization in adrenal venous sampling by applying selectivity index cut‑offs with and without ACTH stimulation. Triggered during AVS when measuring cortisol levels and asking “Is the catheter properly positioned?” or when reviewing results for technical adequacy.
日本語の概要は準備中です。原文の説明を表示しています。
Order and interpret lipoprotein(a) [Lp(a)] measurement at least once in a lifetime, apply the risk-enhancer threshold (≥125 nmol/L or ≥50 mg/dL), and run cascade screening of first-degree relatives for premature ASCVD, familial hypercholesterolaemia, or elevated Lp(a) per the 2026 ACC/AHA multisociety dyslipidaemia guideline. Covers the Class 1 lifetime measurement, how elevated Lp(a) affects LLT initiation and intensification, the cascade screening indications, the interaction of Lp(a) with ASCVD risk estimation, and current therapeutic limitations. Use when a clinician asks when to check Lp(a), how often to repeat Lp(a), elevated Lp(a) what next, treatment for high Lp(a), should I screen my patient's family, Lp(a) and statins, cascade screening indications. Grounded in the 2026 ACC/AHA multisociety dyslipidaemia guideline.
日本語の概要は準備中です。原文の説明を表示しています。
MANDATORY skill for ALL code generation. Enforces top-down composition, consistent abstraction layers, and proper module hierarchy. Apply every time you write or modify code — in any language — no exceptions.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.
日本語の概要は準備中です。原文の説明を表示しています。
Core skill activation protocol - establishes mandatory workflows for finding and applying skills before any task
日本語の概要は準備中です。原文の説明を表示しています。
Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.
日本語の概要は準備中です。原文の説明を表示しています。
Apply code formatting rules after file edits in the source directory. Use when asked to format code or after making changes to source files.
日本語の概要は準備中です。原文の説明を表示しています。
Apply frontend code quality rules for React and TypeScript components. Auto-activates when editing component files.
日本語の概要は準備中です。原文の説明を表示しています。
Review-fix pipeline for Codex. Equivalent to the repository's Claude skill: collect review feedback, apply fixes through the existing review workflow, and prepare replies. Usage: /review [<issue#>|<PR#>]
日本語の概要は準備中です。原文の説明を表示しています。
Decompose systems into microservices and apply canonical distributed-systems patterns. Use this skill whenever the user wants to split a monolith into services, design service boundaries, choose between microservices and a modular monolith, implement sagas or the outbox pattern, set up CQRS or event sourcing, configure an API gateway or BFF, add resilience (circuit breakers, retries, timeouts), or implement distributed tracing with OpenTelemetry. Also trigger for distributed transactions, service discovery, event-driven architecture, contract testing with Pact, canary releases, and idempotent consumers.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, write, and maintain automated tests in any language, with worked examples in Python and JavaScript/TypeScript. Use this skill whenever the user wants to write or plan tests, apply TDD (red-green-refactor), structure unit tests with arrange-act-assert and given-when-then naming, choose between fakes, stubs, and mocks, set up dependency injection for testability, build integration tests with testcontainers, database seeding, or transaction rollback, write Playwright or Cypress end-to-end tests, use property-based testing with Hypothesis or fast-check, create pytest fixtures or factory_boy factories, review coverage or mutation testing, or triage flaky tests in CI. Also trigger for "test pyramid", "test trophy", "test isolation", "mocking", "snapshot tests", "golden files", "parametrized tests", "make the tests pass".
日本語の概要は準備中です。原文の説明を表示しています。
Decompose an epic into atomic parallelizable tasks, route each to the right skill, and keep the four delivery records straight — issues, STATUS, ROADMAP, CHANGELOG. Use as a meta-router when several skills could apply, and as the baseline for how delivery state is recorded. Trigger at the start of any multi-track epic, when the skill count exceeds ~12, or when the records have drifted from reality.
日本語の概要は準備中です。原文の説明を表示しています。
Run the skill-improvement pipeline after a learning was detected — capture, classify, create, validate, apply; explicit request only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when applying security best practices — authentication, authorization, CSRF protection, input sanitization, rate limiting, or secure coding — stack-agnostic.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing a UI brief on a stack with no framework executor — Svelte, Astro, Angular, plain HTML. Stack-independent sibling of react-shadcn-ui; idiom from the stack corpus.
日本語の概要は準備中です。原文の説明を表示しています。
Building React UI on shadcn/ui primitives + Tailwind — the apply/review/polish skill dispatched by `directives/ui/*` for the `react-shadcn` stack; idiom from tailwind-engineer.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the project's frontend stack is Livewire — dispatched by `directives/ui/{apply,review,polish}.ts`. Covers reactive state, events, lifecycle hooks, and component/view separation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the project uses `livewire/flux` — dispatched by `directives/ui/{apply,review,polish}.ts`. Covers Flux components, slots, variants, and form primitives.
日本語の概要は準備中です。原文の説明を表示しています。
Frontend design heuristics and the loop applying them: existing-ui-audit, brief, inventory, build, review. Use when building or changing any UI, not only when planning one.
日本語の概要は準備中です。原文の説明を表示しています。