// Migrates Fantasia Archive features to two-level functions + managers layout: pure scripts/functions/, *_manager.ts wiring (underscore suffix, e.g. dialogFoo_manager.ts), thin Vue SFCs. Use when refactoring features, fixing fa-two-level ESLint violations, or adding new UI.
| name | fantasia-two-level-architecture |
| description | Migrates Fantasia Archive features to two-level functions + managers layout: pure scripts/functions/, *_manager.ts wiring (underscore suffix, e.g. dialogFoo_manager.ts), thin Vue SFCs. Use when refactoring features, fixing fa-two-level ESLint violations, or adding new UI. |
scripts/functions/ and move pure logic there. No imports except import type from app/types/**. Pass i18n.global.t, stores, Result, and bridge APIs as arguments from the manager.scripts/<feature>_manager.ts (suffix _manager.ts, not .manager.ts). Import NPM, Pinia, i18n, _data/, and functions/* here only; do not define functions in the manager—use create… factories from functions/ and export const bindings (ESLint fa-two-level/manager-wiring-only). Do not add a second file that only re-exports that manager under a legacy name—import the manager (or functions/) directly from call sites..vue file: defineProps, child *.vue imports, one use… from the manager.scripts/*.ts modules in that feature (ESLint errors once functions/ exists)._tests imports; add functions/_tests for pure units.yarn lint:eslint on the feature folder, then yarn testbatch:verify.| Message | Fix |
|---|---|
| functions/ must not use value imports | Move the import to *_manager.ts and pass the value into the function. |
| Legacy script module not allowed beside scripts/functions/ | Merge into functions/ + manager or delete after move. |
| Vue script may only import the feature *_manager.ts | Remove store/script imports from the SFC; expose via manager return. |
| Import functions/ only from *_manager.ts | Import the function module only from the manager (tests excepted). |
| Re-export shim file | Delete the alias module; point imports at the defining *_manager.ts or functions/*.ts. |
| manager-wiring-only | Move function bodies to functions/ (or sibling wiring module); manager exports const from create…(deps). |
| manager-wiring-only (class) | Move the class to a non-*_manager.ts module (for example faFooSession.ts); manager only passes the constructor into create…. |
| manager-wiring-only (local const arrow) | Inline the lambda in the factory argument object, or move deps assembly to functions/ or *Wiring.ts. |
*_manager.ts)**/*_manager.ts — no export function, function at module scope, class , or top-level const x = () =>.yarn lint:eslint — fa-two-level/manager-wiring-only covers exports and non-exported top-level const/let and classes.t: (key) => i18n.global.t(key)); that is not a manager body.sessionDeps live in sibling modules (*Session.ts, *Wiring.ts, *Bound.ts), not in *_manager.ts.types/)functions/** may only import type from app/types/** — put every shared export interface / export type there (naming: I_, T_), not in functions/, *_manager.ts, or Vue scripts.export type { … } from implementation files. Call sites import types from app/types/... directly.types/. See types-folder.mdc.src/stores/S_*.ts is the manager. Put pure logic in src/stores/functions/. Bridge scripts under stores/scripts/*Bridge* may import stores/functions/.
Same layout under src-electron/mainScripts/<area>/:
functions/ — pure helpers (import type from app/types/** only).<area>_manager.ts — wiring-only public entry; re-export or bind factories from functions/ and *Wiring.ts modules.*Wiring.ts (and *Surface.ts, *Runtime.ts, etc.) — impure implementation siblings (SQLite, electron, fs, cross-module orchestration).ipcManagement/ — ipcManagement_manager.ts exports registerAllFaIpc; individual registerFa*Ipc.ts files stay as IPC registrars and should import domain APIs from *_manager.ts when possible.Keep contentBridgeAPIs/ thin.
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.
Global keyboard shortcuts (faKeybinds): renderer matching, Pinia store, main-process persistence over IPC, and Keybind settings UI. Use when adding or changing app-wide shortcuts, capture validation, or bridge APIs for keybind storage.
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.
Produces production Electron builds for Fantasia Archive with electron- builder and Quasar. Use when changing build scripts, packaging, or publish flags, or when the user asks how to ship the desktop app.
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.
Designs SQLite usage in Fantasia Archive’s Electron main process: file locations under userData, native better-sqlite3 module constraints, and migrations. Use when editing electron-main database code, schema, or persistence paths.