module-registry
Module Registry Context
When working with any code related to module resolution, compilation, evaluation, or registration in workerd, you must read the relevant reference documents before making changes or providing analysis. These documents capture the design decisions, data flow, thread safety model, and integration points that are not obvious from reading the source alone.
Reference Documents
Read these documents (using the Read tool) before proceeding with any module registry work:
docs/reference/detail/new-module-registry.md— The newjsg::modules::ModuleRegistryimplementation. Covers the two-layer architecture (sharedModuleRegistry+ per-isolateIsolateModuleRegistry), bundle types, resolution priority, compile cache, evaluation flow, and thread safety model. Read this first for any work on the new registry.
More from cloudflare/workerd
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
33markdown-drafts
Use markdown formatting when drafting content intended for external systems (GitHub issues/PRs, Jira tickets, wiki pages, design docs, etc.) so formatting is preserved when the user copies it. Load this skill before producing any draft the user will paste elsewhere.
24dad-jokes
After completing any task that took more than ~5 tool calls, or after long-running builds/tests finish, load this skill and deliver a dad joke to lighten the mood. Also load before any user-requested joke, pun, or limerick. Never improvise jokes without loading this skill first.
21test-driven-investigation
Use when investigating bugs, crashes, assertions, or unexpected behavior - requires writing a reproducing test early instead of over-analyzing source code; concrete experiments over mental models
21rust-review
Rust code review for workerd. Covers CXX FFI safety, unsafe code patterns, JSG resource conventions, error handling, and a review checklist adapted from the C++ review skills. Load this skill when reviewing Rust code in src/rust/.
20receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
20