Agent-Skills

Use when designing, reviewing, or updating Codex app automations, cron jobs, scheduled tasks, recurring runs, or heartbeat follow-ups.

Use when a project or Codex runtime needs environment TOML created, triaged, or updated with safe setup, actions, exec-server providers, and validation evidence.

Scaffold hook packs, validate hooks.json schema, verify hook script permissions, migrate hook configuration, and troubleshoot Codex hook execution errors. Use when creating, auditing, upgrading, or validating Codex hook packs, hooks.json files, hook scripts, SubagentStart/SubagentStop lifecycle hooks, PreToolUse/PostToolUse/PreCompact hooks, Stop claim checks, or repo-local/user-level .codex hook installs.

Review local dirty changes, committed branches, and PR diffs with Codex CLI; report findings, validation, blockers, and merge-readiness evidence. Use when the user asks for Codex review, autoreview, independent model review, or pre-ship validation.

Use when users need to install, bootstrap, upgrade, audit, diagnose, or explain @brainwav/coding-harness in a repository, including harness init/upgrade, CI migration, governance gates, command discovery, and Codex environment action sync.

Analyze current external library or API docs with Context7 when dependency behavior, version-sensitive references, or ctx7 CLI setup/install guidance is needed.

Create, migrate, or validate Better Auth implementation work. Use when the user wants Better Auth added or changed in code, including OAuth, passkeys, 2FA, magic links, or org flows.

Analyze, compare, and recommend a Codex build primitive. Use when the user is packaging or automating a workflow and the right primitive is unclear.

Analyze, deepen, and validate an existing doc or topic through a structured interview. Use when refining PRDs, Linear tickets, notes, or draft specs before planning or execution.

Govern and validate design-system changes. Use when tokens, typography, spacing, iconography, themes, or style aliases need repository-grounded evidence.

Plan AI-native hackathon scope, demo pitch, and judge Q&A. Use when the user needs 1-hour pitch prep, 24-hour build scoping, AI Native DevCon-style track choice, idea pressure tests, or a spec-led hack plan. Do not use for code generation, implementation support, or non-hackathon DevRel content.

Generate, validate, and refresh @brainwav/diagram architecture artifacts when repo diagrams, context packs, PR impact, or CI drift evidence is needed.

Create and review idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView. Use when building or debugging Elixir services that need reliable concurrency and fault tolerance.

Use when evaluating LLM or RAG outputs: audit eval coverage, analyze failed traces, write binary judge prompts, validate judges against labels, generate targeted synthetic cases, evaluate retrieval quality, or plan review tooling. Do not use for ordinary software test implementation.

Audit, fix, and validate accessibility issues. Use when adding or reviewing controls, forms, dialogs, keyboard behavior, focus management, ARIA labels, color contrast, or WCAG compliance.

Audit, fix, and validate HTML metadata. Use when shipping pages that need titles, descriptions, canonical URLs, Open Graph tags, Twitter cards, favicons, JSON-LD, or robots directives.

Diagnose, fix, and validate mise runtime failures. Use when commands fail from mise config, missing runtimes, stale pins, trust prompts, or shell activation drift.

Analyze ambiguous frontend design requests and route the right UI owner. Use this skill when broad design intent needs classification before implementation.

Design or implement production-ready frontend screens and components. Use this skill when UI build, redesign, accessibility, layout, or state coverage is needed.

Best practices for working with Go codebases. Use when writing, debugging, or exploring Go code, including reading dependency sources and documentation.