메뉴
Guides wasm, webR, and duckdb-wasm debugging for DuckHTS, including artifact verification, symbol/export checks, browser-runtime constraints, and package-vs-runtime distinctions. Use when debugging DuckHTS in webR, browser wasm, or duckdb-wasm environments.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Guides machine-readable function catalogs for DuckDB extensions, including a `functions.yaml` source-of-truth pattern that can drive docs, wrappers, aliases, examples, and consistency checks. Use when an extension exposes many SQL functions or multiple wrapper surfaces.
Guides development in the DuckHTS repo, including DuckDB extension work, Rduckhts package integration, vendored htslib workflows, SQL and tinytest coverage, wasm/webR constraints, and exact-compatible rewrites of upstream genomics tools. Use when working in github.com/RGenomicsETL/duckhts.
Guides creation, maintenance, checking, testing, documenting, and releasing R packages using project-native workflows such as Makefiles, tinytest, roxygen2, base R, and optional tools like usethis, pkgdown, air, or jarl. Use when working on any R package or CRAN-style package workflow.
Guides cache, index, and annotation-store design for bioinformatics rewrites, including when to use mainstream interoperable formats versus specialized high-performance encodings. Use when startup cost, repeated lookup performance, interval access, or annotation storage strategy are central design concerns.
Guides library-first bioinformatics rewrites that expose mature native code through bindings, extensions, FFI, or embedded runtimes across R, Python, SQL, and wasm. Use when building reusable interfaces around existing C/C++ libraries instead of standalone-only rewrites.
Guides responsible AI-assisted rewriting and porting of bioinformatics tools, combining rewrites.bio principles with practical validation, attribution, compatibility, and maintenance discipline. Use when planning or implementing a rewrite, reimplementation, or high-performance port of an existing bioinformatics tool.
| name | duckhts-wasm-debugging |
| description | Guides wasm, webR, and duckdb-wasm debugging for DuckHTS, including artifact verification, symbol/export checks, browser-runtime constraints, and package-vs-runtime distinctions. Use when debugging DuckHTS in webR, browser wasm, or duckdb-wasm environments. |
Use this skill when debugging DuckHTS in:
This is a specialized skill because DuckHTS wasm behavior is intentionally different from native Linux/macOS builds.
AGENTS.mdr/Rduckhts/configuresrc/wasm_http_hfile.csrc/include/wasm_socket_compat.hAlways distinguish between:
Do not assume results from one runtime apply to another.
inst/duckhts_extension/build/ in the repo is a real wasm payloadRduckhts_<Version>.tgzWhen a wasm extension fails to load:
strings or symbol-table presence aloneA symbol may exist in the module but still not be exported for the loader.
For init-symbol failures, confirm that the required DuckDB init symbol is actually exported.
DuckHTS repo guidance currently treats wasm networking carefully:
pkg-config curl assumptions for wasmwasm_http_hfile.c strategy unless runtime assumptions have changedWhen debugging a load/runtime problem:
Repo guidance notes that some browser-side warnings can be noisy but non-fatal. Do not confuse unrelated browser console noise with the root cause if the extension loads and HTS smoke tests pass.