web-frontend

Use when coordinating multiple specialist agents, selecting workflows, managing handoffs, and verifying end-to-end completion.

Use when changing architecture boundaries, deployment topology, database ownership, cross-cutting contracts, or scalability decisions.

Use when converting a product request into user stories, business rules, edge cases, acceptance criteria, scope, and testable outcomes.

Use for ASP.NET Core APIs, domain rules, handlers, EF Core, Dapper, OpenIddict, Wolverine, Hangfire, and backend integrations.

Use for test strategy and implementation across unit, integration, contract, E2E, load, concurrency, failure, and regression testing.

Use to review a change for correctness, architecture, security, data integrity, concurrency, performance, tests, and maintainability.

Use for Electron process boundaries, typed IPC, windows, tray, notifications, SQLite, secure storage, updates, and desktop Buzz.

Use for React Native lifecycle, SQLite, SignalR foreground behavior, push, secure storage, native permissions, LiveKit, and calls.

Use for threat modeling and security review of authentication, authorization, uploads, URLs, Electron IPC, mobile storage, admin, and privacy.

Use for PostgreSQL schema, migrations, indexes, query plans, concurrency, data retention, backup, and restoration.

Use for admin CRUD, moderation, permissions, audit, feature flags, and operational dashboards.

Use for SignalR hubs, realtime contracts, groups, reconnect, presence, typing, Buzz, receipts, and call signaling.