'ropa' 검색 결과

Refresh the Key Metrics table in a thesis with current data from Financial Modeling Prep, with a Quartr standardized-statement tie-break for Revenue Growth / Gross Margin gaps (Step 4b-Q) and a scoped web-search fallback (Step 4b) when FMP has no data or resolved the wrong company. Use when user says "numbers", "refresh metrics", "update key metrics", or "refresh [TICKER]" with no other action implied. Surgical edit only — does NOT create research notes or propagate via /sync. Also flags (never auto-edits) stale price/valuation framing in the thesis Summary — see Step 10b.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Propagate a hypothetical macro scenario through the entire portfolio. Use when user says "what if", "scenario", "what happens to my portfolio if", or describes a macro event to model.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Refresh the Key Metrics table in a thesis with current data from Financial Modeling Prep, with a scoped web-search fallback (Step 4b) when FMP has no data or resolved the wrong company. Use when user says "numbers", "refresh metrics", "update key metrics", or "refresh [TICKER]" with no other action implied. Surgical edit only — does NOT create research notes or propagate via $sync. Also flags (never auto-edits) stale price/valuation framing in the thesis Summary — see Step 10b.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cross-company language sweep via Quartr full-text search — date the adoption curve of a term/phrase across the global transcript+filing corpus, identify which companies (and which speaker roles) use it and when they started, and cross-reference against vault theses and graph adjacency to flag terms propagating through supply chains the book owns. Use when user says "sweep", "who is talking about X", "language scan", "adoption curve for X", or "is X inflecting".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides Rust error handling strategy. Use when choosing between Result/Option/panic, using anyhow vs thiserror, propagating errors with ?, or designing custom error types.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation) plus Cobra/Viper conventions where applicable. Use when a user has a Go spec to review, asks "is this spec ready?", or is about to implement from a written design. Distilled from spf13/go-skills and adapted to this repo's conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Quality control for pooled CRISPR screens covering library representation, Gini index, log-skew, replicate Pearson and Spearman concordance, essentialome precision-recall AUC against CEGv2 (Hart 2017), Cas9 cut-toxicity diagnostics, copy-number amplicon detection (Aguirre 2016 / Munoz 2016), bottleneck propagation through plasmid pool, infection, selection, and endpoint stages, MOI verification, and DepMap-style screen-quality scoring. Use when assessing screen quality before hit calling, deciding whether to repeat or rescue a screen, diagnosing low-confidence hits, choosing between MAGeCK / BAGEL2 / Chronos based on quality grade, picking a normalization strategy from QC signatures, or evaluating whether an in-vivo screen retained adequate library complexity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Infer orthologous genes and gene families across species using OrthoFinder3 (HOG-based phylogenetic orthology), SonicParanoid2, Broccoli, ProteinOrtho, OMA / FastOMA hierarchical orthologous groups, eggNOG-mapper, JustOrthologs, and TOGA whole-genome-alignment orthology. Use when building single-copy ortholog sets for phylogenomics, classifying co-orthologs and in/out-paralogs after gene duplication, propagating functional annotation via orthology with awareness of the ortholog conjecture, distinguishing speciation from duplication via gene-tree species-tree reconciliation, computing Quest-for-Orthologs benchmark performance, or running synteny-aware ortholog detection in WGD-affected lineages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Investigates DAG incidents with a precise top event, timeline, competing hypotheses, barriers, propagation, and bounded recovery. NOT for automated root-cause classification, trace collection, or performance profiling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book. NOT for server-side rate limiting, bulkhead isolation, backpressure protocols, or database-specific retry.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Track the full Toulmin epistemic ancestry of every claim produced by a multi-agent swarm. Each agent output is tagged with an argument chain (claim / data / warrant / relationship) derived from SwarmTracer spans and LineageEdge records, so operators can zoom into any sub-claim and see precisely which agents asserted it, what triggered each assertion, and how contradictions propagated or were synthesised away. The SwarmTracer pattern — wrapping the SwarmAgentExecutor to capture spans, record messages, and build a lineage graph — is the concrete runtime substrate. Argumentative lineage lifts that graph into the Toulmin vocabulary so reasoning provenance is both machine-queryable and human-interpretable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates PSR-14 Event Dispatcher implementation for PHP 8.5. Creates EventDispatcherInterface, ListenerProviderInterface, and StoppableEventInterface with event propagation. Includes unit tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate UK/EU GDPR compliance documents — privacy policies, cookie policies, DPIAs, ROPA, DSAR responses, data breach notifications, and consent forms. Use when a business needs GDPR documentation, data protection policies, or privacy compliance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a Go design spec before implementation begins - dispatch a subagent that checks a design doc for completeness, consistency, and idiomatic Go (simplicity, small consumer-defined interfaces, explicit wrapped errors, context propagation) plus Cobra/Viper conventions where applicable. Use when a user has a Go spec to review, asks "is this spec ready?", or is about to implement from a written design. Distilled from spf13/go-skills and adapted to this repo's conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.