What problem does it solve? Developers building on the DaaS (Data-as-a-Service) platform often rebuild features the backend already provides, misuse MCP tool parameters, or hit subtle authentication and CORS bugs. This Skill supplies the architectural rules, API patterns, and production-learned fixes needed to integrate Next.js frontends with DaaS and Supabase correctly. ## Core Features & Use Cases - Two-Tier Architecture Guidance: Enforces the rule that frontends call the DaaS REST API for all data operations and use Supabase only for authentication, never querying the database directly. - Backend-First Rule: Maps common requirements (audit trails, workflows, cron jobs, RBAC, file storage, multi-tenancy) to built-in DaaS features so agents do not rebuild them in Next.js. - MCP Tool Reference: Documents every DaaS MCP tool (items, schema, fields, permissions, extensions, cron, services, scope) with correct parameter formats and known pitfalls. - Production Bug Fixes: Codifies provider architecture rules for DaaSProvider placement, token handling via onAuthStateChange, CORS configuration, and scope forwarding. - Use Case: When asked to add audit logging to a collection, the Skill directs you to query the built-in /api/activity endpoint instead of writing custom logging middleware. ## Quick Start Ask the agent to create a new DaaS collection with fields and read permissions, and it will verify the schema and use the correct MCP tools automatically.
