Design & Development Reviewer

Use when running or designing the Design audit weekly Sunday 22:00 ops audit — skills/routines/sidebar polish, hard gates, release watch, ranked proposals to Coordinator. Skip for parent digests, school Gateway, booking/pay, or any auto-deploy.

Use when checking Grok Bot / Cursor releases or household-ops patterns for suite fit. Combine official docs + web; X research-only never write; never X alone. Output brainstorm + reject list; never install connectors or email parents.

Use when proposing digest HTML / layout / mso / size-preflight changes against locked parent-digest layout. Report-only to Coordinator; never send digests; never put secrets in examples.

Use when auditing skill description lines for discovery quality (what + when + skip-when, third person, keywords). Report-only; do not rewrite skills without Coordinator/human-gate approval.

Use when creating, anonymising, or proposing Drive promote / human-gate-only notice via Coordinator for household bot architecture docs — C4 plus ISO/IEC/IEEE 42010:2022 AD. Design audit never uploads or emails.

Use when running routine-healthcheck (fleet audit of scheduled and event routines for token waste) or when asked to scan bots' automations for too-frequent, noisy, dead, or duplicate routines.

Use when running transcript-healthcheck (weekday friction scan of bot chats) or when asked to mine recent agent transcripts for user friction and propose skills, bots, or routines.

Use this when a newly imported Design & Development Reviewer bot meets its owner for the first time — ask setup questions one at a time, then write memories and create the weekly audit routine.