What problem does it solve? Building .NET backends against Appwrite requires knowing the correct SDK patterns—TablesDB versus the deprecated Databases class, string column types, query builders, permission strings, and dual-client SSR authentication—and getting any of these wrong causes silent access failures or insecure sessions. ## Core Features & Use Cases - Server SDK Operations: Covers user management, TablesDB row CRUD with the full Query API, file storage with InputFile factories, teams, and serverless function execution. - SSR Authentication: Implements the admin-client/session-client pattern for ASP.NET and Blazor, including email/password login, OAuth2 token exchange, and secure a_session cookie handling. - Permissions & Error Handling: Provides Permission/Role string construction, common AppwriteException codes, and warnings about insecure Role.Any() usage. - Use Case: You are building an ASP.NET Minimal API backed by Appwrite and need to log users in via OAuth, store their session in an HttpOnly cookie, and create rows in a table with per-user read/update permissions. ## Quick Start Ask the agent to write C# code that creates an Appwrite client with an API key and inserts a row into a table with user-scoped read and update permissions.
