Context
This tracks a proof-of-concept workflow for turning an HTML/CSS design into editable WordPress blocks, then packaging the resulting workspace as a block theme from Studio AI.
What to validate
- Whether the html-to-blocks workspace model is the right abstraction for generated and imported designs.
- Whether the engine/tool split is fast enough for Studio's desktop agent path.
- Whether the visual comparison and completion gates are strict enough for final theme installation.
- Whether generated mockup creation should move out of generic file tools and into a dedicated workspace/engine primitive.
Current known risks
- Large generated designs can produce many model/tool turns through
Write and Edit.
- Screenshot and visual-diff payloads can make sessions large.
- The engine currently runs as a child process per Studio tool call, so it does not benefit from a warm persistent harness.
Context
This tracks a proof-of-concept workflow for turning an HTML/CSS design into editable WordPress blocks, then packaging the resulting workspace as a block theme from Studio AI.
What to validate
Current known risks
WriteandEdit.