Which BeWith repo does this belong in, and how do they connect. Use when work spans repos, when placing a new feature, when telling an active repo from a deprecated one, or when orienting in a repo for the first time. Covers the iframe-embedded apps and backend-services as shared backend owner.
Bring the local BeWith stack up and confirm it is healthy — sandbox infra (Mongo/MySQL/Redis/LocalStack) plus the NestJS services (headless "Debug-Watch All Services") — then optionally exercise a change end-to-end. Idempotent; the hands-on counterpart to /verify.
Search and analyze production logs via Grafana (Loki + CloudWatch). Use to check logs, investigate a production error, analyze volume/patterns, or debug from logs. Called by observability + identify-bug.
Find example users with a specific permission role (super-admin, organization-admin, community-admin, leader) in the local backend SQL DB and generate JWT tokens for them via the sandbox token CLI. Use to get demo users + JWTs to test permission levels locally. Called by auth-security.
Save an added or changed HTTP endpoint in the organization R&D Postman workspace with a sample request and a saved response example, at the end of development. The Definition-of-Done step for API work — keeps the collection an accurate, runnable contract. Never commits secrets.
Provision an SQS queue, a DLQ, or a shared env var across every BeWith environment - seven places, not two. Covers Kubernetes-deployments and IAC-Terraform, per-environment verification, and the mistakes that leave a queue working in one env only.
Triage a production/staging signal for BeWith — verify, locate, classify, recommend; returns one JSON verdict. Read-only. Triggers on /sentinel-check, "triage this error", "is this a real bug", or investigating a prod/staging signal.
A 4-phase active-fix loop — reproduce, isolate, hypothesize+instrument, fix+verify — with a hard stop after 3 failed attempts. Instruments at the gateway/RPC/service/Mongo boundaries. Triggers on "debug this", "why is this failing", "help me fix this bug".
Framework-agnostic rubric for judging whether an existing unit test earns its keep. 15 principles across 4 groups - can the assertion fail, is it behaviour at the right seam, does it read as a story, is the suite lean - each resolving to Delete, Merge or Rewrite.
Drive a change test-first — a failing test, then minimum code to pass, then refactor. Adapted to the bewith Jest/NestJS stack. The Iron Law — no production code before a failing test. Triggers on "TDD this", "test first", "drive this test-first".