1,580 件 ・ 関連度順
概要と使いどころ
Expert Bash help for writing, debugging, and optimizing safe, portable shell one-liners and scripts on macOS/Linux. Use when users ask for Bash or POSIX sh commands, script reviews, ShellCheck fixes, quoting/pipeline issues, process/file automation, or converting requirements into shell scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Hard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for consistency, traceability, and unresolved ambiguity. Returns PASS or FAIL with specific findings. Load when the spec-driven-development orchestrator routes /analyze, when the user asks to cross-check spec vs plan, audit traceability, verify spec readiness, gate-check before implementation, or says "is this spec implementation-ready", "trace requirements to tasks", "/analyze", "spec sanity check", "spec readiness gate", "spec consistency check". Output: docs/reviews/YYYY-MM-DD-<slug>-spec-crosscheck.md.
日本語の概要は準備中です。原文の説明を表示しています。
Measure, profile, and fix performance bottlenecks — Core Web Vitals, backend latency, bundle size, and database queries. Load when performance requirements exist, users report slowness, profiling reveals bottlenecks, or the user asks to optimize load time, LCP, INP, CLS, or response time. Not for premature optimization without evidence. Pairs with browser-testing-with-devtools and ci-cd-and-automation for regression guards.
日本語の概要は準備中です。原文の説明を表示しています。
Decompose an unknown quantity into 3-5 estimable factors and produce a defensible order-of-magnitude answer without needing precise data. Load when the user needs to size something without data — market size, resource requirements, effort estimates, user numbers, costs — or when a decision is blocked by "we don't know the numbers". Also triggers on "ballpark this", "rough estimate", "how big is this market", "how long would this take", "how many users", or when deep-thinking diagnoses a sizing/estimation frame. The goal is not precision — it is a defensible answer that enables a decision to be made. Based on Enrico Fermi's estimation method.
日本語の概要は準備中です。原文の説明を表示しています。
Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes for correctness, completeness, bugs, edge cases, and quality. Load when the user explicitly asks to review code, check a PR, review a diff, audit recent changes, or verify an implementation matches requirements. Also triggers on "review this code", "check this PR", "review my changes", "code review", "did this implement correctly", "audit this diff", or any explicit request for a formal code review. Do NOT load for "review changes for context" or "review what happened" — those are requests to read code, not to perform a formal review.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a rough idea into a fully approved design before any code is written. Load when the user wants to brainstorm, explore ideas, design a feature, think through approaches, plan a new capability, or figure out what to build. Also triggers on "let's think through", "help me design", "explore options", "what's the best approach for", "I have an idea for", "before we build", or any request to design something before implementation. Enforces a hard gate: no code, no implementation until user approves a design. For executable feature specs (FRs, NFRs, ACs as Given/When/Then), route to `feature-spec` instead — brainstorming owns approach and architecture, not machine-readable requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This skill operates in two phases — (1) generating a structured analysis framework with chapter skeleton, data query requirements, and analysis logic, and (2) after data collection by other skills, producing the final consulting-grade report with structured narratives, embedded charts, and strategic insights.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.
日本語の概要は準備中です。原文の説明を表示しています。
A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify requirements before implementing. Use when serious doubts arise.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data. Handles SEACR vs MACS2 peak calling (with the btaf375 2025 benchmark guidance), pA-MNase vs pA-Tn5 vs pAG-Tn5 chimera differences, E. coli spike-in carryover normalization, IgG-only control logic (no input), characteristic fragment-size signatures (25-75 bp for CUT&Tag), and lower depth requirements (5M reads typical vs 25M for ChIP). Use when calling peaks from CUT&RUN/CUT&Tag, scaling by E. coli spike-in carryover, choosing SEACR norm mode, or comparing CUT&RUN/Tag results to traditional ChIP.
日本語の概要は準備中です。原文の説明を表示しています。
Detects differential alternative splicing between conditions using rMATS-turbo (binomial LRT on junction counts), leafcutter (Dirichlet-multinomial GLM on intron clusters), MAJIQ V3 deltapsi/HET (Bayesian posterior on LSVs), SUPPA2 (empirical-null on TPM-derived PSI), or Shiba (junction-imbalance-corrected, 2025 SOTA at low coverage). Reports FDR-corrected significance and delta PSI effect sizes. Tools differ in statistical model, annotation dependence, calibration regime, and replicate-count requirements. Use when comparing splicing patterns between treatment groups, tissues, or disease states.
日本語の概要は準備中です。原文の説明を表示しています。
Audit required bioinformatics command-line tools against Lmod or Environment Modules on Linux HPC clusters, resolve executable and version requirements, and reproducibly deploy missing software through a site-approved EasyBuild, Spack, Bioconda/micromamba, Apptainer, binary, or source-build workflow. Use when Codex must inspect module availability, diagnose a missing or wrong-version bioinformatics tool, install scientific software on Slurm/PBS clusters, publish or validate modulefiles, or produce an auditable and rollback-ready cluster software deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about the financial differences between being an owner-operator vs company driver — gross pay, expenses, net pay, capital requirements, risk tolerance, lifestyle, and how to evaluate the path. Reference industry pay surveys.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to design an annual driver refresher training program. Covers what to cover, frequency, documentation, and ROI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier or driver asks about winter trucking, snow chain requirements, hot-weather precautions, summer tire failures, fuel additive use (anti-gel), idle management in extreme temperatures, weight restrictions in spring thaw, or how seasonal demand patterns affect freight rates and capacity.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about oversize / overweight load permits — state-by-state permitting process, escort vehicle (pilot car) requirements, route surveys, federal axle weight limits (Federal Bridge Formula), holiday restrictions, multi-state permits, and how to determine if a load needs a permit. Reference state DOT permitting offices.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about CMV maintenance program requirements under 49 CFR 396.3 — what records must be kept, retention periods (12-18 months on vehicle file + 1 year after disposal), what counts as systematic inspection/repair/maintenance, preventive maintenance scheduling, brake adjustment records, and what auditors look for in vehicle files. Cite 49 CFR 396.3 + 396.21.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about passenger-carrying CMVs — buses, motorcoaches, charter operations, school buses, limousines, shuttle services. Covers different HOS rules (10-hour driving / 15-hour on-duty / no 34-restart), Class C CDL with P endorsement, S endorsement for school bus, FMCSA Hours-of-Service for passenger vehicles, $5M insurance minimum, BMC-32 filing, accessibility requirements, and how passenger ops differ from property. Cite 49 CFR 395.5 + 387.33.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to understand when electronic records are acceptable to FMCSA inspectors. Covers PDF, original-format, and search-ability requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to understand record retention requirements for currently-employed drivers. Covers DQF, HOS, vehicle records, and D&A specific periods.
日本語の概要は準備中です。原文の説明を表示しています。