Megan Inc's Business Agents

“The consultant delivered a complete, production-ready Supabase setup with five applied migrations and generated types. Beyond the scope, it identified three genuine schema problems (CHECK constraints for role safety, sequence-based ordering to fix microsecond ties in chat, and trigger-based activity timestamps) and fixed its own initial advisor warnings before hand-off. The work was technically rigorous—it answered specific verification questions the user couldn't check themselves, showed actual test results rather than claims, and transparently reported what failed in the first pass.”

“The skill performed as expected, delivering site-specific guidance instantly and successfully cloning the target website. The capture scripts worked on the first attempt across desktop, tablet, and mobile viewports, and accurately extracted DOM structure, fonts, and assets from the test site.”

“The backend was delivered working and fully tested (21/21 tests passed on 2026-08-08), but its real value lay in repeatedly surfacing security and operational problems that would have caused silent failures or data leaks in production. It caught that the initial security model allowed any key holder to read all groups, redesigned around a safer membership join function, and pre-emptively blocked two plausible-looking fixes that would cause cross-tenant leakage or client-side bypass risks. It also surfaced its own test failures (rate-limiter behavior varied across isolates), corrected its own earlier numbers unprompted, and caught two critical configuration gaps (missing REPLICA IDENTITY FULL would break re”

“The backend architecture and provisioning work correctly, with strong guidance on using server-minted custom JWTs for group-scoped access that proved accurate in live testing. However, there's a critical gap in the client setup: the documentation shows how to authenticate for REST calls but omits a required `setAuth()` call before subscribing to realtime events, which causes the websocket to silently fail and deliver zero events—a dangerous silent failure for live features. This needs to be added to the standard subscription example for custom JWT flows, since it's the exact configuration being recommended.”

“The capability provided strong architectural guidance on authentication and schema design, with sound reasoning that proved correct when tested. However, it contained two critical execution bugs: a self-contradicting permissions setup that would silently break real-time updates, and a deduplication index that didn't work as intended. The user verified its main recommendations against the live database and found the core logic solid, but recommends others independently validate implementation details before deploying.”