The Problem
Collection creative moved between commerce pages, image sources, prompts, generators, design tools, folders, approvals, and campaign platforms. The context behind an asset—what it represented, how it was made, and whether it was ready—was easy to lose.
Product truth lived elsewhere
Collections, product imagery, destinations, and merchandising context had to be rebuilt for every asset.
Generation was only one step
Useful output still required source selection, copy, layout, editing, dimensions, review, and approval.
Files lacked visible lineage
Clean sources, finished compositions, settings, usage history, and approval state were difficult to connect.
Approval needed a controlled exit
Creative should move forward only when a human confirms the final asset and destination structure.
Product Architecture
Asset Studio is organized around four user-facing workspaces with a shared approval and storage model.
One Guided Production Workspace
Collection creative
- Select a live collection and its product or collection imagery.
- Generate new creative, polish a selected image, reuse an Asset Repo source, or upload a finished JPG, PNG, or GIF.
- Edit copy and composition in Designer when the asset needs finishing.
- Require final approval before an asset can move into the reusable repo or destination workflow.
Creative Control After Generation
Asset Studio treats generation as an input to a creative workflow—not as the finished decision.
Choose the right visual role
Use collection heroes, product images, uploads, prior repo assets, references, or a defined three-product composition.
Keep the work editable
Text, layout, image positioning, scale, crop, and output format remain under human control.
Preserve clean sources
Generated source imagery is stored separately from text-composited and finished outputs.
Human review is the release gate
An asset is not treated as final until a user explicitly approves the current version.
Asset Repo and Provenance
The Asset Repo makes approved work reusable without separating the file from the information needed to understand it later.
Sidecar records
Saved assets retain structured provenance, workflow settings, source roles, and relevant collection context.
Start from prior work
Users can open an asset in design mode or rerun a workflow with logged settings.
Manage the library
Filter, inspect metadata, download, select, delete, and analyze approved asset groups.
See recent destination history
Recently used assets are visibly marked so the team can avoid accidental repetition.
System and Delivery Boundary
The product combines a focused frontend with serverless application services and approval-gated movement toward a destination draft.
| Layer | Role | Public description |
|---|---|---|
| React + TypeScript | Creative workspace | Collections, Bulk Create, Designer, Asset Only, Asset Repo, and Settings. |
| Express + Lambda | Application services | Generation jobs, collection context, asset operations, workflow records, and draft preparation. |
| S3 + DynamoDB | Assets and state | Approved files, metadata sidecars, collection workflow status, and configuration records. |
| OpenAI | Creative assistance | Image and copy assistance inside an editable, human-reviewed process. |
| Destination integration | Draft handoff | Approved sections can be assembled into a draft when the destination service is configured. |
What Exists Now
| Capability | Status | Public description |
|---|---|---|
| Collections builder | Deployed | One to five sections using collection, product, upload, and repo sources. |
| Bulk Create | Deployed | Queue multiple collections, formats, and category treatments for review. |
| Designer | Deployed | Editable composition, text, placement, sizing, and export controls. |
| Finished-asset upload | Deployed | JPG, PNG, and GIF intake without forced copy generation. |
| Asset Repo + metadata | Deployed | Reusable asset library with sidecars, analysis, usage, and bulk actions. |
| Public preview | Limited | External testing surface with restricted scope and generation limits. |
| Automated image evaluator | Removed | Human approval remains the active release decision; provenance metadata is retained. |
Public / Private Boundary
Safe to show
- Problem, workflow, and my role
- Collections / Designer / Repo model
- Sanitized interface structure
- Human approval and provenance design
- High-level serverless architecture
- Honest implementation status
- Limited public preview
Intentionally withheld
- Credentials and private identifiers
- Customer, supplier, and internal records
- Proprietary prompts and generation recipes
- Provider payloads and exact API sequences
- Private schemas and business rules
- Source files and production resource names
- Details sufficient to clone the system
Try the limited public preview.
The preview is isolated from internal navigation and operational data.