メニュー
Use when diagnosing Preact Signals bugs, stale renders, missing updates, memory leaks, duplicate Preact copies, React transform misses, devtools/debug output, SSR differences, or issues that need a minimal reproduction.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | preact-signals-debugging |
| description | Use when diagnosing Preact Signals bugs, stale renders, missing updates, memory leaks, duplicate Preact copies, React transform misses, devtools/debug output, SSR differences, or issues that need a minimal reproduction. |
Classify the failure before editing code: core reactivity, Preact adapter, React adapter, no-build/CDN singleton, transform configuration, SSR, or devtools/debugging. Most reported issues reduce to one of those boundaries.
@preact/signals-core, @preact/signals, @preact/signals-react, @preact/signals-react-transform, preact, react..value, not deep mutation..value read actually executes at runtime.{signal} or {signal.value} and whether direct DOM optimization is expected.useSignals() is present.| Symptom | Likely Boundary | Next Skill |
|---|---|---|
| Effect logs but component does not rerender | Adapter or duplicate Preact | preact-signals-preact-integration or preact-signals-no-build |
| Object field changed but subscribers stale | Core signal semantics | preact-signals-core |
React component reads .value but does not update | React tracking setup | preact-signals-react-integration |
Signal works in text but not checked or disabled | React DOM attribute limitation | preact-signals-react-integration |
For children ignore parent variable changes | Cached utility children | preact-signals-preact-integration |
| CDN example behaves differently from npm | Version drift or duplicate Preact | preact-signals-no-build |
For upstream issues, require a small StackBlitz, CodeSandbox, CodePen, or repository. Screenshots and built output are not enough when maintainers need to inspect runtime code paths.
Keep the reproduction focused:
preact/debug in Preact apps for development warnings.@preact/signals-debug and the devtools packages when debugging graph behavior.DEBUG=signals:react-transform:* to inspect transform decisions.node_modules/@preact/signals-debug/README.md (https://github.com/preactjs/signals/blob/main/packages/debug/README.md)Use when hardening npm package release workflows with trusted publishing, OIDC, GitHub environments, pinned GitHub Actions, disabled publish-path caching, Changesets release PRs, direct tag-based npm publish flows, staged publishing, or npm release-supply-chain reviews.
Use when migrating React code or libraries to Preact, configuring preact/compat, bundler aliases, react/jsx-runtime, react-dom, Jest, Node SSR aliases, or diagnosing duplicate React/Preact copies and compat behavior differences.
Use when enabling preact/debug, interpreting Preact debug warnings, invalid HTML nesting or table parser problems, hydration mismatch diagnostics, duplicate keys, invalid refs/events, or component stack traces.
Use when building or debugging Preact forms, controlled or uncontrolled inputs, onInput versus onChange, checkbox, radio, select, textarea behavior, hydration of form state, cursor preservation, or compat event normalization.
Use when Preact hooks fail with invalid hook calls, __H undefined or null errors, mixed CJS/ESM imports, no-build import maps, duplicate Preact copies, useId SSR mismatches, or effect scheduling problems.
Use when Preact SSR, prerendering, hydrate(), Suspense, lazy, streaming SSR, renderToStringAsync(), or browser-parsed HTML produces hydration warnings, duplicate nodes, mismatched DOM, lost focus, stale fallback markup, or client-only conditional render bugs.