Menu
Guidelines to prevent development false starts, environment mismatches, and incorrect commands in the deep-cuts monorepo
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Experimental protocol for Deep Cuts research, prototypes, model evaluations, threshold tuning, ablations, metric comparisons, and claims about accuracy or quality. Use before running or interpreting experiments so bots preserve train/validation/test boundaries, avoid leakage, compare against baselines, and report results honestly.
Guidelines for creating, updating, reorganizing, and reviewing Deep Cuts documentation in the project wiki, including page taxonomy, lifecycle status, protected pages, proposal handling, and link verification.
Pattern for multi-agent collaboration sessions in the deep-cuts fam — forge-first coordination over the botfam substrate (Gitea issues/PRs as the coordination plane, the unified `botfam wait` wake loop, bare-actor worktrees), with IRC opt-in for design sprints, plus session-log conventions
Draft, structure, and finalize a Deep Cuts blog-series post so it conforms to the post template, house voice, and cross-post link rules. Use when writing, drafting, assembling, or editing a "Deep Cuts" blog post (the rlupi.com series), preparing a post for publishing, or adding front matter to one. Covers the template, front matter schema, voice, agent crediting, and the link linter.
Checklist and guide for adding a new analysis pass to the trait-based modular pipeline
Safe pattern for adding SQLite schema migrations in the deep-cuts Rust/rusqlite_migration stack
| name | dev-guidelines |
| description | Guidelines to prevent development false starts, environment mismatches, and incorrect commands in the deep-cuts monorepo |
The dev build requires ACOUSTID_CLIENT_KEY to be set in the shell — it is baked in at compile time via option_env!(). The value lives in src-tauri/.cargo/config.toml, so you don't need to remember it:
export ACOUSTID_CLIENT_KEY=$(grep ACOUSTID_CLIENT_KEY src-tauri/.cargo/config.toml | grep -o '"[^"]*"' | tr -d '"')
npm run tauri dev
Or expand inline:
ACOUSTID_CLIENT_KEY=$(grep ACOUSTID_CLIENT_KEY src-tauri/.cargo/config.toml | grep -o '"[^"]*"' | tr -d '"') npm run tauri dev
Release builds (npm run tauri build) pick up secrets from .cargo/config.toml automatically and do not need the manual export.
npm run tauri dev # normal start (Vite HMR + Rust compilation)
npm run dev # Vite only (frontend preview, no Tauri/Rust)
Do not invoke vite or cargo tauri directly — always go through npm run.
npm run tauri dev sometimes serves a stale Rust binary — it may not recompile even when source files have changed. Symptoms: code fixes appear to have no effect, or analysis results are inconsistent with source changes.
Diagnose: check if the binary is older than the source:
stat -f "%Sm %N" src-tauri/target/debug/deep-cuts
stat -f "%Sm %N" src-tauri/src/embeddings.rs # or whichever file was changed
If the binary timestamp is earlier than the source file, it's stale.
Fix: force a rebuild before launching:
cargo build --manifest-path src-tauri/Cargo.toml
npm run tauri dev
This is especially important after editing files in src-tauri/src/ (e.g. embeddings.rs, analysis.rs) where a stale binary produces silently wrong results with no error message.
The frontend lives at the project root (not a frontend/ subdirectory). All npm commands run from the root:
npm run build
npm run check # svelte-check + TypeScript
npm run check:watch
Svelte 5 enforces strict {@const} placement — these must be immediate children of block tags ({#each}, {#if}, etc.), not DOM elements.
# Rust: persistence, scanner, DSP
cargo test --manifest-path src-tauri/Cargo.toml
Frontend tests use Vitest + @testing-library/svelte + jsdom. Run them with:
npm test # single run
npm run test:watch # watch mode
Test files live alongside source files as *.test.ts (e.g. src/lib/components/Foo.test.ts). The full stack — vitest, @testing-library/svelte, @testing-library/jest-dom, jsdom — is already installed.
On macOS, the SQLite database lives at:
~/Library/Application Support/com.rlupi.deep-cuts/deep_cuts.db
See skills/query-db/SKILL.md for query patterns and safety rules.
src-tauri/tauri.conf.json — app identifier is com.rlupi.deep-cuts, product name is Deep Cuts.
The app has no Python runtime dependency and no run_dev.py. Runtime development is driven through npm run tauri.
Python is used for tools, experiments, model export, and validation scripts under tools/. When a task needs Python, read skills/using-python/SKILL.md and use the project virtualenv (tools/.venv/bin/python) instead of system Python.