1,121 件 ・ 関連度順
概要と使いどころ
Infrastructure-as-code specialist for multi-cloud provisioning using Terraform across any provider (AWS, GCP, Azure, Oracle Cloud). Use for terraform plan/apply, state management, compute, databases, storage, networking, IAM, OIDC, cost optimization, policy-as-code, ISO/IEC 42001 AI controls, ISO 22301 continuity, and ISO/IEC/IEEE 42010 architecture documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.
日本語の概要は準備中です。原文の説明を表示しています。
Backend and infra for a project via Cohesivity (cohesivity.ai). Provisions Postgres, hosting and deploys, auth and social login, realtime websockets, an agent-native email inbox, object and vector storage, Redis, cron, and AI model APIs (OpenAI, Anthropic, Deepgram, Exa) through one HTTP API. Use when a valid `.cohesivity` file exists, a Cohesivity MCP is available, the user names Cohesivity, or the project needs a backend or any of these services and no competing provider was chosen.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing the response to an American Educational Research Journal (AERJ) revise-and-resubmit. AERJ R&Rs come back through the handling editor and multiple masked reviewers, so the response must convert each reviewer while keeping the editor confident the revision is convergent. Structures the response letter; it does not fabricate new results.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting the response letter and revision plan after an American Economic Journal: Microeconomics (AEJ: Micro) R&R. Structures the reply to theory referees (correctness, generality, exposition) and editor; it does not re-derive the result (see aejmic-theory-model).
日本語の概要は準備中です。原文の説明を表示しています。
Use when responding to an American Economic Review: Insights (AER: Insights) conditional-accept decision — addressing the editor's letter within the short window, usually without a second referee round. Drafts a concise, decisive response and revision plan; it does not redo the analysis (see aeri-robustness / aeri-identification).
日本語の概要は準備中です。原文の説明を表示しています。
Use when an American Economic Journal: Applied Economics (AEJ: Applied) decision letter arrives (R&R or conditional accept) and a response-to-referees letter plus a revision plan must be drafted. Plans and structures the response; it does not run the new analysis (aeja-identification / aeja-robustness) or the submission preflight.
日本語の概要は準備中です。原文の説明を表示しています。
Use when anticipating the objections referees and coeditors will raise on an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript, and calibrating desk-reject and revision odds, before submission. Pre-empts pushback and plans the review; it does not draft the post-decision response letter (use aejmac-rebuttal).
日本語の概要は準備中です。原文の説明を表示しています。
Use when an AEJ: Economic Policy decision letter (R&R or reject-and-resubmit) has arrived and a response-letter strategy and revision plan are needed. Structures the response to referees and editor with policy-relevance front and center; it does not run new estimation or redesign identification from scratch.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding which advmat-* sub-skill to invoke next, or when sequencing manuscript work from scope-fit through revision for an Advanced Materials (Adv. Mater.) manuscript. Routes — does not replace — the specialized skills.
日本語の概要は準備中です。原文の説明を表示しています。
Use when anticipating the objections a sophisticated American Economic Journal: Applied Economics (AEJ: Applied) referee will raise, so a manuscript pre-empts them before submission or addresses them in revision. Plans the defense; it does not draft the response letter (aeja-rebuttal) or run the submission preflight (aeja-submission).
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification, revision, artifact evaluation, ACM camera-ready, and in-person presentation, with backward-planning offsets and the security big-four deadline-hopping calendar.
日本語の概要は準備中です。原文の説明を表示しています。
Use when explaining or planning around ACM CCS peer review, the two-cycle HotCRP workflow, decision categories including minor revision, the rebuttal window, the adversarial reviewer pool, ethics and disclosure scrutiny, meta-review dynamics, and ACM proceedings outcomes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting the response to an Administrative Science Quarterly (ASQ) R&R after the manuscript has been revised — structuring the response letter and handling reviewer/editor comments. Drafts the response; it does not perform the underlying revisions (do those first).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building or auditing the related-work section of an ACM MM (ACM Multimedia) paper — covering the multimedia literature spread across vision, audio/speech, language, HCI/QoE, and systems, handling arXiv-speed concurrency, keeping citations double-blind, and verifying that cited "ACM MM papers" are ACM MM and not ICMR, MMSys, CVPR, or TOMM.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to understand how Accounting, Organizations and Society (AOS) evaluates a manuscript — triage by the joint Editors-in-Chief, double-anonymized review by interdisciplinary referees, the meaning of each decision type, and how to read the editor's letter. Explains the process; it does not draft the revision response (aos-rebuttal).
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding which amr-* sub-skill to invoke next, or when sequencing a theory-building manuscript from theoretical-puzzle framing through developmental-review revision for an Academy of Management Review (AMR) submission. Routes — does not replace — the specialized skills.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an Accounting, Organizations and Society (AOS) revise-and-resubmit arrives — planning revisions that may include recoding field data, new experimental conditions, or deepened theorizing, and drafting the point-by-point response to an interdisciplinary reviewer panel. Drafts the response; it does not run new analysis (aos-data-analysis) or the final preflight (aos-submission).
日本語の概要は準備中です。原文の説明を表示しています。
Use when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge placement from artifact evaluation, incorporation of shepherd and minor-revision requirements, disclosure-timing coordination, registration, and in-person presentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when responding to 《会计研究》 (Accounting Research) reviewer reports / an R&R — drafting a point-by-point response letter and 修改说明 that addresses accounting-measure construction, institutional/standard accuracy, identification, and information-mechanism concerns, while keeping the revision anonymous. Use only after the manuscript itself has been revised.
日本語の概要は準備中です。原文の説明を表示しています。
Use when deciding which amann-* sub-skill to invoke next, or when sequencing a comprehensive review article from topic selection through revision for an Academy of Management Annals (Annals) submission. Routes — it does not replace — the specialized skills.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to run Design Error Detection (quick defect scan), find design errors in a Simulink model, perform root cause analysis on DED findings, fix division-by-zero, overflow, dead logic or out-of-bounds defects detected by SLDV, or diagnose why missing coverage cannot be achieved (dead logic blocking coverage objectives). Do NOT use for requirement verification, test generation, Inf/NaN detection, active logic analysis, or coverage measurement.
日本語の概要は準備中です。原文の説明を表示しています。
Critical Akka.NET best practices including EventStream vs DistributedPubSub, supervision strategies, error handling, Props vs DependencyResolver, work distribution patterns, and cluster/local mode abstractions for testability.
日本語の概要は準備中です。原文の説明を表示しています。
Unsupervised clustering and cell-type identification for high-dimensional flow, spectral, and mass cytometry - FlowSOM, PhenoGraph, FlowSOM-via-CATALYST, with UMAP/tSNE for visualization. Covers the type-vs-state marker distinction (cluster on lineage, test state within clusters), over-provision-then-metacluster, the Weber-Robinson benchmark, seed dependence and metacluster stability, why embeddings are for looking not measuring, and median-heatmap annotation/merging. Use when discovering populations without predefined gates, choosing a clustering algorithm, selecting the number of metaclusters, or annotating clusters into cell types.
日本語の概要は準備中です。原文の説明を表示しています。