194 件 ・ 関連度順
概要と使いどころ
Populate databases with realistic, reproducible test data for development, testing, and staging environments. Use when the user requests database seeding or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Ichthyologist. Use when a task calls for Ichthyologist judgment. Reasons from meristic fin formulae, sagittal otolith annuli/daily increments, larval flexion staging, and ICZN type discipline through Eschmeyer's Catalog, FishBase/WoRMS, MiFish/12S eDNA with blank controls, FSA/TropFishR/SS3 stock assessment, and Darwin Core museum metadata while treating CPUE catchability, unvalidated otolith ages, larval pigmentation loss, and eDNA false positives as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Hepatologist. Use when a task calls for Hepatologist judgment. Reasons from hepatic injury pattern (R-value), synthetic function, and portal hypertension through Child-Pugh/MELD 3.0, FIB-4 and elastography, LI-RADS/BCLC staging, SAAG paracentesis, and Baveno VII criteria while treating DILI misattribution, elastography false positives in cholestasis, hypersplenic thrombocytopenia, and missed acute-on-chronic decompensation as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Dentist-Scientist. Use when a task calls for Dentist-Scientist judgment. Reasons from oral biofilm-host ecology, tissue healing capacity, and patient-level clinical endpoints (DMFS, PD/CAL, implant survival) through PICO/PROSPERO protocols, CAMBRA and 2017 AAP/EFP staging, ISO 4049/14801 bench tests with thermocycling, and GRADE-rated reviews while treating in-vitro-to-chairside leaps, plaque-index surrogates without caries reduction, and examiner calibration drift as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Developmental Biologist. Use when a task calls for Developmental Biologist judgment. Reasons from stage, positional information, gene regulatory networks, and tissue mechanics through morphology-based staging (Carnegie/HH/Theiler/NF/hpf), French-flag morphogen logic, light-sheet 4D imaging, lineage tracing, and ARRIVE/MDAR/REMBI reporting while treating developmental delay, CRISPR F0 mosaicism, morpholino p53 toxicity, and conflated fate-versus-lineage claims as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Astronautical Engineer. Use when a task calls for Astronautical Engineer judgment. Reasons from the rocket equation, staging, and mass–power–Δv budgets through NPR 7120.5/ECSS-E-ST-10 subsystem specs, CEA/CEARUN and Sutton propulsion, CLA/pogo and TVAC I&T, GMAT/STK/SPICE mission design, CCSDS TM/TC link margins, and ADCS FDIR while treating unit/frame ICD mismatches, combustion instability, and MCO-class V&V gaps as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working on Formax code changes and you need a disciplined dev loop: keep a single mainline task, avoid scope drift, run only targeted tests (no coverage), avoid partial staging (MM), run mandatory review before commit, include an incremental optimization check, and keep commits small and reviewable.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — for Boundless team members only. Audit native ETH, market deposit, prover collateral, and distributor ZKC reserve balances for every operator-managed address (provers, distributor, order generators, signal). Use when the user wants to know which addresses need topping up, asks about the balance of provers/OGs/distributor/signal signers, says something is "running low" or "out of gas", or wants a periodic operational health check on operator wallets. Defaults to prod env (mainnets + prod testnets) — pass `--all` to also include staging.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — for Boundless team members only. Deploy Boundless infrastructure to a new blockchain. Creates Pulumi stacks, config files, updates ChainId enum, and wires CI/CD pipelines for staging and prod environments. Use when adding a new chain, deploying to a new network, or setting up new chain infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — for Boundless team members only. Query AWS CloudWatch logs for Boundless services (provers, slasher, distributor, order stream, order generator, indexer, signal) on prod/staging environments. Use when the user asks to look at service logs, debug service behavior from log output, search logs for a request ID, or investigate errors using CloudWatch. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — for Boundless team members only. Query the Boundless Indexer REST API for on-chain market data, staking, PoVW rewards, delegations, and market efficiency on prod/staging environments. Use when the user asks about proof requests, provers, requestors, staking data, PoVW rewards, delegations, market aggregates, leaderboards, or wants to fetch data from the indexer API on live networks. Also use when the user mentions "indexer" and wants to look up addresses, requests, or market statistics on deployed environments. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — for Boundless team members only. Query Boundless broker telemetry tables on Redshift for prod/staging operational data. Use when the user asks about broker health, request evaluations, request completions, proving times, skip rates, telemetry data, or wants to run SQL against the telemetry database on live networks. Also covers historical telemetry through 2026-04-24 stored as Parquet archives in S3 (queried via DuckDB). Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.
日本語の概要は準備中です。原文の説明を表示しています。
Mine a per-kernel optimization trace — a git repository capturing successive versions of one kernel being optimized — into structured, gate-validated optimization-experience records for the GPU kernel wiki. Use when asked to distill an optimization run, a kernel_opt trace directory or a version ladder into wiki records; to report what such a run actually achieved; to build, extend, re-run or validate the staging store behind those records; or to explain how a trace-derived record's number, snippet or provenance was established.
日本語の概要は準備中です。原文の説明を表示しています。
Manage environment variables and secrets across development, staging, and production environments. Use when someone needs to audit env vars, sync secrets between environments, detect missing or mismatched variables, rotate credentials, or set up a new environment from an existing one. Trigger words: env vars, environment variables, secrets, .env file, dotenv, config management, secret rotation, missing variable, environment sync.
日本語の概要は準備中です。原文の説明を表示しています。
Mask, redact, and anonymize sensitive data (PII, PCI, PHI) in databases, logs, and APIs. Use when protecting PII in dev/staging environments, redacting sensitive data from logs, anonymizing data for analytics, or applying k-anonymity and differential privacy for GDPR-compliant data sharing.
日本語の概要は準備中です。原文の説明を表示しています。
Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback. Use before any deployment to staging, preview, or production.
日本語の概要は準備中です。原文の説明を表示しています。
影视编剧 (Scriptwriting / Screenwriting) — 为电影 / 电视 / 流媒体剧集写戏剧蓝本的从业者认知操作系统: 决定「讲什么故事、人物是谁为何转变、场景如何被戏剧化、主题为何重要」的学科 —— 区别于导演 (调度 / 视觉实现)、制片 (融资 / 排期)、小说 (无格式 / 场景 / 视觉动作约束)。覆盖 (a) 故事与结构理论 (亚里士多德《诗学》情节 / 人物 / 思想 + 突转 peripeteia / 发现 anagnorisis + 净化 catharsis; Syd Field 范式 / 三幕 / 情节点; Freytag 金字塔; Egri 前提; McKee《故事》掌控性理念 / 鸿沟 / 价值正负转变 / 激励事件 / 渐进式复杂化; Truby《故事剖析》22 步 + 道德论证; Vogler/Campbell 英雄之旅; Blake Snyder《救猫咪》15 拍节拍表; Dan Harmon 故事环; John Yorke 五幕《进入森林》; Frank Daniel 八序列法; 起承转合东亚戏剧结构), (b) 人物 (想要 vs 需要 / 外在目标 vs 内在缺失, 人物弧光 正 / 负 / 平, flaw-wound-ghost 创伤背景, 主动 vs 被动主角的能动性, Egri 三维人物 生理 / 社会 / 心理, 反派是主角的镜子, 群像与关系网, 人物在压力下的选择中显形), (c) 对白 (潜台词 subtext, 对白即动作与冲突而非信息, 避免太直白 on the nose, 人物独特声口, 信息植入 exposition, Mamet/Sorkin 意图-阻碍式对白, 展示而非告知, 中文剧台词工艺), (d) 场景与序列工艺 (场景是有目标 / 冲突 / 转折的微型故事, 场景价值充能与转折点, 晚进早出, 八序列法, set piece, 转场, 场景头 / 动作行 / 括号提示 格式工艺), (e) 主题与前提 (掌控性理念 / 前提, 主题是被戏剧化的论证而非说教, 道德论证 Truby, 主题统一性, 这到底在讲什么), (f) 类型 (类型惯例是对观众的承诺, Snyder 10 类故事, 颠覆 vs 尊重套路, 类型片 vs 文艺片, 中国类型 主旋律 / 古装 / 年代 / 悬疑 / 甜宠 / 都市 / 军旅 / 历史正剧), (g) 格式与工业流程 (好莱坞剧本格式与 Final Draft, logline 一句话故事, treatment 故事大纲, 节拍表, 分场 / 分集大纲, spec 原创剧本 vs 委托, pitch, coverage, 美剧编剧室与 showrunner 制; 中国 大纲→人物小传→分集大纲→剧本, 长剧集 40 集结构, 网络电影 / 网大, 分账剧, 平台定制剧, 微短剧竖屏短剧), (h) 改稿与开发 (写作就是改写, 改稿 / 润色 / 推倒重写, 处理意见 / 改稿意见, 片方与平台 notes, 杀死你的宝贝, 围读, 开发地狱), (i) 改编 (IP改编 小说 / 漫画 / 游戏改编, 忠于精神而非字句, 压缩, 中国网文 IP 热), (j) 中国影视编剧产业现实 (审查 / 广电总局约束, 备案 / 立项, 平台定制剧 爱优腾芒, 分账, 编剧维权 署名权 / 欠薪 / 枪手, 注水剧, 流量 + 大IP 资本逻辑 vs 原创工艺, 导演中心制 vs 编剧话语权), (k) 编剧职业与工艺生涯 (spec vs 委托, 编剧 vs 编审 / 策划, 单兵 vs 编剧室, 在开发链条中的位置, WGA 与署名仲裁规范, 入行, 中国编剧地位与权益)。跨 电影 / 美剧流媒体 / 中国电影与长剧集。不含 导演 / 摄影 / 制片 / 融资 / 表演 / 电影理论批评为终点 / 泛小说写作 / 纪录片 / 新闻 —— 本 skill 是「戏剧化编剧」工艺: 故事 / 人物 / 场景 / 对白 / 主题 / 结构 / 格式 与围绕它们的产业流程。 (Scriptwriting / Screenwriting for film & TV (影视编剧) — the cognitive operating system of practitioners who write the dramatic blueprint of films, television, and streaming series: the discipline of deciding WHAT story is told, WHO the characters are and why they change, HOW the scenes are dramatized, and WHY it matters thematically — distinct from directing (staging/visual realization), producing (financing/scheduling), and prose fiction (which has no format/scene/visual-action constraints). Covers (a) story & structure theory (Aristotle's Poetics — plot/character/thought + reversal peripeteia/recognition anagnorisis + catharsis; Syd Field's paradigm/three-act/plot points; Freytag's pyramid; Lajos Egri's premise; Robert McKee's Story — controlling idea/the gap/value charge/inciting incident/progressive complications; John Truby's 22 steps & moral argument; Christopher Vogler/Joseph Campbell hero's journey; Blake Snyder's Save the Cat 15-beat sheet; Dan Harmon's story circle; John Yorke's 5-act Into the Woods; Frank Daniel's 8-sequence method; 起承转合 East-Asian dramatic structure), (b) character (want vs need/external goal vs internal lack, character arc positive/negative/flat, 人物弧光, flaw-wound-ghost backstory, agency active vs passive protagonist, Egri's 3-dimensional character physiology/sociology/psychology, antagonist as the protagonist's mirror, ensemble & relationship webs, character revealed through choice under pressure), (c) dialogue (subtext 潜台词, dialogue as action & conflict not information, 'on the nose' avoidance, distinct character voice, exposition handling, Mamet/Sorkin intention-obstacle dialogue, show-don't-tell, 台词 craft in Chinese drama), (d) scene & sequence craft (scene as a mini-story with goal/conflict/turn, scene value charge & turning point, enter-late-leave-early, the 8-sequence method, set pieces, transitions, slug line/action line/parenthetical format craft), (e) theme & premise (controlling idea/premise/前提, theme as dramatized argument not message, moral argument Truby, thematic unity, 'what is this really about'), (f) genre (genre conventions as audience promise, Snyder's 10 story types, subverting vs honoring tropes, 类型片 vs 文艺片, Chinese genres 主旋律/古装/年代/悬疑/甜宠/都市/军旅/历史正剧), (g) format & industry process (Holly
日本語の概要は準備中です。原文の説明を表示しています。
Investigate unexpected behavior and mysterious bugs. Use when the cause of a problem is unknown and the user needs to understand WHY something is happening — symptoms like: sudden unexplained changes in metrics or behavior, works locally but not in staging/production, inconsistent or intermittent failures, correct code producing wrong results, operations succeeding but having no effect, environment-specific failures, duplicate executions, stale data, or any "why did this change?" or "why is this happening?" situation. Covers infrastructure anomalies (cache hit rates dropping, latency spikes, queue behavior shifts) as well as code bugs. The key signal is confusion about root cause, not a request to implement a known fix. Do NOT use for feature requests, known fixes, planning, or documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Servd (servd.host) — Craft-specialised managed hosting for Craft CMS. Covers git push-to-deploy with the optional servd.yaml build config, local → staging → production environments with uni-directional Project Config sync, the servd/craft-asset-storage plugin (S3-backed Flysystem volumes on the svdcdn.com CDN, off-server image transforms, Imager-X/ImageOptimize integrations), Servd's static caching (full vs tag-based purge, {% dynamicInclude %}, CSRF injection, cache-busting) and running Blitz alongside it in reverse-proxy mode, MariaDB/MySQL databases over an SSH tunnel, automatic + manual backups, the Dedicated Queue Runner, environment variables and secrets, the ephemeral load-balanced filesystem (Redis + remote volumes for runtime files), plugin/feature constraints, and Servd-vs-Craft-Cloud differences.
日本語の概要は準備中です。原文の説明を表示しています。
VNX feature-execution kickoff preflight. USE THIS when starting or resuming a feature or track from its plan: checking worktree/queue/staging health, finding the first promoteable dispatch, and handing off to @t0-orchestrator. Reads the feature's track + plan doc from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md/PR_QUEUE.md are generic examples, not the source.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any new project from scratch. Asks for project identity (name, GitHub org, Cloudflare account), detects project type, sets up design system, staging+production, i18n from day 1, SEO foundation, AGENTS.md manifest, test infrastructure, 8-gate deploy pipeline, and disciplined development workflows. Prevents wrong deploys, redundant repos, and technical debt from day 0.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap any new project: identity, design system, staging+production, i18n, SEO, test infrastructure, 8-gate deploy pipeline. Prevents tech debt from day 0.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and implement native RayTK (t3kt/raytk) raymarching/SDF toolkit integration into tdmcp — beyond the existing package-manager staging, into AI-driven RayTK operator (ROP) node graphs. Use whenever the user wants to build, plan, design, implement, continue, fix, QA, or ship RayTK support: create/wire RayTK ROPs, a RayTK operator knowledge catalog, a RayTK-native raymarch/SDF scene tool, RayTK recipes, or the RayTK setup/doctor flow — including follow-ups (re-run, continue, refresh after a new RayTK release, re-QA, docs). Also triggers on 'raytk', 'raymarching toolkit', 'SDF toolkit', 't3kt', 'montar um build para o raytk', 'integrar o raytk'. This owns RayTK integration specifically; use it before the generic tdmcp-pipeline for this feature. Simple questions about RayTK can be answered directly.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a link into a papercut reel script. Researches a sourced facts list, writes the 75-95 word script on the 10-beat spine, a banner fact track, a staging table with one set per banner, and the humour pass. Use for "write the script", "research this repo for a reel".
日本語の概要は準備中です。原文の説明を表示しています。