1.2万 件 ・ 関連度順
概要と使いどころ
METAINFORMANT rules for directory docs/metagenomics. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory docs/agents. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory config/phenotype. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory config/ncbi. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory config/multiomics. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory config/singlecell. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory config/longread. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory .agents/workflows. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory config/eqtl. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory docs/core. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
METAINFORMANT rules for directory config/config_base. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.
日本語の概要は準備中です。原文の説明を表示しています。
Create a free remote development host on Oracle Cloud (Always Free) end to end — install and authenticate the OCI CLI, provision VCN/subnet/NSG/instance with capacity retries, then apply a hardened Ubuntu 22.04 Ansible stack (Tailscale-only SSH, ufw, fail2ban, mosh, persistent tmux, Caddy tailnet web previews, on-host verification suite) and tear it down again. Use when the user says "free remote dev environment", "Oracle Cloud free tier dev box", "OCI Always Free VPS", "give me a cloud dev machine for free", "provision a dev host on Oracle", or asks to move a Tailscale-only dev host setup to Oracle Cloud. Covers OCI CLI bootstrap, the Tailscale cutover, verification, costs, and teardown.
日本語の概要は準備中です。原文の説明を表示しています。
Build or review an external integration QA lab with official surface snapshots, coverage matrices, fixtures, opt-in live lanes, and safe credential handling.
日本語の概要は準備中です。原文の説明を表示しています。
Load when authoring/reviewing commit messages or PR titles/descriptions, or replacing a materially diverged phase commit contract; not for ordinary implementation or executing an unchanged approved contract.
日本語の概要は準備中です。原文の説明を表示しています。
Load when asked to create, update, re-baseline, or continue a repository-grounded implementation/technical/refactor plan and its `dev/active/<task>` plan/context/tasks files; not for a product PRD, informal advice, or reviewing an already-written plan.
日本語の概要は準備中です。原文の説明を表示しています。
Load when executing or resuming an approved plan from `dev/active/<task>/` or `.worktrees/<task>`, including phase commits, verification, PR creation, and handoff; not for plan authorship or review.
日本語の概要は準備中です。原文の説明を表示しています。
Load when the user asks for CTO advice on feature strategy, architecture direction, build-vs-buy, infrastructure, market positioning, roadmap, self-hosting, cost, or organizational tradeoffs; not for reviewing an existing implementation-plan workstream.
日本語の概要は準備中です。原文の説明を表示しています。
Load when asked where code lives, how modules relate, what calls a symbol, what implements a feature, or for an architecture/codebase tour using the knowledge graph; not for bug diagnosis, diff review, or refactoring.
日本語の概要は準備中です。原文の説明を表示しています。
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
日本語の概要は準備中です。原文の説明を表示しています。
Audit code quality focusing on deep modules, naming, model hygiene, and architectural clarity. Use after a burst of development, when codebase structure needs assessment, or to make code more agent-navigable.
日本語の概要は準備中です。原文の説明を表示しています。
Crystallize shared understanding into a reviewable spec, or update an existing one. Use when the problem needs a written specification, when assumptions or decisions have changed, or when the user says 'write a spec'.
日本語の概要は準備中です。原文の説明を表示しています。
Deep expertise in cmux — the terminal multiplexer with native browser views. Use when managing panes, reading terminal output, sending keystrokes, opening browser views, or manually testing web UIs and TUIs inside cmux. Triggers on: cmux, open a browser pane, split terminal, read screen, send keys, test this UI in cmux, preview in cmux.
日本語の概要は準備中です。原文の説明を表示しています。
Search, summarize, and synthesize economics literature. find research gaps, position your contribution.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the DoD Systems Engineering Guidebook (OUSD R&E, February 2022). Use for the DoD SE process model — the 16 SE processes (8 technical management + 8 technical) mapped to ISO/IEC/IEEE 15288, the event-driven technical reviews and audits across the Major Capability Acquisition life cycle (ASR, SRR, SFR, PDR, CDR, SVR/FCA, PRR, PCA), the Systems Engineering Plan (SEP), risk/issue/opportunity management, TPMs and leading indicators, system-of-systems and digital engineering, and the 24 design considerations (RAM, system safety, HSI, system security engineering, MOSA, supportability, etc.). Acquisition-program oriented: thin on detailed cost estimating, contracting law, and non-DoD or commercial life cycles.
日本語の概要は準備中です。原文の説明を表示しています。