[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72VRXQAYATWBXE2Z4JADQ2C":3,"skill-same:01M72VRXQAYATWBXE2Z4JADQ2C":87},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M72VRXQAYATWBXE2Z4JADQ2C","meteor-debugging",null,"Use when diagnosing an unexplained failure in a Meteor 3 application before the failing layer or fix is known. Triggers on server crashes, client-only errors, Errors prevented startup, Meteor App - Error, stuck subscriptions, DDP or WebSocket disconnects, Minimongo\u002Fserver data mismatches, hanging or flaky tests, slow builds, --inspect, console.log, .only, Playwright traces, Instrumentation lifecycle events, or requests to debug a Meteor app. Use this skill when evidence must distinguish Meteor tool, server, client, data, test, browser, mobile, or production boundaries. For test setup and authoring use meteor-testing; after confirming a domain cause, hand the repair to the owning skill.","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-debugging\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: meteor-debugging\ndescription: >\n  Use when diagnosing an unexplained failure in a Meteor 3 application before\n  the failing layer or fix is known. Triggers on server crashes, client-only\n  errors, Errors prevented startup, Meteor App - Error, stuck subscriptions,\n  DDP or WebSocket disconnects, Minimongo\u002Fserver\n  data mismatches, hanging or flaky tests, slow builds, --inspect, console.log,\n  .only, Playwright traces, Instrumentation lifecycle events, or requests to debug a Meteor app. Use this skill\n  when evidence must distinguish Meteor tool, server, client, data, test,\n  browser, mobile, or production boundaries. For test setup and authoring use\n  meteor-testing; after confirming a domain cause, hand the repair to the\n  owning skill.\nmetadata:\n  author: meteor\n  kind: workflow\n  meteor: \">=3.0\"\n  area: ops\n  tagline: \"Diagnose Meteor 3 failures across builds, server\u002Fclient runtime, DDP, Mongo, tests, browsers, mobile, and production.\"\n  bundle: [\"essentials\", \"fullstack\", \"ops\"]\n  docs_synced_at: \"2026-10-07\"\nlicense: MIT\n---\n\n# Debug Meteor applications\n\nFind the first failing boundary before changing behavior. Produce a stable\nreproduction, evidence for one cause, and a verification target. Then use the\nskill that owns the repair.\n\n## Diagnosis loop\n\n1. Record the exact symptom, complete error and stack, command or user action,\n   Meteor release, resolved Atmosphere and npm versions, environment, and last\n   known working state.\n2. Reproduce with the narrowest stable command or action before editing.\n3. Classify the first uncertain boundary with the table below.\n4. Read existing evidence before adding instrumentation. Compare client and\n   server output, recent changes, and passing versus failing environments.\n5. Add one targeted observation only when current evidence cannot answer the\n   question. Do not combine a diagnostic change with a speculative fix.\n6. State one falsifiable hypothesis and the observation that would reject it.\n7. Change one variable, reproduce, and trace a bad value or event backward to\n   its origin.\n8. Fix the confirmed cause through the owning skill. Add a regression at the\n   lowest reliable layer when the failure can recur.\n9. Re-run the focused reproduction, then the affected suite or\n   production-like check. Remove temporary diagnostics and artifacts.\n\nIf several evidence-backed hypotheses fail, revisit the boundary map and\nassumptions before stacking mitigations or widening the change.\n\n## Select the boundary\n\n| Symptom | First evidence | Read |\n|---|---|---|\n| Build stalls, compilation error, rebuild regression, Rspack or SWC failure | Full build output, `--verbose`, exact release and build-package versions | [Build debugging](references\u002Fbuild-debugging.md) |\n| Server crashes before startup or fails in a method, publication, job, or hook | Earliest server stack, startup order, request-correlated evidence | [Runtime and inspector](references\u002Fruntime-and-inspector.md) |\n| Client stack, stale render, reactive loop, or client\u002Fserver disagreement | Browser stack, rendered state, reactive invalidation, server comparison | [Runtime and inspector](references\u002Fruntime-and-inspector.md), then the React or Blaze skill |\n| Missing documents, stuck subscription, reconnect, or proxy\u002FWebSocket symptom | Server query, publication output, DDP state, subscription readiness, Minimongo | [DDP and data](references\u002Fddp-and-data.md) |\n| Current output cannot distinguish an entry, guard, branch, state change, or event order | A small set of redacted boundary observations | [Logs and instrumentation](references\u002Flogs-and-instrumentation.md) |\n| Meteor Mocha failure, suite-only failure, async flake, or browser E2E failure | Full hook output, client\u002Fserver test counts, existing report and trace | [Tests and browser](references\u002Ftests-and-browser.md) |\n| Cordova or HCP problem, device-only failure, or live incident | Device logs and versions; deployment logs, health, metrics, release diff | [Mobile and production](references\u002Fmobile-and-production.md) |\n\nA syntax error needs its stack, not browser tracing. A browser-only hydration\nrace needs client evidence, not a server inspector. Use the smallest tool that\ncan reject the current hypothesis.\n\n## Evidence rules\n\n- Label runtime side and operation in temporary logs. Include a request or\n  event identifier only when concurrent flows can interleave.\n- Record selected, redacted fields. Never log credentials, tokens, cookies,\n  authorization headers, private settings, unrestricted method arguments, or\n  full user documents.\n- Treat `console.log` as temporary instrumentation. Use `meteor\u002Flogging` or the\n  application's established structured logger for evidence that must persist.\n- For server lifecycle evidence on Meteor 3.6, use the optional\n  `instrumentation` package through [Logs and instrumentation](references\u002Flogs-and-instrumentation.md).\n  Earlier releases retain targeted logs; listeners observe, not authorize.\n- Use `.only` only as temporary local test focus when the runner and execution\n  mode support it. Remove it and run the broader suite before handoff.\n- Prefer observable readiness over sleeps: subscription ready, settled method,\n  expected document, visible UI, or a specific browser event.\n- Inspect existing Playwright reports and traces before starting an interactive\n  browser. For a `playwright-cli` request, first check whether the executable\n  is available. If it is unavailable, obtain authority before installation or\n  browser downloads. Explicitly report that availability result and request\n  the authority rather than only asking for the application URL. Use it only\n  for a real browser boundary.\n- For an authorized ad hoc `playwright-cli` reproduction: **MUST** run\n  `snapshot`, `console`, and `requests`, start tracing before the failing\n  action, stop tracing immediately after it, and close the browser session.\n  Do not substitute source inspection for this browser evidence or omit the\n  trace because the console or network already suggests a cause.\n- Use only an application path or URL the user placed in scope. If the current\n  workspace has no app and the prompt gives no URL, ask for one. Do not scan\n  unrelated directories, processes, or ports to discover an application.\n- Read through `meteor shell` and `meteor mongo` before mutating. Never use\n  `meteor reset --db` as a diagnostic shortcut.\n- On production, do not expose an inspector, deploy a debug build, retain\n  secret-bearing traces, or experiment on live data.\n\n## Handoffs\n\n| Confirmed cause | Continue with |\n|---|---|\n| Test setup, design, driver, fixture, or new regression structure | `meteor-testing` |\n| SWC, Rspack, watcher, cache, build graph, or generated handoff | `meteor-modern-build-stack` or `migrate-to-rspack` |\n| Confirmed Cordova platform, native plugin\u002Fconfiguration, device networking, signing, or native HCP compatibility | `meteor-native` |\n| Method, publication, Mongo\u002FMinimongo, React, Blaze, accounts, or security | Matching domain skill |\n| Galaxy, container, proxy, environment, health check, or rollout | `meteor-deployment` |\n| Documented community package behavior | `meteor-community-packages`, then the upstream repository |\n| Pure Node.js, browser, database, or runner failure with no Meteor boundary | General debugging guidance |\n\n## Cleanup\n\nBefore handoff:\n\n1. Remove only the logs, `debugger` statements, `.only` markers, pauses,\n   temporary routes, and debug settings added for this investigation.\n2. Delete or protect screenshots, traces, profiles, saved browser state, and\n   dumps according to their data sensitivity.\n3. Re-run the original reproduction and the affected suite.\n4. Report the confirmed cause, evidence, fix, verification, and any remaining\n   uncertainty.\n\n## Anti-patterns\n\n- Edit the assertion before checking setup, async completion, and skipped\n  client coverage.\n- Add logs across the application without a hypothesis.\n- Serialize every runtime object indiscriminately. Circular values, reactive\n  wrappers, getters, binary data, and large documents need selected snapshots.\n- Treat a focused passing test as success when the suite still fails.\n- Add arbitrary sleeps, broad selectors, retries, or heap increases until the\n  symptom disappears.\n- Install browser tooling or scaffold tests for a server, build, or database\n  failure.\n\n## References\n\n- [Runtime and inspector](references\u002Fruntime-and-inspector.md)\n- [Logs and instrumentation](references\u002Flogs-and-instrumentation.md)\n- [Tests and browser](references\u002Ftests-and-browser.md)\n- [Build debugging](references\u002Fbuild-debugging.md)\n- [DDP and data](references\u002Fddp-and-data.md)\n- [Mobile and production](references\u002Fmobile-and-production.md)\n- [Evaluation cases](references\u002Feval-cases.md)\n","# Debug Meteor applications\n\nFind the first failing boundary before changing behavior. Produce a stable\nreproduction, evidence for one cause, and a verification target. Then use the\nskill that owns the repair.\n\n## Diagnosis loop\n\n1. Record the exact symptom, complete error and stack, command or user action,\n   Meteor release, resolved Atmosphere and npm versions, environment, and last\n   known working state.\n2. Reproduce with the narrowest stable command or action before editing.\n3. Classify the first uncertain boundary with the table below.\n4. Read existing evidence before adding instrumentation. Compare client and\n   server output, recent changes, and passing versus failing environments.\n5. Add one targeted observation only when current evidence cannot answer the\n   question. Do not combine a diagnostic change with a speculative fix.\n6. State one falsifiable hypothesis and the observation that would reject it.\n7. Change one variable, reproduce, and trace a bad value or event backward to\n   its origin.\n8. Fix the confirmed cause through the owning skill. Add a regression at the\n   lowest reliable layer when the failure can recur.\n9. Re-run the focused reproduction, then the affected suite or\n   production-like check. Remove temporary diagnostics and artifacts.\n\nIf several evidence-backed hypotheses fail, revisit the boundary map and\nassumptions before stacking mitigations or widening the change.\n\n## Select the boundary\n\n| Symptom | First evidence | Read |\n|---|---|---|\n| Build stalls, compilation error, rebuild regression, Rspack or SWC failure | Full build output, `--verbose`, exact release and build-package versions | [Build debugging](references\u002Fbuild-debugging.md) |\n| Server crashes before startup or fails in a method, publication, job, or hook | Earliest server stack, startup order, request-correlated evidence | [Runtime and inspector](references\u002Fruntime-and-inspector.md) |\n| Client stack, stale render, reactive loop, or client\u002Fserver disagreement | Browser stack, rendered state, reactive invalidation, server comparison | [Runtime and inspector](references\u002Fruntime-and-inspector.md), then the React or Blaze skill |\n| Missing documents, stuck subscription, reconnect, or proxy\u002FWebSocket symptom | Server query, publication output, DDP state, subscription readiness, Minimongo | [DDP and data](references\u002Fddp-and-data.md) |\n| Current output cannot distinguish an entry, guard, branch, state change, or event order | A small set of redacted boundary observations | [Logs and instrumentation](references\u002Flogs-and-instrumentation.md) |\n| Meteor Mocha failure, suite-only failure, async flake, or browser E2E failure | Full hook output, client\u002Fserver test counts, existing report and trace | [Tests and browser](references\u002Ftests-and-browser.md) |\n| Cordova or HCP problem, device-only failure, or live incident | Device logs and versions; deployment logs, health, metrics, release diff | [Mobile and production](references\u002Fmobile-and-production.md) |\n\nA syntax error needs its stack, not browser tracing. A browser-only hydration\nrace needs client evidence, not a server inspector. Use the smallest tool that\ncan reject the current hypothesis.\n\n## Evidence rules\n\n- Label runtime side and operation in temporary logs. Include a request or\n  event identifier only when concurrent flows can interleave.\n- Record selected, redacted fields. Never log credentials, tokens, cookies,\n  authorization headers, private settings, unrestricted method arguments, or\n  full user documents.\n- Treat `console.log` as temporary instrumentation. Use `meteor\u002Flogging` or the\n  application's established structured logger for evidence that must persist.\n- For server lifecycle evidence on Meteor 3.6, use the optional\n  `instrumentation` package through [Logs and instrumentation](references\u002Flogs-and-instrumentation.md).\n  Earlier releases retain targeted logs; listeners observe, not authorize.\n- Use `.only` only as temporary local test focus when the runner and execution\n  mode support it. Remove it and run the broader suite before handoff.\n- Prefer observable readiness over sleeps: subscription ready, settled method,\n  expected document, visible UI, or a specific browser event.\n- Inspect existing Playwright reports and traces before starting an interactive\n  browser. For a `playwright-cli` request, first check whether the executable\n  is available. If it is unavailable, obtain authority before installation or\n  browser downloads. Explicitly report that availability result and request\n  the authority rather than only asking for the application URL. Use it only\n  for a real browser boundary.\n- For an authorized ad hoc `playwright-cli` reproduction: **MUST** run\n  `snapshot`, `console`, and `requests`, start tracing before the failing\n  action, stop tracing immediately after it, and close the browser session.\n  Do not substitute source inspection for this browser evidence or omit the\n  trace because the console or network already suggests a cause.\n- Use only an application path or URL the user placed in scope. If the current\n  workspace has no app and the prompt gives no URL, ask for one. Do not scan\n  unrelated directories, processes, or ports to discover an application.\n- Read through `meteor shell` and `meteor mongo` before mutating. Never use\n  `meteor reset --db` as a diagnostic shortcut.\n- On production, do not expose an inspector, deploy a debug build, retain\n  secret-bearing traces, or experiment on live data.\n\n## Handoffs\n\n| Confirmed cause | Continue with |\n|---|---|\n| Test setup, design, driver, fixture, or new regression structure | `meteor-testing` |\n| SWC, Rspack, watcher, cache, build graph, or generated handoff | `meteor-modern-build-stack` or `migrate-to-rspack` |\n| Confirmed Cordova platform, native plugin\u002Fconfiguration, device networking, signing, or native HCP compatibility | `meteor-native` |\n| Method, publication, Mongo\u002FMinimongo, React, Blaze, accounts, or security | Matching domain skill |\n| Galaxy, container, proxy, environment, health check, or rollout | `meteor-deployment` |\n| Documented community package behavior | `meteor-community-packages`, then the upstream repository |\n| Pure Node.js, browser, database, or runner failure with no Meteor boundary | General debugging guidance |\n\n## Cleanup\n\nBefore handoff:\n\n1. Remove only the logs, `debugger` statements, `.only` markers, pauses,\n   temporary routes, and debug settings added for this investigation.\n2. Delete or protect screenshots, traces, profiles, saved browser state, and\n   dumps according to their data sensitivity.\n3. Re-run the original reproduction and the affected suite.\n4. Report the confirmed cause, evidence, fix, verification, and any remaining\n   uncertainty.\n\n## Anti-patterns\n\n- Edit the assertion before checking setup, async completion, and skipped\n  client coverage.\n- Add logs across the application without a hypothesis.\n- Serialize every runtime object indiscriminately. Circular values, reactive\n  wrappers, getters, binary data, and large documents need selected snapshots.\n- Treat a focused passing test as success when the suite still fails.\n- Add arbitrary sleeps, broad selectors, retries, or heap increases until the\n  symptom disappears.\n- Install browser tooling or scaffold tests for a server, build, or database\n  failure.\n\n## References\n\n- [Runtime and inspector](references\u002Fruntime-and-inspector.md)\n- [Logs and instrumentation](references\u002Flogs-and-instrumentation.md)\n- [Tests and browser](references\u002Ftests-and-browser.md)\n- [Build debugging](references\u002Fbuild-debugging.md)\n- [DDP and data](references\u002Fddp-and-data.md)\n- [Mobile and production](references\u002Fmobile-and-production.md)\n- [Evaluation cases](references\u002Feval-cases.md)\n",{"name":5,"license":15,"metadata":24,"description":33},{"area":25,"kind":26,"author":9,"bundle":27,"meteor":30,"tagline":31,"docs_synced_at":32},"ops","workflow",[28,29,25],"essentials","fullstack",">=3.0","Diagnose Meteor 3 failures across builds, server\u002Fclient runtime, DDP, Mongo, tests, browsers, mobile, and production.","2026-10-07","Use when diagnosing an unexplained failure in a Meteor 3 application before the failing layer or fix is known. Triggers on server crashes, client-only errors, Errors prevented startup, Meteor App - Error, stuck subscriptions, DDP or WebSocket disconnects, Minimongo\u002Fserver data mismatches, hanging or flaky tests, slow builds, --inspect, console.log, .only, Playwright traces, Instrumentation lifecycle events, or requests to debug a Meteor app. Use this skill when evidence must distinguish Meteor tool, server, client, data, test, browser, mobile, or production boundaries. For test setup and authoring use meteor-testing; after confirming a domain cause, hand the repair to the owning skill.\n","main","0b022e17f4fcd7753440de79bd512603cf832de3","skills\u002Fmeteor-debugging",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-12 03:34:42",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add meteor\u002Fagent-skills --skill meteor-debugging",{"tool":49,"command":50},"bunx","bunx skills add meteor\u002Fagent-skills --skill meteor-debugging",{"tool":52,"command":53},"pnpm","pnpm dlx skills add meteor\u002Fagent-skills --skill meteor-debugging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-debugging\u002FSKILL.md",true,[57,63,67,71,75,79,83],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fbuild-debugging.md","REFERENCE","参考文档",11938,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-debugging\u002Freferences\u002Fbuild-debugging.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fddp-and-data.md",6093,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-debugging\u002Freferences\u002Fddp-and-data.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Feval-cases.md",21839,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-debugging\u002Freferences\u002Feval-cases.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Flogs-and-instrumentation.md",7339,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-debugging\u002Freferences\u002Flogs-and-instrumentation.md",{"path":76,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fmobile-and-production.md",3361,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-debugging\u002Freferences\u002Fmobile-and-production.md",{"path":80,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fruntime-and-inspector.md",3670,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-debugging\u002Freferences\u002Fruntime-and-inspector.md",{"path":84,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ftests-and-browser.md",7243,"https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-debugging\u002Freferences\u002Ftests-and-browser.md",[88,95,102,109,116,123],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M72VTEG9AB229C97SRKZ2FFG","meteor-typescript","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.","https:\u002F\u002Fgithub.com\u002Fmeteor\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmeteor-typescript\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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",[],[]]