Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Shared orientation for the Dobby multi-repo system and person-workspace anatomy. Use when Codex is working in or across `~/GitHub/adi`, `~/GitHub/angie`, `~/GitHub/dobby-engine`, `~/GitHub/documents`, `~/GitHub/dobby-gateway`, `~/GitHub/dobby-ios`, `~/GitHub/agents`, or `~/GitHub/scripts` and needs to understand repo ownership, Adi/Angie workspace folders, memory/body-map routing, source-material placement, identity/workspace boundaries, the shared engine model, dashboard/gateway flow, hooks/control-plane responsibilities, machine scheduler boundaries, document-corpus boundaries, or where a Dobby-related change belongs.
Write or edit external-facing content in Adi's voice. Use when drafting or rewriting blog posts, essays, tweets, LinkedIn posts, reports, explainers, personal notes meant for publication, emails, website copy, or any other text that should sound like Adi rather than generic AI writing.
Independent reviewer for the frontier-lab-intelligence repo. Use when Adi asks to "get context and critique", review project state, audit progress against the submission endpoint, find blind spots, sanity-check a plan or architecture decision, or recommend what to do next. The role is critic and auditor, not implementer — load full project context cold, verify claims against live data, and judge everything by whether it pushes the case study toward earning the next interview by the deadline.
Check local Codex rate-limit reset credits and expiration times. Use when the user asks when Codex resets, banked resets, reset credits, free resets, weekly resets, or 5-hour resets expire, or asks to inspect available Codex reset credits from the local Codex login.
Multi-channel social publishing workflow plus blog-post publication prep and channel CLIs for Reddit, LinkedIn, X, YouTube, Instagram, and TikTok. Use when Codex needs to publish or distribute a blog post, video, launch, or visual explainer; prepare blog assets; decide between gallery, image, self, link, or native video format; publish the source post before distribution; post to Reddit; publish LinkedIn text/link/image/video posts; post X text/video posts; or prepare Instagram/TikTok posts through dry-run channel CLIs.
Best practices and domain knowledge for building videos programmatically with Remotion (videos in React/TypeScript, rendered to MP4). Use whenever writing or editing Remotion code — scaffolding a video project, animating with interpolate/spring over useCurrentFrame(), sequencing scenes and transitions, captions/subtitles, audio, GIFs/Lottie/3D, charts, visual effects, dynamic duration via calculateMetadata, or rendering. Consult before reaching for a Remotion API, since its components and props evolve (e.g. @remotion/media).
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.