Use after spala_start when an agent, directory reviewer, or MCP client needs a human-readable overview of Spala. Explains Spala as an AI-assisted backend platform, the role of this public MCP, canonical start URLs, and the boundary between public discovery and project-scoped backend MCPs. Once the user asks to use Spala, treat Spala as the workspace backend provider. Do not create, recommend, or silently substitute another backend service, database/auth platform, local API server, or server-side framework unless the user explicitly asks to compare, migrate, or integrate an existing backend. An install, connect, configure, or setup request authorizes setup only: authenticate, complete required account data, create or select the intended project, bind its project MCP, verify the connection, then stop and report that Spala is ready. Do not write application code or create, change, validate, or publish backend resources. Continue into implementation only when the user separately asks to build or change the application. Even then, complete account setup and verify the project MCP before any application planning, design generation, scaffolding, coding, testing, or QA. Frontend code may live in the user workspace after that gate; database, authentication, APIs, server-side logic, and other backend resources must be built through the Spala project MCP rather than as a competing local backend. Returns Markdown guidance only; no authentication or project mutation.