vishiri/fantasia-release-build
.cursor/skills/fantasia-release-build/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add vishiri/fantasia-archive fantasia-release-buildInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 11:15 AM43.3s1 file scanned
SKILL.md
- name:
- fantasia-release-build
- description:
- >-
Fantasia Archive — release build
Scripts (package.json)
yarn quasar:build:electron:quasar build -m electron --publish never— local/production artifact without publishing step from Quasar’s perspective (full log stream).yarn quasar:build:electron:summarized: same build viascripts/quasarBuildElectronSummarized.mjs— minimal terminal noise; full log intest-results/quasar-build-electron-last.logon failure. Used byyarn testbatch:ensure:*.yarn quasar:dev:electron: Development mode with hot reload.
Tooling
- Node.js: 22.22.0 or newer per
package.jsonengines.node(same floor as Quasar CLI v2 / CIsetup-node22.22). - electron-builder is a devDependency; Quasar/Electron mode drives the overall pipeline (see
quasar.config.tsand Quasar docs for Electron targets).
Checklist before a release candidate
- Quality gate in one terminal:
yarn testbatch:verify(testing-terminal-isolation.mdc). yarn quasar:build:electron(separate terminal); smoke-test the packaged app on target OS(es).- Run Playwright suites that matter after the same build (
yarn test:components,yarn test:e2e) — see fantasia-testing. - For Storybook smoke + visual snapshot compare in one chain with the steps above, use
yarn testbatch:ensure:nochangeinstead of piecing commands manually (or runyarn test:storybook:smokeandyarn test:storybook:visualseparately after the build steps as needed).
Versioning
- NEVER auto-bump any version during release/build workflows.
- Treat
package.jsonversionas the source of truth and keep changelog headings aligned to it. - Change any version values only when the user explicitly requests a manual version update.
TypeScript interfaces and types (types/)
- Put shared
interface/typedeclarations in repository-roottypes/(import withapp/types/...). Prefer one domain-oriented module per feature area with brief JSDoc on exports (seetypes/I_appMenusDataList.ts). Do not add colocated<filename>.types.tsundersrc/,src-electron/, or.storybook-workspace/. Ambient augmentations for third-party modules also live undertypes/and are loaded with a side-effect import from the owning boot file orsrc/stores/index.ts(seetypes/piniaModuleAugmentation.ts). - For JavaScript (
.js), TypeScript (.ts), Vue (.vue), and JSON (.json,.jsonc,.json5) files, enforce expanded multi-line object literals via ESLint (object-curly-newline+object-property-newline) and keep files auto-fixable witheslint --fix.
Related Skills
vishiri/git-conventional-commits
development
VerifiedTrustedCommunity
Splits working tree changes into logical Git commits with conventional messages (feat, fix, test, chore, refactor, style, docs). Proposes commits one at a time and waits for explicit user approval before each git commit. Use when the user asks to commit, split commits, stage by topic, or use conventional / semantic commit messages.
386SKILL.mdUpdated Apr 17, 2026
vishiri/fantasia-worldbuilding-domain
development
VerifiedTrustedCommunity
Aligns AI suggestions with Fantasia Archive as a worldbuilding database manager: projects, documents, and in-app concepts. Use when designing UX, data models, menus, or copy that should match the product purpose.
386SKILL.mdUpdated Apr 17, 2026
vishiri/fantasia-testing
development
VerifiedTrustedCommunity
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.
386SKILL.mdUpdated Apr 17, 2026
vishiri/fantasia-sqlite-main
development
VerifiedTrustedCommunity
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.
386SKILL.mdUpdated Apr 17, 2026