What problem does it solve? The Appwrite CLI has many commands and flags, and common mistakes—like treating a real project as one-off API calls, forcing pushes against empty local config, or leaking API keys into committed files—cause broken deployments and lost schema state. This Skill encodes the correct workflows so you avoid those traps. ## Core Features & Use Cases - Config vs one-off decisions: Learn when to use appwrite.config.json with init/pull/push versus appwrite client for single API calls, and how auth, endpoints, and environment variables interact. - Type-safe code generation: Generate a fully typed TypeScript TablesDB wrapper with appwrite generate, or model types in eight languages with appwrite types, always derived from the local config. - Safe deployments and queries: Push functions, sites, and tables with correct --force, --with-variables, and --activate flags, and query data with --filter, --sort-desc, and cursor pagination instead of deprecated flags. - Use Case: You are setting up CI to deploy an Appwrite function. The Skill tells you to check in appwrite.config.json without secrets, authenticate with appwrite client --key "$APPWRITE_API_KEY", and run appwrite push function --force. ## Quick Start Ask the AI to help you initialize an Appwrite project, pull its table schema, and generate type-safe TypeScript code using the Appwrite CLI.