Coding Standards

TypeScript: No any

Never use any unless absolutely necessary — and that should be a final resort.

Process when you reach for any:

1. Look for an existing type that fits. Most domains already have one.
2. If no suitable type exists, define a proper one in the right location:
   • Shared types → packages/shared/src/types.ts or relevant subdirectory
   • SDK-specific types → packages/sandbox/src/clients/types.ts or the appropriate client file
   • Container-specific types → under packages/sandbox-container/src/ with appropriate naming
3. Use the new type everywhere it applies — don't leave one-off shapes scattered around.

This catches errors at compile time instead of runtime and keeps the codebase consistent.

Style: Uppercase Acronyms