菜单
Extends or fixes renderer-facing Electron APIs exposed through the preload script and contextBridge. Use when adding IPC-like surface area, typing window.faContentBridgeAPIs, editing src-electron/contentBridgeAPIs, or extending shared IPC channel names in electron-ipc-bridge.ts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Runs and extends Fantasia Archive tests: Vitest unit tests vs Playwright component and E2E tests, including rebuild-before-Playwright rules and file naming. Use when writing tests, debugging CI, or when the user mentions Vitest, Playwright, component tests, or e2e.
Per-tab editState on opened workspace documents: preview (read-only) vs edit (inputs). Use when adding DocumentWorkspacePage fields, tab session state, or opened_documents snapshot columns.
Maintains the English in-app changelog at i18n/en-US/documents/changeLog.md in strict sync with package.json version, without any automatic version bumping. Changelog text must be user- or release-relevant only—never internal QA, Git meta (commits/pushes), or “updated changelog”. Prefer editing the log in the same commit as the work, before push. Use after substantive app, UX, or user-facing docs changes, or when the user asks for release notes.
Default post-edit verification for Fantasia Archive agents: ESLint on touched paths, full vue-tsc, stylelint on touched styles, and yarn vitest run only on specs connected to the edit batch. Full yarn testbatch:verify is reserved for final cleanup, git commit, and explicit user requests. Use after substantive code edits before reporting work done.
Sets up and runs Fantasia Archive locally using Yarn, Node.js 22.22 or newer, and Quasar Electron mode. Use when installing dependencies, choosing dev vs production build commands, or when the user mentions environment setup, CLI, or first run.
Works on Fantasia Archive Electron main process: app lifecycle, window management, platform tweaks, native integrations, and ipcMain registration (register*Ipc + electron-ipc-bridge channel names). Use when editing electron-main.ts, src-electron/mainScripts/, or main-side tests.
| name | fantasia-electron-preload |
| description | Extends or fixes renderer-facing Electron APIs exposed through the preload script and contextBridge. Use when adding IPC-like surface area, typing window.faContentBridgeAPIs, editing src-electron/contentBridgeAPIs, or extending shared IPC channel names in electron-ipc-bridge.ts. |
src-electron/: AGENTS.md comment rules — no Markdown emphasis; single quotes for refselectron-preload.ts → contextBridge.exposeInMainWorld('faContentBridgeAPIs', apiObject)window.faContentBridgeAPIs — src/globals.d.tscontentBridgeAPIs/*.ts per API (window control, keybinds, project management, projectContentAPI, …)ipcRenderer.invoke + ipcMain.handle. sendSync last resort onlyelectron-ipc-bridge.ts — FA_*_IPC constants; never duplicate string literalsregister*Ipc.ts wired from startApp()contentBridgeAPIs/*.tstypes/I_<Name>.tselectron-ipc-bridge.ts + register*Ipc.ts + startupcontentBridgeAPIs/<name>.tsapiObject in electron-preload.tsglobals.d.tscontentBridgeAPIs/_tests/, ipcManagement/_tests/ — dev scoped connected specs during edits; full yarn testbatch:verify enforces 95% on src-electron before commitnodeIntegration in renderershell, paths, etc.invoke — no @electron/remote without documented reasonneverthrow in preload — Promise chains; see neverthrow.mdcShared types → types/. See types-folder.mdc.