Use when the user explicitly wants unusually strong pushback, tougher assumption-testing, devil's-advocate reasoning, or a higher-than-normal skepticism setting beyond the repository's baseline directness. Prioritize finding weak logic, missing evidence, bad tradeoffs, and blind spots before endorsing anything.
Use when designing, reviewing, or extending InboxBridge browser extensions for Chromium, Firefox, or Safari. Captures official browser-extension best practices around permissions, storage, auth, packaging, and testing.
Use when changing the React admin UI, the /remote surface, translated copy, layout behavior, or frontend controller/component structure in InboxBridge. Focuses on frontend conventions, translation expectations, and frontend validation.
Use when changing the Quarkus backend, Flyway schema, mailbox import logic, auth/session services, or REST endpoints in InboxBridge. Focuses on backend architecture, transactional boundaries, security invariants, and backend validation.
Use when reviewing, refactoring, or extending the Quarkus backend architecture in InboxBridge. Captures modern Quarkus, Java 25, Maven, testing, package-structure, and backend-boundary best practices adapted to this repository.
Use when reorganizing or extending React code in InboxBridge. Captures the repo's preferred React structure, state, composition, and styling conventions.
Use when changing polling, IMAP/POP3 handling, destination imports, OAuth mailbox flows, deduplication, or live poll controls in InboxBridge. Focuses on the project's highest-risk mailflow, isolation, and security invariants.
Use when working anywhere in the InboxBridge repository or when a request is broad and spans backend, frontend, docs, validation, or release workflow. Applies the repository's standing rules before making changes.