We need a steady flow of demo videos — X/Twitter, Reddit, YouTube Shorts, blog posts, App Store-style screen recordings — and we'd like to scale that without scheduling Daniel to record every clip by hand. This doc maps the content-creation agent landscape, names the gap between "synthetic video hype" and "scripted…
Every quarter someone pitches an "AI does QA" tool. Most are web-first or mobile-first. MacParakeet is a menu-bar macOS app with a non-activating KeylessPanel overlay, global dictation hotkeys, and TCC-gated microphone/screen-recording flows. The general AI-QA frontier doesn't speak our shape yet. This doc tracks…
How coding agents (Claude Code, Codex, or any future harness) collaborate on this repo: who orchestrates, who implements, who reviews, and what each layer may touch. This is the map; the skills own the mechanics — never restate a skill's commands here or anywhere else (single owner per fact).
Issues for this repo live on the Open Software platform (os-platform), org june — NOT GitHub Issues. GitHub Issues exist on the repo but are a legacy/watchdog surface, not the triage queue.
Implements VZT Flow features observing this repo's boundaries — additive edits, the gotcha list from CLAUDE.md, pull-rebase discipline in a shared worktree, never touching the user's running daily-driver app without relaunching it. Use for routine feature/bugfix work in this repo.
Cuts a VZT Flow release — version bump consistency across all four version fields, tag, watch the release workflow, verify the produced asset list matches what install.sh/install.ps1 expect. Use when asked to cut, ship, or tag a VZT Flow release.
Runs the VZT Flow end-to-end verification ladder (build, tests, TTS-transcribe checks, clean-test latency, paste-test, daemon socket checks, overlay states) and reports real measured numbers — never estimates. Use before claiming a change works, before a release, or when asked to verify VZT Flow.
Reviews code for reuse, simplification, dead code, efficiency, and altitude — quality only, not correctness bugs. Pre-briefed on Blurt's deliberately-dormant code so a dead-code pass doesn't propose deleting it. Use for /simplify-style cleanup passes, one agent per angle.
Reviews SwiftUI/AppKit UI changes against macOS Human Interface Guidelines — modality, alerts vs inline validation, grouped-form structure, controls, and native idioms. Use after editing views in App/Blurt (wizard, settings, overlay).
Reviews Swift changes for Swift 6 strict-concurrency correctness (actor isolation, Sendable, @MainActor, data races) and Blurt's documented audio/pipeline invariants. Use after editing engine or app code that touches actors, async, the mic capture path, or the dictation pipeline.