What problem does it solve? Developers integrating Tigris object storage often don't know whether to use a Tigris-native SDK, a boto3 extension, or a raw AWS S3 SDK for their language, leading to wrong package choices and misconfigured endpoints. ## Core Features & Use Cases - Per-language decision table: Maps TypeScript/JS, Go, Python, Ruby, PHP, and CLI usage to the correct SDK or extension. - CLI guidance: Enforces use of the tigris/t3 CLI over aws s3, including Tigris-only features like forks, snapshots, and native login. - S3-compatible configuration: Provides endpoint, region (auto), and path-style settings required when falling back to AWS SDKs for Ruby and PHP. - Use Case: When starting a new Node.js app, the skill directs you to @tigrisdata/storage instead of @aws-sdk/client-s3, with correct environment variables and client-upload patterns. ## Quick Start Ask which SDK to use for connecting your application in a given language to Tigris object storage.