What problem does it solve? Building .NET backends against Appwrite requires knowing the correct SDK patterns for user management, table CRUD, file storage, permissions, and SSR session handling, and mistakes like using deprecated classes or missing permissions cause broken or insecure apps. ## Core Features & Use Cases - Server SDK Patterns: Set up API-key clients and perform user management, TablesDB CRUD with typed string columns, and full Query filtering, sorting, and cursor pagination. - Storage, Teams, and Functions: Upload files via InputFile factories, manage teams and memberships, execute serverless functions, and write .NET function handlers. - SSR Authentication: Implement ASP.NET and Blazor login flows with admin and session clients, secure a_session cookies, and OAuth2 token exchange. - Use Case: You are building an ASP.NET Minimal API backed by Appwrite and need email/password login with secure session cookies plus row-level permissions on database records. ## Quick Start Use the appwrite-dotnet skill to scaffold an ASP.NET login endpoint that creates an Appwrite email/password session and sets the secure session cookie.