What problem does it solve? The Appwrite CLI has many commands and subtle behaviors that --help does not explain, such as when to use appwrite.config.json versus appwrite client, how regional endpoints differ from the login host, and how to avoid destructive pushes. This Skill encodes those operational rules so agents and developers use the CLI correctly the first time. ## Core Features & Use Cases - Config vs one-off guidance: Distinguishes project workflows (init, pull, push against appwrite.config.json) from one-shot appwrite client calls, preventing schema drift and stray config files. - Type-safe code generation: Explains when to use appwrite generate for a fully typed TypeScript TablesDB wrapper versus appwrite types for model interfaces in TS, JS, PHP, Kotlin, Swift, Java, Dart, or C#. - Safe deploys and CI: Covers --force for non-interactive pushes, API key auth via environment variables, function/site variable handling with --with-variables, and query flags like --filter and --cursor-after. - Use Case: An agent asked to add a column to a table and regenerate types will pull the table, edit appwrite.config.json, push with --force, rerun appwrite generate, and run the type checker instead of issuing raw tablesdb create-* calls. ## Quick Start Ask the assistant to push your local Appwrite table schema changes and regenerate the TypeScript types using the Appwrite CLI.
