メニュー
VelociDB code conventions - error handling, module boundaries, the experimental-modules policy, locking style, and documentation expectations. Use when writing or reviewing any VelociDB code, deciding where new code lives, or cleaning up warnings.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
How VelociDB's async API and parallel query execution work - the tokio spawn_blocking model in src/async_api.rs and the rayon thresholds in the executor. Use when modifying async_api.rs, adding async methods, tuning parallelism, or debugging blocked runtimes, stalled futures, or async test hangs.
VelociDB Change Data Capture - the in-memory change log in src/cdc.rs and its executor hooks. Use when modifying cdc.rs, adding CDC hooks to new write paths, changing ChangeEvent fields, or debugging missing/duplicate/out-of-order change events.
How to run and write VelociDB tests - test suite layout, commands, and patterns for unit, integration, crash-recovery, property-based, and async tests. Use when adding features, fixing bugs, writing new tests, or deciding which suites must pass before a change is done.
VelociDB vector search implementation - F32_BLOB(n)/VECTOR(n) columns, vector32 literals, distance functions, and exact parallel KNN. Use when modifying src/vector.rs, adding distance metrics, extending vector SQL syntax, or debugging dimension-mismatch, KNN-ordering, or vector-parsing issues.
Debugging VelociDB - REPL-based reproduction, tracing, inspecting db/WAL files, and a map of common failure modes to their causes. Use when investigating bugs, corruption errors, deadlocks/hangs, wrong query results, or data that disappears after reopen.
Extending VelociDB's regex-based SQL parser in src/parser.rs - statement dispatch, quote/paren-aware splitting helpers, value parsing, and known fragility. Use when adding SQL syntax, new statements or operators, changing WHERE/ORDER BY/VALUES parsing, or debugging "Invalid ... syntax" / mis-split errors.
| name | code-quality |
| description | VelociDB code conventions - error handling, module boundaries, the experimental-modules policy, locking style, and documentation expectations. Use when writing or reviewing any VelociDB code, deciding where new code lives, or cleaning up warnings. |
The SQL engine uses ONLY: storage, btree, parser, executor,
transaction, types, wal, vector, cdc, async_api.
mvcc, async_io, lockfree, simd, btree_optimized, crdt,
cloud_vfs, hybrid_storage, pmem are experimental: exported for
visibility, not wired in. Do not add dependencies from active-path modules
to experimental ones, and do not "fix" experimental-module warnings as part
of unrelated changes. If a feature graduates, say so explicitly in
src/lib.rs and the README.
crate::types::Result<T> (VelociError). Pick the
matching variant: ParseError, ConstraintViolation, NotFound,
Corruption (on-disk invariant broken), TransactionError, TypeMismatch,
StorageError, Busy.unwrap()/expect() on the active path except for logically infallible
cases with a justifying message (e.g. expect("group active after begin_group")).
Tests and the REPL binary may unwrap freely."Table '{}' not found".RwLock/Mutex everywhere; locks are NOT reentrant.// schema lock released).src/transaction.rs).//! docs stating purpose; /// docs with # Example on
public Database methods (they compile as doctests — keep them building).PAGE_SIZE,
BTREE_ORDER, PARALLEL_THRESHOLD, DEFAULT_CDC_CAPACITY).src/main.rs builds against the velocidb library crate — never re-add
mod declarations there.Do not introduce new warnings in active-path modules; cargo check --all-targets output for files you touched should be clean. Pre-existing
experimental-module warnings stay as-is.