Skip to content

[Fleet Execution] Add Tier 1 Script Examples #302

@jules-fleet

Description

@jules-fleet

Objective

Create foundational Tier 1 examples (deterministic scripts) for the Stitch SDK: basic generation, browsing and exporting, batch execution, and gallery generation.

Code-Level Diagnosis

Code path: packages/sdk/examples/
Mechanism: The packages/sdk/examples/ directory contains a mix of single-file scripts but lacks structured directory-based core examples.
Root cause: Absence of foundational scenario-based scripts that demonstrate linear SDK execution without agent wrappers.

Current Implementation

// Missing structured script examples like basic-design/, browse-and-export/, etc.

Proposed Implementation

Files to modify: Create structured directories for basic-design, browse-and-export, batch-generation, and screenshot-gallery.

Integration (Before -> After)

- packages/sdk/examples/generate-screen.ts
- packages/sdk/examples/browse-designs.ts
+ packages/sdk/examples/basic-design/index.ts
+ packages/sdk/examples/basic-design/README.md
+ packages/sdk/examples/browse-and-export/index.ts
+ packages/sdk/examples/browse-and-export/README.md
+ packages/sdk/examples/batch-generation/index.ts
+ packages/sdk/examples/batch-generation/README.md
+ packages/sdk/examples/screenshot-gallery/index.ts
+ packages/sdk/examples/screenshot-gallery/README.md

Test Scenarios

  1. Basic Design: Execute bun index.ts -> Generates design sequentially.

Target Files

  • packages/sdk/examples/basic-design/index.ts
  • packages/sdk/examples/basic-design/README.md
  • packages/sdk/examples/browse-and-export/index.ts
  • packages/sdk/examples/browse-and-export/README.md
  • packages/sdk/examples/batch-generation/index.ts
  • packages/sdk/examples/batch-generation/README.md
  • packages/sdk/examples/screenshot-gallery/index.ts
  • packages/sdk/examples/screenshot-gallery/README.md
  • packages/sdk/examples/generate-screen.ts
  • packages/sdk/examples/browse-designs.ts

Boundary Rules

Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.


Fleet Context

Metadata

Metadata

Assignees

No one assigned

    Labels

    fleetFleet-managed issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions