What problem does it solve? App backends often need auxiliary services like headless browsers, caches, or image processors, but wiring up companion containers with correct networking, secrets, and resource limits is error-prone. This Skill guides the full lifecycle of sidecar containers in FuseBase apps. ## Core Features & Use Cases - Sidecar Lifecycle Management: Add, remove, and list sidecar containers via the fusebase sidecar CLI commands for both backends and cron jobs. - Secrets & Environment Control: Whitelist registered app secrets per sidecar with KEY or KEY:ALIAS forms, and configure isolated environment variables. - Resource & Networking Rules: Enforce tier sizing (small/medium/large), the 2 CPU / 4 Gi total budget, localhost networking, and the reserved port 3000 constraint. - Use Case: A scraping app needs a headless browser. Add a browserless/chrome sidecar on port 9222 with a medium tier, then have the backend call it at http://localhost:9222 after fusebase deploy. ## Quick Start Add a chromium sidecar to my-scraper using the browserless/chrome image on port 9222 with a medium resource tier.