deep-cuts

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

How to run Python scripts and install packages in the deep-cuts project

Rules for writing commit messages in the deep-cuts repository — subject line format, body content, scope naming, and what to omit

Pattern for adding a new Tauri IPC command (request/response or push event) in the deep-cuts monorepo

Conventions for writing Svelte 5 components in deep-cuts — runes, stores, props, event listeners, and file layout

Inspect, debug, and compare the Deep Cuts UI using an available browser tool. Use this skill whenever the user wants to inspect DOM structure, read computed CSS styles, take a screenshot of the app, or compare the UI before and after a Svelte/CSS change. Triggers on phrases like "show me the DOM", "what styles does X have", "screenshot the app", "compare before and after", "inspect the detail pane", "check the layout", or any request to verify a visual change. Also use proactively when finishing a CSS or Svelte refactor — capture a before snapshot, apply the change, then diff to confirm only intended styles changed.

Guidelines for the Sonic Glitch design system, theme variables, and multi-theme readability (dark, light, high-contrast)

Guidelines to prevent development false starts, environment mismatches, and incorrect commands in the deep-cuts monorepo

End-to-end checklist for building a signed macOS release — bump manifest min_app_version, verify sidecars, build, and inspect the .app

How to bundle an external binary and its dylib dependencies with the Tauri app, patch rpaths, sign everything, and resolve the path at runtime

Bump the app version in Cargo.toml after a release to start the next dev cycle

How to locate and query the deep-cuts pipeline metrics SQLite database

How to locate and query the deep-cuts production SQLite database