Agent skill

Veloxdb Scalable Performance

by veloxbase in veloxbase/veloxdb

Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend.

MITAuto-check passedDatabases

Install Veloxdb Scalable Performance

skills CLI
$ npx skills add veloxbase/veloxdb --skill veloxdb-scalable-performance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install veloxbase/veloxdb veloxdb-scalable-performance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/veloxbase/veloxdb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/veloxdb-scalable-performance .claude/skills/veloxdb-scalable-performance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
veloxdb-scalable-performance
GitHub stars
646
Token cost
~1.7k tokens
SKILL.md length
680 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend.

  • The user asks about performance
  • SKILL.md covers Package manager and file…, Rust / Tauri (src-tauri/), Frontend (src/) and PostgreSQL and product behavior, plus 2 more sections
  • Calls pnpm
  • Large result sets

What it does

Veloxdb Scalable Performance is an agent skill from veloxbase/veloxdb. Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend. Covers pnpm-only tooling, src/ file layout (features, data, components/ui, lib), connection pooling, bounded query results, IPC payload size, TanStack Query defaults, virtualization, memo patterns, minimal useEffect usage, and shadcn-style UI consistency. Use when the user asks about performance, memory, latency, large result sets, slow queries, pooling, caching, N+1 patterns, scaling the UI…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering Design systems, Database administration and Query optimization. It works with TanStack, Tauri, Rust and PostgreSQL. The repository describes itself as: Database management, built for developers. The licence is MIT.

When your agent uses it

  • The user asks about performance
  • Large result sets
  • Package manager
  • Component styling aligned with the design system

Example prompts

  • “Use the veloxdb-scalable-performance skill to guide scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React +…”
  • “/veloxdb-scalable-performance”

What it can do on your machine

Read from SKILL.md and the folder at commit 2ca04f2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • cursor.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Veloxdb Scalable Performance loads about 1.7k tokens when it runs. Until then it costs about 161 tokens; SKILL.md has 680 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~161
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from veloxbase/veloxdb at commit 2ca04f2, republished under its MIT licence (© veloxbase). 680 words, ~1,678 tokens.

Download SKILL.mdSave it as .claude/skills/veloxdb-scalable-performance/SKILL.md (or your agent's skills folder).
name
veloxdb-scalable-performance
description
Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend. Covers pnpm-only tooling, src/ file layout (features, data, components/ui, lib), connection pooling, bounded query results, IPC payload size, TanStack Query defaults, virtualization, memo patterns, minimal useEffect usage, and shadcn-style UI consistency. Use when the user asks about performance, memory, latency, large result sets, slow queries, pooling, caching, N+1 patterns, scaling the UI, effects/hooks, repo structure, package manager, or component styling aligned with the design system.

VeloxDB scalable performance

VeloxDB is a desktop Tauri 2 app: the UI invokes async Tauri commands in Rust, which talk to PostgreSQL via deadpool_postgres. The frontend uses TanStack Query, TanStack Table, and TanStack Virtual where large grids matter. Prefer stack-specific guidance over generic web scaling advice.

Package manager and file structure

  • pnpm only: Use pnpm for all JavaScript tooling in this repo—pnpm install, pnpm dev, pnpm build, pnpm lint, pnpm exec, pnpm add / pnpm remove, and pnpm tauri / pnpm tauri:build. Do not suggest or run npm or yarn for installs or scripts unless the user is explicitly migrating lockfiles.
  • Layout (keep new code in the right place):
    • src/features/<area>/ — Product features: components/ for screens/widgets, colocated queries.ts (or *.ts) for TanStack Query hooks and feature types that are not global. Examples: features/connections, features/queries, features/schema, features/tables, features/commands.
    • src/data/ — App-wide data layer: types.ts, query-client.ts, query-keys.ts, repositories/ (Tauri invoke boundaries and repository interfaces). Shared fetch/cache contracts live here, not inside random feature folders.
    • src/components/ui/ — Reusable, design-system-style primitives (shadcn-style). src/components/ (outside ui/) for shared non-primitive pieces such as ErrorBoundary.tsx.
    • src/lib/ — Small shared helpers (e.g. utils.ts, tauri.ts) with no feature-specific UI.
    • src/App.tsx, src/main.tsx — Application shell and bootstrap; avoid bloating them—compose from features instead.
    • src-tauri/ — Rust backend, Tauri config, and commands; pair frontend changes with the right module in src-tauri/src/ when touching IPC or DB.

Rust / Tauri (src-tauri/)

  • Use async Tauri commands and the tokio runtime; do not block on synchronous I/O in command handlers.
  • Reuse connection pooling through AppState (RwLock<HashMap<String, Pool>>), build_pool, and get_or_create_pool in src-tauri/src/db.rs. New features that open ad hoc clients should justify why they bypass the pool.
  • MAX_QUERY_ROWS in db.rs caps rows materialized for the UI path. run_query sets truncated when more rows exist than returned. Any streaming, pagination, or export design must stay consistent with this contract (or deliberately replace it end-to-end).
  • IPC payloads: Tauri serializes command results to the webview. Avoid returning unbounded Vecs; for large exports or dumps, prefer chunking, writing to disk from Rust, or explicit user-scoped limits.
  • Pool lifecycle: Pools are stored per connection_id. If adding many connections or long-lived sessions, consider eviction or caps so the map does not grow without bound.
Show full SKILL.md (326 more words)Show less

Frontend (src/)

  • TanStack Query: Default client behavior lives in src/data/query-client.ts (staleTime, gcTime, refetchOnWindowFocus: false, etc.). Preserve desktop-oriented defaults; override in individual useQuery options only when the feature needs different freshness or retries.
  • Large grids: Follow src/features/queries/components/ResultsGrid.tsx—@tanstack/react-virtual for rows, stable keys, and memoized column defs. New heavy tables should virtualize rather than rendering all DOM nodes.
  • Trees / sidebars: src/features/connections/components/ConnectionsSidebarTree.tsx uses useMemo / useCallback for filtered data and handlers. Extend in the same style; debounce or narrow dependencies for search/filter so the whole tree is not recomputed on every keystroke without reason.
  • useEffect: Avoid it unless necessary. Prefer derived state during render, event handlers, TanStack Query (data / status for render-time branching; useMutation callbacks such as onSuccess when an imperative follow-up is required), and refs for values that should not trigger re-renders. Reserve useEffect for real external synchronization: subscriptions, DOM/layout measurement, imperative browser or third-party APIs, or Tauri listeners that must mount/unmount with the component.
  • shadcn-style UI: Compose from existing primitives in src/components/ui/ (Radix-based patterns, class-variance-authority, tailwind-merge, Tailwind v4 tokens). Match established spacing, typography, focus rings, and disabled states; extend with cva variants instead of one-off inline styles. New shared widgets belong under src/components/ui/ following the same patterns as button.tsx, dialog.tsx, etc.
  • React Compiler: The project uses babel-plugin-react-compiler. Avoid piling on useMemo/memo unless profiling or semantics require it.

PostgreSQL and product behavior

  • Prefer bounded reads (LIMIT, and keyset/cursor pagination for future features). Make truncation obvious in the UI when truncated is true.
  • When discussing user databases, mention indexes and EXPLAIN-style reasoning where it helps; keep DBA depth proportional to the task.

Change checklist

  • Identify the hot path: IPC serialization, PostgreSQL execution, or React render.
  • Reason about scale: row counts, number of connections/pools, tree depth, query frequency.
  • Reuse existing patterns: repositories and invoke usage under src/data/.
  • Keep edits scoped to the user’s request; do not refactor unrelated code for performance without cause.

Optional: slash-only invocation

To require explicit invocation, add disable-model-invocation: true to the YAML frontmatter above (see Cursor Agent Skills).

© veloxbase, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/veloxdb-scalable-performance of veloxbase/veloxdb.

Open the folder on GitHubat commit 2ca04f2

Compare with similar skills

Veloxdb Scalable Performance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Veloxdb Scalable Performance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Veloxdb Scalable Performance this skillveloxbase/veloxdb646—~1.7kAutomated safety check: PassMIT
Weft FrontendWeaveMindAI/weft2k—~8kAutomated safety check: NotesCustom licence
Cdphuoshen80/ReinaManager694—~178Automated safety check: PassAGPL-3.0
Frontend BuilderWeaveMindAI/weft2k—~2.6kAutomated safety check: PassCustom licence
PlanetScale Postgres Playbookplanetscale/database-skills7063 repos~1.8kAutomated safety check: PassMIT
PostgreSQL Documentation Reference2025Emma/vibe-coding-cn23k1 repos~19kAutomated safety check: PassMIT

Similar skills

  • Weft Frontend

    WeaveMindAI/weft

    Read when the user wants a page, app or site for the program, and before dispatching the frontend-builder: the verified scaffold commands, the default stack (pnpm, SvelteKit, PostgreSQL, BetterAuth…

    2k GitHub stars~8k tokensUpdated today
    Frontend & DesignAuto-check: notes
  • Cdp

    huoshen80/ReinaManager

    通过 CDP 连接 ReinaManager WebView2,复现、诊断并验证真实应用的前端问题。仅在用户显式调用 /cdp 或 $cdp 进行前端调试时使用。

    694 GitHub stars~178 tokensUpdated today
    DatabasesAuto-check passed
  • Frontend Builder

    WeaveMindAI/weft

    Builds the project's frontend under front/ end to end, unsupervised.

    2k GitHub stars~2.6k tokensUpdated today
    Frontend & DesignAuto-check passed
  • PlanetScale Postgres Playbook

    planetscale/database-skills

    Official

    Indexes reference files on Postgres schema design, indexing, partitioning, query patterns, MVCC and VACUUM, and PlanetScale-specific operations.

    706 GitHub starsUsed in 3 repos~1.8k tokens
    DatabasesAuto-check passed
  • PostgreSQL Documentation Reference

    2025Emma/vibe-coding-cn

    PostgreSQL database documentation - SQL queries, database design, administration, performance tuning, and advanced features. Use when working with PostgreSQL…

    23k GitHub starsUsed in 1 repo~19k tokens
    DatabasesAuto-check passed
  • DB Ops Sop

    OpenDCAI/DataMind

    Database operations runbook — backup, recovery, performance tuning, troubleshooting.

    449 GitHub stars~388 tokensUpdated 19 days ago
    DatabasesAuto-check passed

More from veloxbase/veloxdb

  • Reactflow Workflow

    veloxbase/veloxdb

    Build and harden React Flow diagram surfaces in VeloxDB using @xyflow/react patterns (nodes, edges, viewport, controls, interactions, performance).

    646 GitHub stars~897 tokensUpdated 9 days ago
    Auto-check passed
  • Rust Heavy Performance

    veloxbase/veloxdb

    Enforces a Rust-first approach for heavy work in VeloxDB so expensive compute stays in Tauri/Rust instead of JavaScript.

    646 GitHub stars~733 tokensUpdated 9 days ago
    Auto-check passed

Questions about Veloxdb Scalable Performance

What does Veloxdb Scalable Performance do?

Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend. Veloxdb Scalable Performance is an agent skill from veloxbase/veloxdb. Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend.

When should I use Veloxdb Scalable Performance?

Veloxdb Scalable Performance fits situations like: the user asks about performance; large result sets; package manager; component styling aligned with the design system.

How do I install Veloxdb Scalable Performance in Claude Code?

Run `npx skills add veloxbase/veloxdb --skill veloxdb-scalable-performance -a claude-code`. Or copy the skill folder (.cursor/skills/veloxdb-scalable-performance in veloxbase/veloxdb) into .claude/skills/veloxdb-scalable-performance in your project. Claude Code loads it when a task matches its description.

How do I install Veloxdb Scalable Performance in Codex?

Run `npx skills add veloxbase/veloxdb --skill veloxdb-scalable-performance -a codex`. Or copy the skill folder (.cursor/skills/veloxdb-scalable-performance in veloxbase/veloxdb) into .agents/skills/veloxdb-scalable-performance in your project. Codex loads it when a task matches its description.

Can I use Veloxdb Scalable Performance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add veloxbase/veloxdb --skill veloxdb-scalable-performance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/veloxdb-scalable-performance, .gemini/skills/veloxdb-scalable-performance, .github/skills/veloxdb-scalable-performance and .opencode/skills/veloxdb-scalable-performance in your project.

What does Veloxdb Scalable Performance need to run?

Going by SKILL.md and its folder, Veloxdb Scalable Performance needs the command-line tools its instructions call (pnpm).

Does Veloxdb Scalable Performance access the network?

SKILL.md names 1 domain. As links in the text: cursor.com. This is read from the text; nothing was executed.

Is Veloxdb Scalable Performance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Veloxdb Scalable Performance use?

Veloxdb Scalable Performance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Veloxdb Scalable Performance use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Veloxdb Scalable Performance?

Skills that share tags, products or a category with Veloxdb Scalable Performance: Weft Frontend (WeaveMindAI/weft, 2k stars), Cdp (huoshen80/ReinaManager, 694 stars), Frontend Builder (WeaveMindAI/weft, 2k stars) and PlanetScale Postgres Playbook (planetscale/database-skills, 706 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Veloxdb Scalable Performance?

veloxbase (a GitHub organization) maintains it in veloxbase/veloxdb, which has 646 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 30, 2026.

Source: veloxbase/veloxdb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.