📦 ADDITIONAL DIRECTORIES

container/

Purpose: Sandbox container tooling for local development and debugging

Location: /container/

Key files:

1. cli-tools.ts - Command-line interface for container operations:

   • File synchronization
   • Command execution in sandbox
   • Log retrieval
   • Static analysis
   • Runtime error monitoring

2. storage.ts - Persistent storage management:

   • Key-value store for container state
   • File system operations
   • Cache management

3. process-monitor.ts - Process lifecycle monitoring:

   • Dev server health checks
   • Process restart on crashes
   • Resource usage tracking
   • Error collection

4. types.ts - TypeScript types for container APIs

Usage: These tools are used internally by the sandbox service and for local debugging. Not typically modified unless adding new sandbox features.

---

templates/

Purpose: Project template system for generating new apps

Location: /templates/

Key files:

1. template_catalog.json - Master catalog of all available templates:

   • React (Vite, CRA)
   • Next.js
   • Vue
   • Svelte
   • Vanilla JS Each with metadata: name, description, files, dependencies

2. definitions/ - Template definition files (not in repo, generated)

3. zips/ - Compressed template archives for deployment

4. generate_template_catalog.py - Builds catalog from template sources

5. deploy_templates.sh - Deploys templates to production

6. reference/ - Reference implementations

How templates work:

1. Agent selects template based on user's requirements (React, Vue, etc.)
2. Template provides base files (package.json, tsconfig, etc.)
3. Agent generates additional files on top of template
4. All files deployed to sandbox for preview

Adding new templates:

1. Create template definition in definitions/
2. Run python generate_template_catalog.py
3. Test locally with agent
4. Deploy: bash deploy_templates.sh