carterbs

Generate and iterate on weekly meal plans using the BradOS CLI. Use when asked to "plan meals", "make a meal plan", "what should I eat this week", "generate a meal plan", or any meal planning request. Handles the full workflow: generate draft, present it, iterate on feedback via critique, finalize, and produce a shopping list.

Build a new health metric history view page following the established HRV/RHR/Sleep pattern. Use when adding a new metric history screen (e.g., weight, VO2 max, body fat, steps). Handles the ViewModel, View, navigation wiring, and XcodeGen regeneration.

Aurora Glass design system for all Brad OS UI work. Use this skill whenever building, modifying, or reviewing SwiftUI views in the iOS app. Applies to: creating new screens, editing existing views, adding components, reviewing UI consistency, or any task that touches Theme.swift or visual elements. This is the single source of truth for colors, typography, spacing, glass surfaces, aurora glows, components, and interaction patterns.

Get UI/UX design feedback from OpenAI by sending app screenshots. Use when asked to "review the UI", "improve the design", "make it look better", "get design feedback", or when evaluating visual quality of app screens.

Create git commits with no Claude attribution. NEVER adds co-author information—commits appear as if user wrote them. Use when user asks to "commit", "make a commit", save work to git, says "wrap up" or "finish" after completing work, asks "what's next?" or "are we done?" after coding, or mentions staging changes or commit messages.

ALWAYS invoke this skill (do NOT use the default Explore agent) when user asks to "research", "investigate", "explore", or "understand" the codebase. Use for understanding architecture or system design, documenting patterns or conventions, investigating how features work end-to-end, answering "how does X work?" or "where is Y implemented?" questions, preparing context before implementing changes, or exploring unfamiliar code.

Create detailed implementation plans with thorough research and iteration. Use when starting significant features spanning multiple files, planning refactors affecting architecture, working on multi-phase projects with milestones, establishing success criteria before coding, breaking down complex work, or documenting approach for non-trivial technical decisions.

Interact with Gardener backlog SQLite storage and create new backlog tasks.

Debug Gardener runtime failures by joining git worktree/branch/commit context with OTEL JSONL logs. Use for: reading and filtering malformed or high-volume `otel-logs.jsonl`, isolating failed runs by `run.id`/worker, tracing failure events, and mapping runtime context from log entries back to git run/worktree state.

Generate a session recording file and reproduction test from a Gardener TUI error. Use when a worker fails with a visible error (e.g. "process error: missing turn.completed or turn.failed event") and you want to reproduce it deterministically via the replay system.