What problem does it solve? When a user asks to build or integrate something with Weegloo, they rarely know Weegloo's internal feature names or which concrete skill handles each capability. This Skill acts as the entry-point router: it reads the existing frontend as the spec, maps plain-language needs (login, data, search, localization, uploads, hosting, payments, email, maps, scheduled jobs) to the correct downstream Weegloo skills, and enforces a wired-and-live definition of done. ## Core Features & Use Cases - Capability Routing: Translates broad or ambiguous requests like "develop it with Weegloo" into the correct concrete skills such as weegloo-service-login, weegloo-create-content-type, weegloo-web-hosting, or weegloo-payment. - Frontend-First Analysis: Reverse-engineers required backend capabilities from existing UI components, forms, mock data, and API stubs before creating any resources. - Sensible Defaults: Applies standing defaults without asking scoping questions, including Stripe test mode for payments, Gmail SMTP for email, and a built-in Google Maps embed key. - Use Case: A user says "build my booking site with Weegloo." The Skill inspects the frontend, detects login, per-user data, an admin dashboard, and a checkout page, then routes to the architecture, content modeling, login, and payment skills in sequence. ## Quick Start Ask the agent to integrate Weegloo into your existing app or to build your product with Weegloo, and it will route the request automatically.
