bnema

Use when managing per-project backlog folders, feature queues, async agent work items, lifecycle status updates, PR/done/blocked transitions, or status reviews inside an Obsidian vault.

Use when prototyping, authoring agent skills, or asking the agent to zoom out and map unfamiliar code before acting.

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

Use when reviewing architecture boundaries, hexagonal architecture, clean architecture layers, dependency direction, trust boundaries, uploads, parsers, redirects, or web security risks.

Use when configuring or running hexcheck in a Go repo for hexagonal architecture boundaries, adapter business-logic warnings, and mock discipline.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Use when requesting or receiving code review, dispatching review subagents, running CodeRabbit, deep reviews, simplification/cleanup passes, local branch review, ready-for-PR/finalize intent, finalizer workflow, or preparing work for merge.

Use when running CodeRabbit CLI code reviews, reviewing uncommitted or committed changes, comparing branches, or authenticating with CodeRabbit. Triggers on "code review", "cr review", "coderabbit", "review my changes", "review this branch".

Use when auditing, reviewing, or modifying web applications where untrusted data crosses trust boundaries — including request handlers, parsers, renderers, document importers, file uploads, redirects, API endpoints, webhooks, and multi-step feature chains. Also use when reviewing framework defaults, content-type handling, or feature composition that could chain into vulnerabilities.

Use when deploying containers, managing routes, configuring services, or operating any application with the Gordon CLI. Use when the user mentions gordon, push-to-deploy, or self-hosted container deployment.

Use when building or updating Astro sites, components, content-driven pages, islands, content collections, view transitions, or Astro server features such as SSR, actions, API routes, middleware, and adapters.

Use when running CodeRabbit CLI code reviews, reviewing uncommitted or committed changes, comparing branches, or authenticating with CodeRabbit. Triggers on "code review", "cr review", "coderabbit", "review my changes", "review this branch".

Use when asked for a deep code review, thorough review, security audit, full review of changes, or pre-merge review. Triggers on "deep review", "thorough review", "audit my code", "review for security", "check for bugs", "review before merge".

Use when writing, reviewing, or debugging Drizzle ORM code — schema definitions, queries, mutations, relations, migrations, transactions, or any project using drizzle-orm with PostgreSQL, MySQL, SQLite, Turso, Neon, D1, or other supported databases

Use when building distinctive, production-grade frontend interfaces — components, pages, or full applications. Guides bold aesthetic direction and real working code with exceptional design quality.

Debug Go programs and tests with Delve from the terminal. Use when stepping through failing tests, setting breakpoints, inspecting variables, tracing goroutines or deadlocks, attaching to a running Go process, examining a core dump, or diagnosing race conditions and state changes in any Go repository.

Use when the user wants to learn, understand code, study a concept, build while learning, dissect a function, get an explanation adapted to their level, or ask for a more pedagogical walkthrough.

Use when the learner wants to learn a language, framework, tool, or concept from a blank repo, scratch folder, or loosely defined goal; also use for project-based learning where the learner wants to build something in order to learn.

Use when the user wants to understand existing code, a function, a loop, a parser, a request handler, data flow, control flow, or any code path that benefits from step-by-step explanation.

Use when the learner wants to understand an existing repository or public/open-source codebase, learn its architecture, trace a feature through it, or build a reading path before dissecting individual files.

Use when the user wants a spec turned into phased work with checklist subtasks persisted in the tasked_phases tool, or when ongoing work should be tracked phase by phase with checked tasks.

Use when configuring or running hexcheck in a Go repo for hexagonal architecture boundaries, adapter business-logic warnings, and mock discipline.