1.1万 件 ・ 関連度順
概要と使いどころ
Use when a task needs the judgment of a Computer Systems Analyst — running requirements elicitation and gap analysis against a target system, writing a feasibility study for a build-vs-buy-vs-customize decision, designing a system integration approach (point-to-point vs middleware vs API-led), scoping data-migration risk before a cutover, or choosing between phased and big-bang implementation strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Computer Hardware Engineer — designing a power delivery network and selecting decoupling capacitors for a digital IC's core rail, budgeting a high-speed signal's rise time against trace impedance and via stub length, closing static timing on a board-level DDR or SerDes interface, sizing thermal resistance for a package's TDP, or reviewing a PCB layout for signal- or power-integrity risk before fab release.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Community Health Worker — screening a client for social-determinants-of-health barriers, triaging a referral to housing/food/transportation resources, translating a clinical instruction into a teach-back-verified action plan, or deciding whether a no-show pattern signals disengagement or an unaddressed barrier.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Compliance Manager — sizing and defending a compliance program's headcount/budget, deciding build-vs-buy on monitoring or case-management technology, choosing a centralized-vs-embedded staffing model, translating a new regulatory obligation into a costed resourcing ask, or reporting program coverage to executives/the board.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Chemical Equipment Operator/Tender — deciding whether to continue or stop a reagent addition when reactor temperature exceeds its expected range, evaluating a batch record deviation's actual chemical consequence before release, following lockout/tagout before servicing equipment that processed a hazardous chemical, or verifying secondary containment readiness.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Childcare Worker — checking ratio/headcount compliance across mixed-age groups, deciding whether a fall or minor incident needs a written report versus a verbal mention at pickup, redirecting a behavior problem in an unstructured (non-curriculum) setting, or triaging which of several simultaneous demands (a crying toddler, a fight over a toy, a diaper) gets attention first.
日本語の概要は準備中です。原文の説明を表示しています。
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 the judgment of a book publisher — sizing an advance against a P&L model before an acquisition auction, setting a print run from comp-title sales data, deciding whether to keep bidding or walk in a multi-house auction, valuing subsidiary rights as part of a deal, or diagnosing why a title's early sell-through is diverging from its launch plan.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs. civil penalty vs. certificate action), auditing a Safety Management System for a functioning safety-assurance loop rather than paperwork completeness, scoping a records-sampling strategy across a fleet under surveillance, or deciding whether to ground an aircraft pending an AD compliance finding.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Auto Damage Insurance Appraiser — writing a repair estimate from photos or an in-person inspection, deciding repair vs. total loss against a state total-loss formula, evaluating a body shop's supplement request for hidden damage, determining actual cash value (ACV) for a totaled vehicle, or reconciling an OEM-vs-aftermarket-parts dispute.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a certified athletic trainer — triaging an on-field or on-court injury, deciding same-day return-to-play vs. refer-out, running a concussion sideline assessment and graduated return-to-sport progression, recognizing exertional heat stroke or another sudden-death emergency, or writing the objective findings that justify a clearance decision.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Administrative Law Judge, Adjudicator, or Hearing Officer — applying a mandatory sequential/structured evaluation framework in required order, weighing conflicting medical or vocational opinion evidence using specific regulatory factors, writing findings that explicitly address significant contrary evidence in the record, drafting a credibility/consistency finding tied to specific record citations, or checking whether a draft decision would survive substantial-evidence review.
日本語の概要は準備中です。原文の説明を表示しています。
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 Adult ESL/Basic Education Instructor — placing a new adult learner using standardized assessment scores, designing life-context-relevant lesson content for working adults, tracking NRS-reportable level gains, addressing attendance/retention barriers, or preparing a learner for GED/HSE or workplace English benchmarks.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-agent review resolution with trust-but-verify methodology. Accepts a PR number/URL or a local code-review report file. Extracts review comments, verifies each with parallel agents using confidence scoring (0-100), filters false positives, presents a triage report for approval, then applies fixes and replies. Use when user runs /resolve-review, mentions "resolve PR comments", "address review feedback", "fix PR suggestions", "handle review comments", or "resolve review findings".
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold, validate, and maintain Johnny.Decimal documentation structure for software projects. Use when user mentions "Johnny Decimal", "J.D docs", "docs structure", "organize docs", "documentation layout", "scaffold docs", "docs migration", "generate index", "docs index", "add area", "classify docs", "move doc", editing files in numbered directories (00-*, 10-*, 20-*), or discussing documentation organization.
日本語の概要は準備中です。原文の説明を表示しています。
Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile setup", "setup task runner", "audit taskfile", "scaffold taskfile", "add taskfile", "taskfile.yml", or "developer tasks".
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive guide for building, configuring, customizing, and deploying Docsify documentation sites. Use when the user wants to (1) initialize a new Docsify site, (2) add or organize Markdown pages, sidebars, navbars, or cover pages, (3) configure `window.$docsify` options, (4) customize themes / CSS variables / fonts, (5) install built-in or third-party Docsify plugins (search, GA, emoji, zoom, copy-code, comments, pagination, tabs, etc.), (6) write a custom Docsify plugin using lifecycle hooks, (7) use Docsify Markdown helpers (callouts, link attributes, image attributes, heading IDs, task lists, embed files with `:include`), (8) deploy to GitHub Pages, GitLab Pages, Netlify, Vercel, Firebase, Docker, Nginx, etc., (9) enable PWA / offline mode, virtual routes, or Vue compatibility, or (10) upgrade a Docsify site from v4 to v5. Triggers on mentions of "docsify", "_sidebar.md", "_navbar.md", "_coverpage.md", "$docsify", or `docsify-cli`.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Create, run, and maintain API test collections using Bruno (OpenCollection YAML format and legacy Bru format). Use when the user wants to: (1) create a Bruno API test collection from scratch or from OpenAPI/Swagger specs, (2) write API request files with tests and assertions, (3) run API tests using bru CLI, (4) generate test reports (HTML, JUnit, JSON), (5) set up CI/CD pipelines (GitHub Actions) for automated API testing, (6) debug or fix failing Bruno API tests, (7) add environment configurations for API testing, (8) chain API requests with data extraction, or (9) work with any .yml/.bru Bruno collection files. Triggers on mentions of 'Bruno', 'bru CLI', 'API testing collection', 'OpenCollection', or requests to automate API testing with file-based collections.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
日本語の概要は準備中です。原文の説明を表示しています。
Create a new Azure DevOps wiki page. Use when the user wants to add a new wiki page, write project documentation in Azure DevOps wiki format, or update wiki page structure with mermaid diagrams in Traditional Chinese.
日本語の概要は準備中です。原文の説明を表示しています。
Write, review, and optionally test Bash and Zsh shell scripts following project coding standards. Use for ANY shell scripting task: (1) creating a new Bash or Zsh script, (2) editing, fixing, or reviewing an existing .sh, .bash, or .zsh file, (3) adding error handling, dependency checks, or cleanup traps to shell scripts, (4) implementing API integration or file processing in shell, (5) writing or fixing ShellSpec tests (spec/*_spec.sh), or (6) deciding whether a script should be written in Bash or Zsh. Defaults to Bash; Zsh-specific guidance lives in a reference file that is loaded only when writing Zsh.
日本語の概要は準備中です。原文の説明を表示しています。