Interface with Blender (3D modeling, animation, rendering) through its Python API (bpy). Use whenever the user mentions Blender, .blend files, bpy, bmesh, geometry nodes, shader nodes, Cycles, EEVEE, Workbench, scene/object/material manipulation, mesh editing, armatures/rigging, keyframe animation, F-curves, drivers, NLA, importing/exporting 3D formats (GLTF/glb, FBX, OBJ, USD, STL, Alembic, Collada), batch rendering, headless render farms, CLI invocation (`blender --background --python`), authoring add-ons, custom operators/panels/menus, modal operators, PropertyGroups, Geometry Nodes trees, baking, simulation (cloth/fluid/rigid body), grease pencil, compositor nodes, or hooking Blender up to MCP / live AI control. Trigger even on vague asks like 'script Blender', 'automate Blender', 'render this from a script', or any 3D-graphics task where Blender is implied. Also trigger when the user asks to install bpy as a pip module or run Blender headless on a server.
Diagnose and fix Unraid (Lime Technology NAS OS) issues — array start/stop hangs, parity errors, disabled or emulated disks (red ball/red X), New Config and trust-parity, Docker macvlan/ipvlan call traces and custom networks, VM problems (KVM, libvirt, QEMU), GPU/USB/PCIe passthrough (IOMMU groups, VFIO, ACS override), BTRFS scrub/balance and ZFS pool degraded/corruption, mover and share allocation policies (high-water/most-free/fill-up), user shares vs disk shares, /mnt/user vs /mnt/cache vs /mnt/disk*, SMB/NFS permissions and newperms, Community Applications (CA) plugin and .plg install, /boot/config persistence, USB boot and GUID/license issues, syslog and diagnostics bundle interpretation, Fix Common Problems plugin, and version-aware release-notes lookup against docs.unraid.net. Use this whenever the user mentions Unraid, unRAID, Lime Tech NAS, or describes any symptom on an Unraid box — array won't stop, won't start, disk dropped, parity sync errors, container has no network, VM black screen, cache pool
Diagnose and fix Linux desktop issues — graphics drivers (Nvidia, AMD/Mesa, Intel), display servers (Wayland, X11, XWayland), audio (PipeWire, PulseAudio, Bluetooth), boot failures, systemd unit errors, suspend/hibernate, NetworkManager/Wi-Fi, kernel module problems, Flatpak/Snap sandbox breakage, and general desktop environment failures. Use this whenever the user reports ANY Linux desktop symptom — black screen, login loop, no audio, screen tearing, frozen cursor, GPU hangs, crashes after kernel update, broken external monitor, suspend doesn't work, app won't launch under Wayland, screen recording missing, Bluetooth pairing fails, or anything else where their Linux machine isn't behaving. Trigger even when the user just says 'my Linux is broken' or describes a vague desktop problem without naming the subsystem. Also use for proactive triage of dmesg/journalctl logs the user pastes, even if no explicit fix is requested.
Find every flaw in the overall approach and strategy of the code. Challenges whether the right problem is being solved, whether the algorithm is appropriate, whether assumptions are validated, and whether better alternatives exist. Produces severity-ranked issues with file:line references. Use when you want a dedicated approach review of code changes, files, or directories.
Find every flaw in the structural soundness, component design, and system organization of the code. Challenges whether boundaries are clean, coupling is minimized, dependencies flow correctly, and the module structure scales. Produces severity-ranked issues with file:line references. Use when you want a dedicated architecture review of code changes, files, or directories.
Find every violation of language and framework conventions, established patterns, and anti-patterns in the code. Challenges whether idioms are followed, APIs are designed correctly, and deprecated patterns are avoided. Produces severity-ranked issues with file:line references. Use when you want a dedicated best-practices review of code changes, files, or directories.
Find every flaw in failure modes, edge cases, and graceful degradation. Challenges whether all failure paths are handled, whether the system degrades gracefully or crashes spectacularly, and whether error propagation is correct. Produces severity-ranked issues with file:line references. Use when you want a dedicated error handling review of code changes, files, or directories.
Find every flaw in the long-term code health, change resilience, and future-developer experience. Challenges whether unfamiliar developers can safely understand, modify, and extend the code. Evaluates modular boundaries, debugging affordances, documentation sufficiency, and upgrade paths. Produces severity-ranked issues with file:line references. Use when you want a dedicated maintainability review of code changes, files, or directories.