4,564 件 ・ 関連度順
概要と使いどころ
Infer cis-regulatory connections (peak-to-peak co-accessibility) from scATAC-seq using Cicero, ArchR getCoAccessibility, or SCENIC+. Use when linking enhancer accessibility to promoter accessibility, identifying enhancer-gene pairs from chromatin alone (without paired RNA), running gene-regulatory inference combining ATAC + RNA, or comparing predicted regulatory contacts against Hi-C/Micro-C ground truth.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier asks whether to buy or lease their next tractor (or trailer), comparing full-service lease (Ryder, Penske, NationaLease), capital lease, finance lease, walk-away open-end lease, or cash purchase. Covers tax treatment, residual risk, maintenance bundling, balance-sheet impact, and cash-flow modeling.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about cybersecurity for a trucking carrier — protecting ELD data, customer information, financial systems, EDI integrations, fleet telematics, ransomware risk, vendor / shipper data sharing, incident response, and FMCSA cyber-recommendations. Reference NIST + CISA cybersecurity frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing Coval evaluation setup for coverage, misleading scores, missing evidence, judge validation and execution risk. Read-only; use when inheriting an eval or deciding whether its results support a release decision.
日本語の概要は準備中です。原文の説明を表示しています。
Decision-ready scouting record for a user-connected provider access campaign. Use when an assigned Provider Access Launch task needs its easiest official route, minimum scopes, cost, account needs, approval path, implementation consumer, and easy-execute verdict established before submission. NOT for client Local Listings distribution.
日本語の概要は準備中です。原文の説明を表示しています。
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Use when the user explicitly asks to threat model a codebase or path, enumerate abuse paths, or perform AppSec threat modeling.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
日本語の概要は準備中です。原文の説明を表示しています。
Claude Codeセッション中に行われたアーキテクチャ上の意思決定を構造化されたADRとして記録する。意思決定の瞬間を自動検出し、コンテキスト、検討された代替案、根拠を記録する。将来の開発者がコードベースの形状の理由を理解できるようADRログを維持する。
Analyze an idea, proposal, change, claim, or decision from facts through problem, value, mechanism, consequences, evidence, alternatives, and action. Use when the user asks what something is for, why it matters, whether it is worth doing, what impact it has, or how to decide. Do not use for simple factual lookup or straightforward execution.
日本語の概要は準備中です。原文の説明を表示しています。
Combine React's official "You Might Not Need an Effect" guidance with this project's stricter no direct useEffect stance. Use when writing, reviewing, or refactoring React components that might reach for useEffect, derived state, event relays, reset logic, subscriptions, or client fetching.
日本語の概要は準備中です。原文の説明を表示しています。
GRASP principles knowledge base for PHP 8.5 projects. Provides quick reference for 9 responsibility assignment patterns (Information Expert, Creator, Controller, Low Coupling, High Cohesion, Polymorphism, Pure Fabrication, Indirection, Protected Variations). Use for architecture audits and design decisions.
日本語の概要は準備中です。原文の説明を表示しています。
PHP Standards Recommendations (PSR) overview knowledge base. Provides comprehensive reference for all accepted PSRs including PSR-1,3,4,6,7,11,12,13,14,15,16,17,18,20. Use for PSR selection decisions and compliance audits.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze context and decide on continuation via Stop hook. Use when determining if work should continue, analyzing completion status, making continuation decisions, or implementing the Two-Claude pattern.
日本語の概要は準備中です。原文の説明を表示しています。
[31] ANALYZE. Universal deep thinking methodology for any situation requiring quality reasoning. Use when solving problems, debugging, making decisions, analyzing code, planning, reviewing, or anytime you need thorough thinking instead of surface-level responses. Triggers on "think deeply", "analyze thoroughly", "reason carefully", "deep thinking", "understand completely", or any task requiring careful thought.
日本語の概要は準備中です。原文の説明を表示しています。
Apply timeless programming wisdom from "97 Things Every Programmer Should Know" when writing, reviewing, or refactoring code. Use for design decisions, code quality checks, professional development guidance, testing strategies, and workflow optimization.
日本語の概要は準備中です。原文の説明を表示しています。
[51] EXECUTE. Commitment to maximum quality work with 150% coverage. Use when you need the highest quality output for critical tasks, complex problems, important decisions, or when standard work isn't enough. Triggers on "maximum quality", "150% mode", "full quality", "critical task", or when you explicitly want AI to work at its best.
日本語の概要は準備中です。原文の説明を表示しています。
[32] ANALYZE. Ensure every critical claim has verifiable evidence with confidence levels. Each fact must have source + confidence percentage. If confidence <85%, enter Loop150 to find more sources. Use for critical decisions, factual claims, legal/compliance work, or any situation where unverified claims are dangerous.
日本語の概要は準備中です。原文の説明を表示しています。
Apply 37signals/DHH Rails conventions when writing Ruby on Rails code. Use when building Rails applications, reviewing Rails code, or making architectural decisions. Covers various aspects of Rails application architecture, design and dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
Use when GitHub may have shipped a GraphQL schema update affecting timeline event unions (PullRequestTimelineItems / IssueTimelineItems), when the gh-timeline dispatcher fallback is hitting more than expected, before a gh-timeline release, or when the user requests phrases like "verify timeline coverage", "audit gh-timeline schema", "check for new timeline events", "GitHub schema changed". Walks through schema diff → patch → test update → live verification → optional fixture refresh, marking each spot where a human decision is required.
日本語の概要は準備中です。原文の説明を表示しています。
実装要求に、要求が答えていない設計判断が残るとき、または誤りが後段で黙って通る変更を扱うときに使う。具体的には、API・設定の与え方・データモデル・新しい型や概念・責務や層境界を決める必要がある、複数の実現方法から選ぶ設計判断がある、変更範囲を事前に局所化できない、認可・公開範囲・データ消失・外部送信のように誤りをテストや型検査で検出しにくい、のどれかに当たるタスクで発火する。原因と修正箇所が特定済みで期待結果と検証方法が明確な修正、既存パターンの適用、機械的な rename、CI/CD・ドキュメント・設定値・依存バージョンだけの変更では使わない。要求を出典付きの決定と質問に分解する解釈ゲート、判断の重さに応じた階層(直接実装 / 軽量 / 標準)の判定、subagent への分担、実物差分での検収、独立レビューをフェーズ順に管理するスキル。
Decision framework for choosing between regex and LLM when parsing structured text — start with regex, add LLM only for low-confidence edge cases.
日本語の概要は準備中です。原文の説明を表示しています。
Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.
日本語の概要は準備中です。原文の説明を表示しています。
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
日本語の概要は準備中です。原文の説明を表示しています。