Project-local enforcement of vibemix frontend design standards. Loaded automatically by agents that touch frontend code or UI design — Forged Obsidian Chrome (tozpembe) discipline, 20/80 rule, One-Rose, gold quarantine, no AI slop.
Reviews any change to what the vibemix co-host SAYS or WHEN it speaks against the 5 cardinal anti-slop invariants. Trigger BEFORE shipping edits to src/vibemix/state/coach.py, src/vibemix/agent/dj_cohost.py, anything under src/vibemix/prompts/ (matrix.py, filter.py, negative_dict.py), src/vibemix/state/event_detector.py, state/refresh.py, state/evidence_registry.py, coach/citation_linter.py, or any reaction/persona/lens/learn-tutor wiring. Also trigger when a PR/plan touches the reaction loop, the citation grammar, EVIDENCE_SOURCES, the slop filter, or the ws bus, OR when Kaan asks "is this grounded / will this slop / does this break an invariant / can we ship this reaction change". Reactions that are scripted, late, hallucinated, or generic are the release blocker — this is the gate.
Launch vibemix in dev-source mode and DRIVE the running app to prove a change works LIVE — the perception loop (fire a control, read the logs it produced, confirm the co-host's reaction is grounded, not slop). Trigger when verifying any backend/runtime change actually works in the app (not just green tests), when Kaan asks "does this actually work / show me it working / run it / verify live", when a control or panel looks dead/unresponsive (button does nothing, panel blank, no reaction), when confirming a co-host reaction is grounded vs hallucinated, or when you edited anything under src/vibemix/ (state, agent, runtime/ws_bus, prompts, coach) and need to observe it on the real ws bus. Use BEFORE claiming a runtime fix is done — green unit tests do NOT prove the live app works (frozen sidecar + Tauri runtime hide real failures).
Verifies BOTH ends of a vibemix IPC message type are wired — sender on one side, handler/consumer on the other — so a one-ended "dead" type never ships as a silent dead feature. Trigger BEFORE shipping any edit to tauri/ui/src/ipc/messages.schema.json, when adding/removing/renaming an ipc.* message type, when wiring a new control end-to-end (button → emitIpc → register_handler → response), or when hunting a control/panel that looks dead or unresponsive ("button does nothing", "panel stays blank", "no reaction on the wire"). Also trigger when a PR or plan touches the ws_bus, register_handler, emitIpc/sendIpcRequest/subscribeIpc, or the codegen:ipc pipeline.
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.