What problem does it solve? Choosing the wrong API or identity model on Weegloo leads to over-privileged tokens, broken member permissions, and leaked data. This Skill maps your product's access model to the correct combination of CMA, CDA, ACMA, ACDA, Upload, ServiceLogin, and token types before you write any code. ## Core Features & Use Cases - Architecture Recipes: Five ready-made recipes covering fully public sites, public sites with admin editing, members-only read services, member read/write communities, and composite multi-tier products. - Identity Disambiguation: Clarifies the two separate identity systems (Weegloo User vs Service User) and which APIs each Bearer token can reach. - Anti-Pattern Detection: Lists forbidden patterns such as exposing Personal Access Tokens in browsers, binding Administrator roles to DeliveryAccessTokens, or routing member writes through CMA. - Use Case: You are building a members-only forum where users post and upload avatars. The Skill directs you to ServiceLogin for sign-up, ACMA with a createdBy :self default role for member writes, Upload plus ACMA Media create for avatars, and CDA with a least-privilege DeliveryAccessToken for any public content. ## Quick Start Ask the agent to plan the Weegloo architecture for your app, describing whether visitors are anonymous, members, or admins.
