Plover
Official@tryplover · Canada
Plover provides debugging and troubleshooting skills for its Electron desktop app stack, covering pnpm workspaces, Vitest, Gemini integration, OAuth, and native modules.
Agent Skills by Plover
Showing 9 vetted skills indexed across 1 GitHub repositories.
tryploverplover-env-and-backend
Diagnose env loading and backend URL wiring failures in the Plover Electron app.
tryploverplover-pnpm-workspace
Diagnose and fix pnpm workspace filter, script, and store errors.
tryploverplover-testing
Diagnose and fix Vitest, better-sqlite3, and Electron test failures in the Plover repo.
tryploverplover-gemini
Diagnose and fix Gemini SDK functionCalls accessor errors and 429 quota failures.
tryploverplover-electron-windows-overlay
Diagnose and fix Electron overlay window rendering and positioning bugs on Windows.
tryploverplover-auth
Diagnose and fix Supabase authentication and Google OAuth errors in the Plover Electron app.
tryploverplover-git-safety
Diagnose and recover from concurrent git, worktree, and stacked-PR footguns in the Plover repo.
tryploverplover-store-schema
Diagnose vestigial columns and unreliable timestamp signals in the Plover SQLite store schema.
tryploverplover-electron-vite-build
Diagnose and fix electron-vite build and runtime errors in pnpm workspace Electron apps.
Frequently Asked Questions About Plover
FAQPage SchemaWhat tasks can I solve using Plover's skills?▼
Plover's skills diagnose concrete failures in its Electron app repo: pnpm workspace filter and store errors, Vitest mocking and hoisting bugs, better-sqlite3 native module ABI mismatches, electron-vite build breakage, Gemini API type errors and 429 quota fallbacks, Google OAuth token exchange failures, and git worktree/branch safety issues.
Who are Plover's skills designed for?▼
They target developers and coding subagents working inside the Plover repository — engineers touching app/src/main, electron.vite.config.ts, the plover-server auth middleware, or the tasks table schema in app/src/main/store/db.ts who need repo-specific fixes rather than generic documentation.
What runtime environment do Plover's skills assume?▼
The skills assume the Plover monorepo: a pnpm workspace with an Electron app built via electron-vite, Vitest for testing, better-sqlite3 for local storage, the @google/generative-ai client for Gemini, and a plover-server backend configured through app/.env variables like GOOGLE_CLIENT_ID and PLOVER_BACKEND_URL.
What prerequisites or dependencies do Plover's skills require?▼
You need the Plover repo checked out with pnpm installed, Node.js and Electron versions aligned for native module ABI compatibility, valid Google OAuth credentials (GOOGLE_CLIENT_ID) in app/.env, and on Windows awareness that a running pnpm dev session locks better_sqlite3.node during rebuilds.
Do Plover's skills cover database schema pitfalls?▼
Yes. The plover-store-schema skill covers the tasks table in app/src/main/store/db.ts, warning against the vestigial calendar_event_id column and explaining why created_at/updated_at are unreliable for task-age signals — Planner bulk-creates subtasks with shared timestamps and incrementProgress() bumps updated_at on every call.