'library' 검색 결과

Review licenses in dependency lists, individual libraries, or code planned for public release. Get a memo covering obligations for the deployment model, license conflicts, unresolved questions, and recommended actions for legal review before shipping.

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

• Review dependency licenses before shipping
• Assess a library before adding it
• Check license compatibility before releasing code

Continue library-dependent Python tasks when sandbox execution fails by switching to a shell script. Covers recognizing import errors, preserving script text, checking execution output, and troubleshooting package availability for tasks such as PDF generation or visualization.

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

• Retrying Python code after missing-library errors
• Continuing PDF generation through shell execution
• Running visualization code with installed packages

Build charts and interactive diagrams in TypeScript with explicit data types and clear component boundaries. Guides library selection, data validation, interaction design, and shareable view settings to support maintainable visualization code.

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

• Choose a visualization library for a TypeScript app
• Refactor a D3 prototype into maintainable TypeScript
• Define data types for selections and tooltips

Screen an existing compound library against a protein target with Boltz. Rank candidates by binding confidence or lead optimization score, download predicted structures, and review solubility, permeability, and lipophilicity results alongside the ranked hits.

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

• Screening an existing compound library against a protein
• Finding candidates with high binding confidence
• Comparing candidates for lead optimization

Find the right official documentation before answering technical questions. It identifies the library and version, retrieves focused references and examples, and explains relevant APIs while separating documented behavior from inference.

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

• Checking API usage for an installed library version
• Finding official guidance before upgrading
• Separating documented behavior from assumptions

Manage a shared skill library for Claude Code, Codex, Cursor, and other agents. Search, install, update, and deploy skills to selected agents, organize reusable groups and tags, and check where each skill is available.

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

• Deploy shared skills to Claude Code and Codex
• Check and update installed skills
• Organize skills with tags and reusable groups

Create new Feishu cloud documents from Markdown, a text format for structured content. Choose a folder or knowledge library location, and include tables, images, and diagrams in meeting notes or project plans.

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

• Create meeting notes in a specified folder
• Write project plans with tables and diagrams
• Add technical documents under a knowledge library page

Search saved Zotero papers by keywords or meaning, read selected PDF pages, and organize references. Use shell commands to update bibliographic details, tags, notes, and annotations, add items by identifier, and export bibliographies.

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

• Find saved papers about a research topic
• Read specific PDF sections and add annotations
• Organize reference details, tags, and reading notes

Turn successful posts or text into reusable templates with fields for changing details. Save, categorize, preview, edit, and apply your own content structures to new topics, while tracking how often each template is used.

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

• Saving a successful post as a template
• Reusing a familiar structure for a new topic
• Browsing templates by platform or usage count

Researches library documentation, implementation practices, and specific web pages using Nia, Perplexity, and Firecrawl through MCP tools. Produces a handoff document with findings, available code examples, recommendations, pitfalls, and source links for another agent.

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

• Research library APIs before planning a feature
• Compare recommended implementation practices
• Collect content from a specific documentation page

Check installed DOCA versions across package metadata, application files, runtime tools, and BlueField system information. Use the results to investigate build and runtime mismatches, check feature availability, and understand NGC container version tags.

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

• Check whether installed DOCA versions agree
• Investigate build and runtime version mismatches
• Check feature support for a specific release

Check DOCA installation health, prepare build and runtime requirements, and investigate environment failures such as missing libraries or memory settings. Helps choose container learning or hardware deployment paths based on the available system.

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

• Check whether a DOCA installation is healthy
• Investigate library detection and runtime environment failures
• Start learning through an NGC DOCA container without hardware

Build and troubleshoot custom plug-ins for workloads that doca-bench cannot measure with its built-in modes. Use the shipped CUDA example to guide shared-library construction, check loading and version compatibility, and verify a small test before larger runs.

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

• Checking whether a workload needs a custom extension
• Building a GPU benchmark plug-in from the shipped example
• Diagnosing a custom shared library that will not load

Build a first DOCA application by adapting an installed sample. Get guidance on build configuration, object setup and shutdown order, and common errors, plus how other languages access DOCA through its public C interface.

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

• Adapting an installed sample into a first DOCA application
• Configuring a build with pkg-config and meson
• Checking object lifecycle order and common errors

Build custom emulated PCIe devices that a host recognizes as peripherals while BlueField DPU code handles their operation. Get guidance on DOCA sub-library selection, capability checks, setup within an installed environment, and debugging device visibility or driver binding.

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

• Expose a custom PCIe device to a host
• Choose PCI Generic, virtio-net, or virtio-fs
• Investigate missing devices or driver binding failures

CRISPR library design for genetic screens. Covers sgRNA selection, library composition, control design, and oligo ordering. Use when designing custom sgRNA libraries for knockout, activation, or interference screens.

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

Write tests using React Native Testing Library (RNTL) v13 and v14 (`@testing-library/react-native`). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React 18, sync render) and v14 (React 19+, async render). Triggers on: test files for React Native components, RNTL imports, mentions of "testing library", "write tests", "component tests", or "RNTL".

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

Compatibility entry point for React-library work in Octane; routes existing-binding maintenance to update-bindings and actual React implementation ports to octane-react-library-port.

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

Turns Hi-C/Micro-C FASTQ into a deduplicated, filtered .pairs file with pairtools and decides whether the library worked. Covers the bwa mem -SP5M / bwa-mem2 / chromap --preset hic alignment idiom (mates mapped as independent single-end reads), pairtools parse vs parse2 and the walks-policy choice (5unique pairwise vs all for Pore-C/Micro-C concatemers), pair-type classification (keep UU and rescued UC), dedup (PCR vs optical/by-tile), select by pair_type/MAPQ/distance, restriction-fragment handling (restrict, Arima dual-enzyme, Micro-C/DNase fragment-free), and allele-specific phasing (pairtools phase to two coolers). The library-QC decision uses % long-range cis as the one-number quality metric, trans as the noise floor, orientation balance as fragment-map-free dangling-end/self-circle QC, and % duplicates as a complexity proxy. Use when processing Hi-C/Micro-C/Omni-C reads into pairs, judging library quality, handling multi-enzyme or restriction-agnostic protocols, or generating allele-specific contacts.

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

Comprehensive quality control for CLIP-seq libraries (eCLIP, iCLIP, iCLIP2, PAR-CLIP) covering library complexity (preseq), FRiP, IDR replicate reproducibility, read-distribution metagene, SMInput vs IgG control rationale, rRNA / snoRNA contamination, fragment-length distribution, and ENCODE-compliance thresholds. Use when assessing whether a CLIP library passed, deciding lenient vs stringent peak thresholds, comparing replicates with IDR rescue and self-consistency ratios, or distinguishing failed IP from over-amplified library.

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

ATAC-seq library quality control -- TSS enrichment, FRiP, fragment-size periodicity, library complexity (NRF/PBC1/PBC2), mitochondrial fraction, and ENCODE 4 thresholds. Use when assessing whether an ATAC-seq library passes ENCODE acceptance criteria, diagnosing transposition artefacts, comparing Omni-ATAC vs standard prep quality, or selecting which replicates to drop before peak calling.

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

Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.

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

Query a user's TrailSnap photo library through scoped MCP tools to find photos, reconstruct memories, build person timelines, create evidence-backed narratives, or propose an album plan for explicit in-app approval. Use for the user's own TrailSnap library; never claim a proposal was executed or changed the library.

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

Searches current documentation, release notes, API references and public repository issues for libraries, frameworks, SDKs, APIs and CLI tools with `firecrawl developer`. Use before answering when the user names a version, is upgrading, pastes an error from a library or tool, or asks how to use, configure or migrate a specific library or API. Model knowledge stops at a training cutoff and misses new releases, renamed APIs, changed defaults and recent fixes, so when a version, option, error or API is unfamiliar or may have changed, look it up instead of guessing. Also checks whether a bug was fixed and in which release. Not for general programming concepts, code that uses no specific library, or refactoring code the user supplied.

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