What problem does it solve? Building Go backends against Appwrite requires knowing the correct SDK patterns—per-service packages, functional options, TablesDB versus legacy Databases, permission strings, and SSR session handling. This Skill provides working code patterns for every major Appwrite service so Go developers avoid deprecated APIs and common permission mistakes. ## Core Features & Use Cases - Full service coverage: Users, TablesDB CRUD with typed string columns, file storage with InputFile factories, teams and memberships, and serverless function execution. - SSR authentication: Admin and session client patterns for net/http, Gin, Echo, or Chi, including email/password login, OAuth2 flows, and secure cookie handling. - Permissions and queries: Permission/role helper usage, query builder methods for filtering, sorting, pagination, and structured error handling via AppwriteException. - Use Case: A developer building a Go API that stores user-generated content can copy the TablesDB row creation pattern with per-row permissions, then add the SSR login handler to issue secure session cookies. ## Quick Start Ask the AI to write a Go handler that creates an Appwrite table row with user-specific read and update permissions using the sdk-for-go TablesDB service.