ワンクリックで
verify
Runtime-verify a renderer change by driving the app in a browser — build/launch/drive recipe for Nova Spektr.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Runtime-verify a renderer change by driving the app in a browser — build/launch/drive recipe for Nova Spektr.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when adding, changing or reviewing a user-typed search/filter over a list (accounts, wallets, contacts, validators, operations, assets) — a search input, combobox or picker filtering rows by query. Also use when a user reports search "not finding" an item they can see in the list, or results disappearing while typing a visible name.
Maintain feature spec READMEs and the Feature Map index. Use when creating a new feature or aggregate, materially changing the behaviour of an existing one, writing or updating a spec README, or when asked about feature documentation coverage.
| name | verify |
| description | Runtime-verify a renderer change by driving the app in a browser — build/launch/drive recipe for Nova Spektr. |
pnpm start:renderer serves the renderer at https://localhost:3000 (Vite, ~30s until first page finishes bundling). The full Electron pnpm start is NOT needed for renderer-only changes — the app works in a plain browser.localhost only — https://127.0.0.1:3000 throws a cert interstitial. To get an isolated storage origin (fresh IndexedDB/localStorage without touching existing dev data), start a second instance: pnpm start:renderer --port 3001 — same cert hostname, different origin.localhost:3000 and :3001 may already contain the developer's real dev profiles — treat them as user data: read-only driving is fine, don't import DBs or clear storage, and revert any localStorage flag you flip.tests/system/data/db/ (e.g. transfers/transfers_tests_db.json). Only do this on a fresh origin.type actions drop characters in the recipient Combobox — SS58 addresses arrive mangled and fail checksum validation. Set values via the native setter instead:
Object.getOwnPropertyDescriptor(HTMLInputElement.prototype,'value').set.call(input, addr); input.dispatchEvent(new Event('input',{bubbles:true}))13mAjFVjFDpfa42k2dLdSnUyrSzK8vAySsoudnxX2EKVtfaq (from the system-test fixtures). Don't type addresses from memory — checksum fails read as "Address has incorrect format".navigate calls do NOT reload the page — persisted stores (effector-storage persist) only re-hydrate on a real location.reload(). Same-tab localStorage.setItem does not fire storage events either.await import('/@fs/<abs-repo-path>/src/renderer/aggregates/<x>/model.ts') then .getState() on stores. knownCount-style sanity values tell you whether you got the app's instance.address-book-has-ever-connected ('true'/absent) — flipping it + reload moves the app between never-connected and disconnected (unverifiable) modes without a backend. Fully-connected mode needs real backend auth; cover it with integration tests instead.find for them rather than scrolling blindly.