studio
Ship production-ready code with full type safety, instant autocomplete, and time-travel debugging. Build, test, and deploy with zero configuration and complete observability built-in.
studio
Studio.do
Overview
The studio primitive is part of the .do platform's semantic API system. It follows the $.Subject.verb.Object pattern for consistent, intuitive interactions across SDK, CLI, API, and MCP interfaces.
Semantic Pattern
All studio operations follow the semantic $.Studio.verb.Object pattern:
import { $, studio } from 'sdk.do'
// Create resources
await $.Studio.create.Resource({ /* config */ })
// Query data
await $.Studio.get.Data({ /* params */ })
// Update state
await $.Studio.update.Status({ /* changes */ })Quick Start
import { studio } from 'sdk.do'
// Initialize and use the primitive
const result = await studio.operation({
// configuration parameters
})Access Methods
The studio primitive is accessible through multiple interfaces:
SDK
TypeScript/JavaScript library for programmatic access:
import { studio } from 'sdk.do'
await studio.method({ /* ... */ })CLI
Command-line interface for terminal operations:
do studio <command> [options]API
REST/RPC endpoints for HTTP integration:
curl -X POST https://api.do/v1/studio \
-H "Content-Type: application/json" \
-d '{"key":"value"}'MCP
Model Context Protocol for AI assistant integration:
Use studio primitives with AI assistants via MCPRelated Primitives
See other primitives in the infrastructure category.