specbl1z

Systematic pre-merge verification workflow for Rust monorepo branches. Check compilation, tests, clippy, grep leftovers, then fix → commit → push → PR. Use when user says "check work done in this branch" or before merging any PR.

Dependency lock and Cargo.lock conflict policy for Rust workspaces. Covers when to update, when to regenerate, manual conflict handling, and merge/sync guidelines to prevent recurring Cargo.lock merge conflicts.

Audit and fix documentation (README, ARCHITECTURE, CHANGELOG) against current codebase while waiting for CI/bot reviews on a PR. Fix factual drift, dead references, and add changelog entries — then commit docs to the same branch.

Daytona sandbox knowledge for answering user questions about remote development environments. Use when the user asks about Daytona, sandboxes, remote execution, cross-platform builds, or needs to run code on cloud infrastructure instead of locally. Provides API details, pricing, troubleshooting, and CLI commands.

Modal.com knowledge for answering user questions about serverless GPU compute, cost comparison with Daytona, and Python-based sandbox workflows. Use when the user asks about GPU access, ML training, Modal pricing, serverless sandboxes, or wants to compare cloud compute options for their Rust/Python projects.

Mandatory project quality workflow for the specgen Rust monorepo. Enforces zero-warning policy, formatting standards, and test compliance. Trigger before any commit, pull request, or completion of a coding task. Also trigger when the user says "check quality", "run QA", or "is it ready?".

Comprehensive toolkit for detecting and eliminating "AI slop" - generic, low-quality AI-generated patterns in natural language, code, and design. Use when reviewing or improving content quality, preventing generic AI patterns, cleaning up existing content, or enforcing quality standards in writing, code, or design work. Trigger on first run in any new codebase, after AI-assisted coding sessions, or when user says "clean up", "review quality", "check slop", or "anti-slop".

How to implement a robust MCP server that dispatches domain-specific tool calls to a compiled CLI (e.g., Rust/Go). Use this when building MCP integrations for existing CLI tools, or when platform constraints (like Termux/Android) prevent direct usage of native Node.js database drivers. This skill teaches the 'Generic Dispatcher' pattern to keep the bridge layer thin and performant.