[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72VTEG9AB229C97SRKZ2FFG":3,"skill-same:01M72VTEG9AB229C97SRKZ2FFG":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M72VTEG9AB229C97SRKZ2FFG","meteor-typescript",null,"Use when setting up or repairing Meteor application declarations, TypeScript configuration, JavaScript IntelliSense, or local and CI type-checking. Triggers on meteor types, meteor\u002F* imports resolving to any, missing declarations, duplicate Meteor identifiers, zodern:types, @types\u002Fmeteor, .meteor\u002Ftypes, tsconfig.json, jsconfig.json, and tsc --noEmit in a Meteor app. Use this skill when choosing or migrating declaration providers without changing the app's runtime or bundler. For a Meteor 2-to-3 runtime migration use migrate-to-meteor-3 first; for SWC\u002FRspack compilation use meteor-modern-build-stack or migrate-to-rspack. General TypeScript language questions and Atmosphere declaration publishing are outside this app scope.","meteor\u002Fagent-skills","meteor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F789528?v=4","01M72VQVFCJ72XHP7ZKS3774NA","Meteor","01M72VQVG5VZ0X5VCQYM0MCK1Q",11,"MIT","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-typescript\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: meteor-typescript\ndescription: >\n  Use when setting up or repairing Meteor application declarations, TypeScript\n  configuration, JavaScript IntelliSense, or local and CI type-checking.\n  Triggers on meteor types, meteor\u002F* imports resolving to any, missing\n  declarations, duplicate Meteor identifiers, zodern:types, @types\u002Fmeteor,\n  .meteor\u002Ftypes, tsconfig.json, jsconfig.json, and tsc --noEmit in a Meteor app.\n  Use this skill when choosing or migrating declaration providers without\n  changing the app's runtime or bundler. For a Meteor 2-to-3 runtime migration\n  use migrate-to-meteor-3 first; for SWC\u002FRspack compilation use\n  meteor-modern-build-stack or migrate-to-rspack. General TypeScript language\n  questions and Atmosphere declaration publishing are outside this app scope.\nmetadata:\n  author: meteor\n  kind: knowledge\n  meteor: \">=3.0\"\n  area: build\n  tagline: \"Configure Meteor app declarations, TypeScript and JavaScript IntelliSense, and reliable local\u002FCI type-checking.\"\n  docs_synced_at: \"2026-10-07\"\nlicense: MIT\n---\n\n# TypeScript in Meteor applications\n\nMake the editor and checker resolve the intended Meteor declarations and\nactually inspect application source. Preserve working provider choices unless\nthe task includes changing them. A runtime or bundler upgrade does not imply\na declaration migration.\n\nFor a runtime migration or bundler configuration request, load the owning\nskill before proposing migration steps or build configuration. This skill's\ndeclaration guidance does not supply that procedure; do not substitute a\ngeneric TypeScript\u002FRspack recipe when the owning skill is unavailable.\n\n## Identify the layer\n\n| Layer | Evidence and action |\n|---|---|\n| Compilation | The Atmosphere `typescript` package or Rspack\u002FSWC strips types. Use the build owner for syntax transforms, loaders and bundling. |\n| Declaration provider | Inspect `.meteor\u002Fpackages`, `.meteor\u002Fversions`, npm\u002Fworkspace manifests and lockfile for direct `zodern:types`, `@types\u002Fmeteor` and native opt-in. |\n| Resolution | Inspect active `tsconfig.json`\u002F`jsconfig.json`, `extends`, `files`, `include`, `exclude`, `paths` and `types`. Check the editor uses the intended project\u002Fcompiler. |\n| Checking | Inspect the installed npm `typescript` and scripts; it is separate from the Atmosphere compiler. Preserve a configured checker such as `TsCheckerRspackPlugin`. |\n\nDo not infer that an app is checked because `meteor run` or `meteor build`\nsucceeded. Conversely, do not claim an explicitly configured checker never\nruns just because SWC itself only transpiles.\n\n## Choose the provider\n\nNative package declarations are available on Meteor 3.6+.\n\n| Target and intent | Decision |\n|---|---|\n| Meteor 3 before 3.6 | Native `meteor types` is unavailable. Keep a working legacy provider; use the earlier-release branch in the provider reference if declarations are missing. |\n| New Meteor 3.6 TypeScript, TypeScript + Tailwind, Svelte or Angular app | The scaffold selects native declarations and `meteor create` generates them. Keep that provider; regenerate after cloning or changing packages. |\n| Existing app upgraded to 3.6 with working legacy types | Keep its provider and paths unless native adoption is requested. A runtime upgrade does not migrate them. |\n| Explicit native adoption on 3.6+ | Root config required. Checkpoint providers\u002Fconfig, remove direct `zodern:types`, generate successfully, then merge native resolution and remove overlapping ambient types. |\n| JavaScript-only 3.6+ app wanting IntelliSense | Use `jsconfig.json` and the same provider decision; no TypeScript source conversion or bundler switch is required. |\n\nRead [declaration providers](references\u002Fdeclaration-providers.md) for the\nordered switch, native adapter\u002Fbarrel distinction, inherited configuration,\nTypeScript 7 compatibility, earlier providers and rollback. Read\n[JavaScript IntelliSense](references\u002Fjavascript-intellisense.md) for JS apps.\n\n## Verify the effective project\n\n1. Confirm generation actually ran. A direct `zodern:types` makes\n   `meteor types` skip with exit zero; `meteor create` generates for the four native\n   scaffolds above. After cloning or changing packages, run `meteor types`\n   explicitly; normal `run`, `build`, `test` and `lint` do not regenerate them.\n2. Use the app's local compiler. With native declarations, run\n   `meteor types && tsc --noEmit` in a package script; select the intended\n   config explicitly when the app has several projects.\n3. Check `tsc --listFiles --noEmit` includes application source. Appending a\n   barrel under `files` can disable implicit inclusion; retain existing source\n   patterns and exclusions. A deliberate temporary wrong type should fail;\n   remove the probe and rerun. JavaScript IntelliSense alone does not enable\n   `checkJs`; select JS checking separately when requested.\n4. Restart the editor's TypeScript server after configuration changes. If\n   CLI and editor disagree, compare selected config\u002Fcompiler before clearing\n   Meteor state or reinstalling providers.\n5. Keep generated `.meteor\u002Ftypes\u002F` untracked and unedited. Fix exposed app\n   errors rather than masking them with `any` or a new `skipLibCheck` bypass.\n\n## Diagnose the boundary\n\n| Symptom | First check |\n|---|---|\n| Native command reports nothing to do | Root `tsconfig.json` or `jsconfig.json`. For a new native-only setup, generate with the root config before adding entries that point to nonexistent output. |\n| Generation fails | Read the error; local packages may need fixing. Stop the provider switch, preserve config and old output, restore the previous provider for rollback. |\n| Ordinary imports work, scoped\u002Fsub-path imports fail | Explicit native barrel in `files` plus wildcard mapping to per-package adapters, not to the barrel. |\n| Duplicate identifiers | Overlapping providers, inherited `types: [\"meteor\"]` and app ambient declarations before symlinks. |\n| Peer types fail inside Meteor's package store | Consider `preserveSymlinks` for that specific boundary; it cannot remove duplicate providers. |\n| User service fields are `unknown`, or OAuth signatures disagree | Use [application augmentation and provider signatures](references\u002Fdeclaration-providers.md#application-user-services-and-oauth-signatures); keep generated types unedited. |\n| One community package remains untyped | Check whether the installed package publishes declarations. No generator can promise coverage for every Atmosphere package. |\n| Generated relative imports or subscription handle types disagree with runtime | Check the native declaration contract in [provider guidance](references\u002Fdeclaration-providers.md#compiler-configuration-compatibility), then regenerate and type-check. Keep generated files unedited and structural handles usable. |\n\nIf the actual task is publishing package declarations, use the official\n[Atmosphere package types documentation](https:\u002F\u002Fdocs.meteor.com\u002Fpackages\u002F7.writing-atmosphere-packages#typescript-types).\nDo not edit generated application adapters as a package-authoring solution.\n","# TypeScript in Meteor applications\n\nMake the editor and checker resolve the intended Meteor declarations and\nactually inspect application source. Preserve working provider choices unless\nthe task includes changing them. A runtime or bundler upgrade does not imply\na declaration migration.\n\nFor a runtime migration or bundler configuration request, load the owning\nskill before proposing migration steps or build configuration. This skill's\ndeclaration guidance does not supply that procedure; do not substitute a\ngeneric TypeScript\u002FRspack recipe when the owning skill is unavailable.\n\n## Identify the layer\n\n| Layer | Evidence and action |\n|---|---|\n| Compilation | The Atmosphere `typescript` package or Rspack\u002FSWC strips types. Use the build owner for syntax transforms, loaders and bundling. |\n| Declaration provider | Inspect `.meteor\u002Fpackages`, `.meteor\u002Fversions`, npm\u002Fworkspace manifests and lockfile for direct `zodern:types`, `@types\u002Fmeteor` and native opt-in. |\n| Resolution | Inspect active `tsconfig.json`\u002F`jsconfig.json`, `extends`, `files`, `include`, `exclude`, `paths` and `types`. Check the editor uses the intended project\u002Fcompiler. |\n| Checking | Inspect the installed npm `typescript` and scripts; it is separate from the Atmosphere compiler. Preserve a configured checker such as `TsCheckerRspackPlugin`. |\n\nDo not infer that an app is checked because `meteor run` or `meteor build`\nsucceeded. Conversely, do not claim an explicitly configured checker never\nruns just because SWC itself only transpiles.\n\n## Choose the provider\n\nNative package declarations are available on Meteor 3.6+.\n\n| Target and intent | Decision |\n|---|---|\n| Meteor 3 before 3.6 | Native `meteor types` is unavailable. Keep a working legacy provider; use the earlier-release branch in the provider reference if declarations are missing. |\n| New Meteor 3.6 TypeScript, TypeScript + Tailwind, Svelte or Angular app | The scaffold selects native declarations and `meteor create` generates them. Keep that provider; regenerate after cloning or changing packages. |\n| Existing app upgraded to 3.6 with working legacy types | Keep its provider and paths unless native adoption is requested. A runtime upgrade does not migrate them. |\n| Explicit native adoption on 3.6+ | Root config required. Checkpoint providers\u002Fconfig, remove direct `zodern:types`, generate successfully, then merge native resolution and remove overlapping ambient types. |\n| JavaScript-only 3.6+ app wanting IntelliSense | Use `jsconfig.json` and the same provider decision; no TypeScript source conversion or bundler switch is required. |\n\nRead [declaration providers](references\u002Fdeclaration-providers.md) for the\nordered switch, native adapter\u002Fbarrel distinction, inherited configuration,\nTypeScript 7 compatibility, earlier providers and rollback. Read\n[JavaScript IntelliSense](references\u002Fjavascript-intellisense.md) for JS apps.\n\n## Verify the effective project\n\n1. Confirm generation actually ran. A direct `zodern:types` makes\n   `meteor types` skip with exit zero; `meteor create` generates for the four native\n   scaffolds above. After cloning or changing packages, run `meteor types`\n   explicitly; normal `run`, `build`, `test` and `lint` do not regenerate them.\n2. Use the app's local compiler. With native declarations, run\n   `meteor types && tsc --noEmit` in a package script; select the intended\n   config explicitly when the app has several projects.\n3. Check `tsc --listFiles --noEmit` includes application source. Appending a\n   barrel under `files` can disable implicit inclusion; retain existing source\n   patterns and exclusions. A deliberate temporary wrong type should fail;\n   remove the probe and rerun. JavaScript IntelliSense alone does not enable\n   `checkJs`; select JS checking separately when requested.\n4. Restart the editor's TypeScript server after configuration changes. If\n   CLI and editor disagree, compare selected config\u002Fcompiler before clearing\n   Meteor state or reinstalling providers.\n5. Keep generated `.meteor\u002Ftypes\u002F` untracked and unedited. Fix exposed app\n   errors rather than masking them with `any` or a new `skipLibCheck` bypass.\n\n## Diagnose the boundary\n\n| Symptom | First check |\n|---|---|\n| Native command reports nothing to do | Root `tsconfig.json` or `jsconfig.json`. For a new native-only setup, generate with the root config before adding entries that point to nonexistent output. |\n| Generation fails | Read the error; local packages may need fixing. Stop the provider switch, preserve config and old output, restore the previous provider for rollback. |\n| Ordinary imports work, scoped\u002Fsub-path imports fail | Explicit native barrel in `files` plus wildcard mapping to per-package adapters, not to the barrel. |\n| Duplicate identifiers | Overlapping providers, inherited `types: [\"meteor\"]` and app ambient declarations before symlinks. |\n| Peer types fail inside Meteor's package store | Consider `preserveSymlinks` for that specific boundary; it cannot remove duplicate providers. |\n| User service fields are `unknown`, or OAuth signatures disagree | Use [application augmentation and provider signatures](references\u002Fdeclaration-providers.md#application-user-services-and-oauth-signatures); keep generated types unedited. |\n| One community package remains untyped | Check whether the installed package publishes declarations. No generator can promise coverage for every Atmosphere package. |\n| Generated relative imports or subscription handle types disagree with runtime | Check the native declaration contract in [provider guidance](references\u002Fdeclaration-providers.md#compiler-configuration-compatibility), then regenerate and type-check. Keep generated files unedited and structural handles usable. |\n\nIf the actual task is publishing package declarations, use the official\n[Atmosphere package types documentation](https:\u002F\u002Fdocs.meteor.com\u002Fpackages\u002F7.writing-atmosphere-packages#typescript-types).\nDo not edit generated application adapters as a package-authoring solution.\n",{"name":5,"license":15,"metadata":24,"description":30},{"area":25,"kind":26,"author":9,"meteor":27,"tagline":28,"docs_synced_at":29},"build","knowledge",">=3.0","Configure Meteor app declarations, TypeScript and JavaScript IntelliSense, and reliable local\u002FCI type-checking.","2026-10-07","Use when setting up or repairing Meteor application declarations, TypeScript configuration, JavaScript IntelliSense, or local and CI type-checking. Triggers on meteor types, meteor\u002F* imports resolving to any, missing declarations, duplicate Meteor identifiers, zodern:types, @types\u002Fmeteor, .meteor\u002Ftypes, tsconfig.json, jsconfig.json, and tsc --noEmit in a Meteor app. Use this skill when choosing or migrating declaration providers without changing the app's runtime or bundler. For a Meteor 2-to-3 runtime migration use migrate-to-meteor-3 first; for SWC\u002FRspack compilation use meteor-modern-build-stack or migrate-to-rspack. General TypeScript language questions and Atmosphere declaration publishing are outside this app scope.\n","main","0b022e17f4fcd7753440de79bd512603cf832de3","skills\u002Fmeteor-typescript",3,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills","https:\u002F\u002Fdocs.meteor.com\u002F","https:\u002F\u002Fgithub.com\u002Fmeteor","https:\u002F\u002Fmeteor.com\u002F","2026-11-10 23:47:25",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add meteor\u002Fagent-skills --skill meteor-typescript",{"tool":46,"command":47},"bunx","bunx skills add meteor\u002Fagent-skills --skill meteor-typescript",{"tool":49,"command":50},"pnpm","pnpm dlx skills add meteor\u002Fagent-skills --skill meteor-typescript","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-typescript\u002FSKILL.md",true,[54,60,64],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fdeclaration-providers.md","REFERENCE","参考文档",10574,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-typescript\u002Freferences\u002Fdeclaration-providers.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Feval-cases.md",11445,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-typescript\u002Freferences\u002Feval-cases.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fjavascript-intellisense.md",2483,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-typescript\u002Freferences\u002Fjavascript-intellisense.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M72VTT678CAVGTRHSCCZMNSN","migrate-to-rspack","Use when migrating an existing Meteor app to Rspack (Meteor 3.4+), or upgrading Rspack 1 to 2 on Meteor 3.6. Triggers on nested imports, mainModule entry points, server-only apps, replacing fourseven:scss \u002F meteor\u002Fless \u002F coffeescript \u002F jorgenvatle:vite \u002F zodern:melte with loaders, Svelte\u002FTypeScript preprocessing or Lingui SWC plugin failures after upgrade, CommonJS default-import interop, module.exports in client graphs, Node built-ins in browser code, _build \u002F build-assets \u002F build-chunks, .meteorignore hiding handoff files, dynamic chunks under ROOT_URL, meteor.modules for CSS\u002FHTML, resolve.symlinks or resolve.alias migration, automatic dependency updates and immutable CI\u002FDocker builds. Use this skill when the user asks about migration compatibility or a build plugin's Rspack replacement. For new-app setup and rspack.config.js helpers, use meteor-modern-build-stack instead.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-to-rspack\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M72VTMKP4FEEE8KPTBW0TS0Y","migrate-to-meteor-3","Use when migrating a Meteor 2.x application to Meteor 3.x. Triggers on callAsync, *Async Mongo, removed Fibers, implicit-global ReferenceError, lost Blaze reactivity, a publish function returning a Promise, a scheduler dropping a Promise, a read API receiving update modifiers, async allow\u002Fdeny, an Iron Router controller not running, \"Method stub took too long\", Atmosphere resolution, Express 5 WebApp handlers, lost async context, rawCollection callbacks, TypeScript declaration failures during upgrades, useTracker, and useSubscribe. Use this skill when the user asks about upgrading Meteor, async caller propagation, iterators with await, or replacing and forking packages. Standalone declarations and type-checking belong to meteor-typescript.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigrate-to-meteor-3\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M72VT9PART27QBM306JC3PGN","meteor-testing","Use when setting up, designing, writing, or repairing tests and test harnesses in a Meteor 3 app. Triggers on meteortesting:mocha, --driver-package, TEST_WATCH, TEST_BROWSER_DRIVER, MOCHA_GREP, meteor.testModule, focused tests, .only, Meteor.server.method_handlers, Meteor.server.publish_handlers, DDP.connect, --full-app integration mode, sinon, async test signatures, Playwright\u002FCypress E2E. Use this skill when the user asks about test runners, asks about testing publications, or asks about Jest vs Mocha in Meteor. For a failing, hanging, or flaky test whose failing layer or root cause is unknown, use meteor-debugging before changing the test or app.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-testing\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M72VT4X6FMW8YDG4GNR8FKNJ","meteor-security","Use when auditing or hardening a Meteor 3 application. Triggers on missing check() on method arguments, missing this.userId guards on publications, browser-policy CSP, DDPRateLimiter rules, oauth-encryption via Accounts.config oauthSecretKey, audit-argument-checks, allow\u002Fdeny legacy patterns, BrowserPolicy.content.disallowInlineScripts, BrowserPolicy.framing.disallow. Use this skill when the user asks about hardening, asks about a security review, or asks about CSP for a third-party script (Stripe, Google Maps, fonts).","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-security\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M72VSY34AX3TF3AF68E5M4K9","meteor-react","Use when building or debugging React interfaces in Meteor 3: meteor create --react, createRoot, JSX or TSX entry points, Rspack React detection, Fast Refresh, react-meteor-data, useTracker, useSubscribe, useFind, withTracker, Suspense, and Tracker.withComputation. Triggers on isLoading being treated as a boolean, useFind receiving fetch(), stale closure inputs, duplicate tracker side effects, unstable Suspense keys, lost reactivity after await, state reset after refresh, or React tests leaking computations. Use this skill when the user asks about a React skeleton, React Compiler, React-specific rspack.config rules, reactive data hooks, or classic versus Suspense integration. Route general bundler configuration to meteor-modern-build-stack and Meteor 2 upgrades to migrate-to-meteor-3.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-react\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M72VSJQ3XWNA0SHZJ0F9SFF1","meteor-mongo-minimongo","Use when authoring or debugging Mongo queries in Meteor 3. Triggers on Mongo.Collection, find\u002FfindOne, server async vs client Minimongo sync, oplog vs change streams, indexes, selectors, modifiers, projections. Use this skill when the user asks about Mongo on the server or asks about Minimongo on the client.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-mongo-minimongo\u002FSKILL.md",[],[]]