Rename Figma plugin for Studio

Author: chubes4

docs/README.md

@@ -20,7 +20,7 @@ Start here before changing skills, generator code, verification contracts, or ge
 | [Generated outputs](generated-outputs.md) | Generated package matrix, build pipeline, generated-output contracts, MCP config shape, telemetry MCP tool reference, verifier expectations, and Cursor export contract. | Change or review generated files under `plugins/`, add a surface, or reason about package artifacts. |
 | [Skills and integrations](skills-and-integrations.md) | Skill inventory, Studio integration concepts, MCP contracts, relationship to WordPress agent skills packaging, and safe extension boundaries. | Update shared skills, Studio guidance, or agent integration behavior. |
 | [Contributor workflows](contributor-workflows.md) | Setup, commands, change recipes, manual smoke testing, CI automation contracts, and pull request checklist. | Prepare, verify, and review a repository change. |
-| [Figma to WordPress](figma-playground-runner.md) | Figma plugin handoff to a WordPress Playground runner for Static Site Importer and Blocks Engine. | Review or test the Figma-to-HTML-to-WordPress integration path. |
+| [Figma to WordPress Studio](figma-studio-runner.md) | Figma plugin handoff to a WordPress Studio runner for Static Site Importer and Blocks Engine. | Review or test the Figma-to-HTML-to-WordPress integration path. |
 
 ## Repository source inventory
 

docs/figma-playground-runner.md docs/figma-studio-runner.mddocs/figma-playground-runner.md renamed to docs/figma-studio-runner.md

@@ -1,6 +1,6 @@
-# Figma to WordPress
+# Figma to WordPress Studio
 
-`plugins/figma-to-wordpress` moves a Figma file into WordPress. It hands the design to a WordPress runner service that creates a Playground session and imports the result with Static Site Importer and Blocks Engine.
+`plugins/figma-to-wordpress-studio` moves a Figma file into WordPress. It hands the design to a WordPress runner service that creates a Studio session and imports the result with Static Site Importer and Blocks Engine.
 
 ## Architecture
 
@@ -9,11 +9,11 @@ Figma plugin UI
   -> Figma document scene data
   -> runner request
   -> WordPress runner service
-  -> WordPress Playground session URL
+  -> WordPress Studio session URL
   -> Static Site Importer / Blocks Engine inside WordPress
 ```
 
-The TypeScript boundary stops at request construction and opening the returned Playground URL. WordPress, PHP, Static Site Importer, Blocks Engine, and Playground session orchestration remain WordPress-side runtime concerns.
+The TypeScript boundary stops at request construction and opening the returned Studio URL. WordPress, PHP, Static Site Importer, Blocks Engine, and Studio session orchestration remain WordPress-side runtime concerns.
 
 ## Figma Iframe Limits
 
@@ -29,9 +29,9 @@ Practical constraints for this browser-based flow:
 
 Because of those constraints, the primary integration shape is a service handoff: the plugin posts a runner request and opens the returned URL in a browser tab. If in-plugin embedding works later, it can consume the same runner response interface.
 
-## Playground And PHP Role
+## Studio And PHP Role
 
-WordPress Playground is the correct place to run WordPress and PHP plugin logic. It provides a browser-hosted WordPress runtime backed by WebAssembly PHP and a virtual filesystem.
+WordPress Studio is the correct place to run WordPress and PHP plugin logic. It provides a browser-hosted WordPress runtime backed by WebAssembly PHP and a virtual filesystem.
 
 Static Site Importer and Blocks Engine should run in that WordPress runtime because they are WordPress/PHP import systems. The Figma plugin should not reimplement them in TypeScript. The plugin's job is to hand off design data with enough metadata for the WordPress runner to transform, install, activate, and import with those plugins.
 
@@ -40,32 +40,32 @@ Static Site Importer and Blocks Engine should run in that WordPress runtime beca
 Implemented now:
 
 - `GeneratedWebsiteArtifact` for static generated files from Figma.
-- `figma-to-wordpress/runner-request/v1` for the runner handoff plan.
-- A Figma UI client that posts the runner request and opens the returned Playground URL.
+- `figma-to-wordpress-studio/runner-request/v1` for the runner handoff plan.
+- A Figma UI client that posts the runner request and opens the returned Studio URL.
 
 Not implemented yet:
 
-- The hosted WordPress runner endpoint that creates the Playground session.
+- The hosted WordPress runner endpoint that creates the Studio session.
 - Post-import block validation and visual parity checks.
 
 ## Local Testing
 
 From the repository root, run the plugin checks:
 
 ```bash
-npm run check --prefix plugins/figma-to-wordpress
-npm run build --prefix plugins/figma-to-wordpress
-npm test --prefix plugins/figma-to-wordpress
+npm run check --prefix plugins/figma-to-wordpress-studio
+npm run build --prefix plugins/figma-to-wordpress-studio
+npm test --prefix plugins/figma-to-wordpress-studio
 ```
 
 Figma development test:
 
-1. Run `npm run build --prefix plugins/figma-to-wordpress`.
-2. Load `plugins/figma-to-wordpress/manifest.json` as a Figma development plugin.
+1. Run `npm run build --prefix plugins/figma-to-wordpress-studio`.
+2. Load `plugins/figma-to-wordpress-studio/manifest.json` as a Figma development plugin.
 3. Run the plugin.
-4. Use `Open in WordPress Playground`.
-5. Confirm the runner service returns a Playground URL that opens in a normal browser tab.
+4. Use `Open in WordPress Studio`.
+5. Confirm the runner service returns a Studio URL that opens in a normal browser tab.
 
 ## Next Integration Step
 
-The next meaningful step is a hosted WordPress runner endpoint with progress/error reporting around the Playground import and post-import block/visual validation. That should remain in the WordPress/Playground runner layer, not by porting PHP importer behavior into the Figma plugin.
+The next meaningful step is a hosted WordPress runner endpoint with progress/error reporting around the Studio import and post-import block/visual validation. That should remain in the WordPress/Studio runner layer, not by porting PHP importer behavior into the Figma plugin.

plugins/figma-to-wordpress/README.md …gins/figma-to-wordpress-studio/README.mdplugins/figma-to-wordpress/README.md renamed to plugins/figma-to-wordpress-studio/README.md plugins/figma-to-wordpress/README.md renamed to plugins/figma-to-wordpress-studio/README.md

@@ -1,8 +1,8 @@
-# Figma to WordPress
+# Figma to WordPress Studio
 
-This plugin moves a Figma file into WordPress by handing the design to a WordPress runner service that imports it with Static Site Importer and Blocks Engine in WordPress Playground.
+This plugin moves a Figma file into WordPress by handing the design to a WordPress runner service that imports it with Static Site Importer and Blocks Engine in WordPress Studio.
 
-It does not port Static Site Importer, Blocks Engine, WordPress, PHP, or Playground internals to TypeScript. The TypeScript code extracts Figma scene data, prepares the runner request, and opens the Playground session URL returned by the WordPress-side runner.
+It does not port Static Site Importer, Blocks Engine, WordPress, PHP, or Studio internals to TypeScript. The TypeScript code extracts Figma scene data, prepares the runner request, and opens the Studio session URL returned by the WordPress-side runner.
 
 ## Flow
 
@@ -11,17 +11,17 @@ Figma plugin controller + UI
   -> whole Figma document scene data
   -> runner request
   -> WordPress runner service
-  -> WordPress Playground session
+  -> WordPress Studio session
   -> Static Site Importer imports through Blocks Engine
 ```
 
 ## Boundaries
 
 - Implemented: a Figma Desktop-loadable plugin shell with whole-file export.
 - Implemented: a reusable scene-to-HTML/CSS artifact generator with diagnostics and tests for the current local handoff.
-- Implemented: a product-neutral runner request that can be posted to a WordPress-side Playground session service.
+- Implemented: a product-neutral runner request that can be posted to a WordPress-side Studio session service.
 - Not implemented: running Static Site Importer from TypeScript.
-- Not implemented: the hosted WordPress runner endpoint that creates the Playground session and returns its URL.
+- Not implemented: the hosted WordPress runner endpoint that creates the Studio session and returns its URL.
 - Not implemented: automated visual parity/block validation after import.
 
 ## Files
@@ -36,21 +36,21 @@ Figma plugin controller + UI
 
 ## Local Test
 
-1. Run `npm run build --prefix plugins/figma-to-wordpress`.
-2. In Figma Desktop, use Plugins -> Development -> Import plugin from manifest, then select `plugins/figma-to-wordpress/manifest.json`.
-3. Open the plugin and choose `Open in WordPress Playground`.
-4. Confirm the WordPress runner service returns a Playground URL and the plugin opens it in a browser tab.
+1. Run `npm run build --prefix plugins/figma-to-wordpress-studio`.
+2. In Figma Desktop, use Plugins -> Development -> Import plugin from manifest, then select `plugins/figma-to-wordpress-studio/manifest.json`.
+3. Open the plugin and choose `Open in WordPress Studio`.
+4. Confirm the WordPress runner service returns a Studio URL and the plugin opens it in a browser tab.
 
 For quick syntax verification without a full Figma build pipeline:
 
 ```bash
-npm run check --prefix plugins/figma-to-wordpress
-npm run build --prefix plugins/figma-to-wordpress
-npm test --prefix plugins/figma-to-wordpress
+npm run check --prefix plugins/figma-to-wordpress-studio
+npm run build --prefix plugins/figma-to-wordpress-studio
+npm test --prefix plugins/figma-to-wordpress-studio
 ```
 
 ## Runner Boundary
 
-Figma plugin UIs run in a constrained iframe-like environment. Cross-origin iframes, WASM boot, popup behavior, and navigation can be restricted depending on host context and plugin permissions. The supported boundary is a WordPress-side runner service: the plugin posts a runner request, the service creates the Playground session, and the plugin opens the returned URL.
+Figma plugin UIs run in a constrained iframe-like environment. Cross-origin iframes, WASM boot, popup behavior, and navigation can be restricted depending on host context and plugin permissions. The supported boundary is a WordPress-side runner service: the plugin posts a runner request, the service creates the Studio session, and the plugin opens the returned URL.
 
-See [`../../docs/figma-playground-runner.md`](../../docs/figma-playground-runner.md) for the integration notes.
+See [`../../docs/figma-studio-runner.md`](../../docs/figma-studio-runner.md) for the integration notes.

…-to-wordpress/fixtures/sample-scene.json …dpress-studio/fixtures/sample-scene.jsonplugins/figma-to-wordpress/fixtures/sample-scene.json renamed to plugins/figma-to-wordpress-studio/fixtures/sample-scene.json plugins/figma-to-wordpress/fixtures/sample-scene.json renamed to plugins/figma-to-wordpress-studio/fixtures/sample-scene.json

@@ -1,6 +1,6 @@
 {
-  "name": "Figma to WordPress",
-  "id": "figma-to-wordpress",
+  "name": "Figma to WordPress Studio",
+  "id": "figma-to-wordpress-studio",
   "api": "1.0.0",
   "main": "dist/code.js",
   "ui": "dist/ui.html",

plugins/figma-to-wordpress/manifest.json …/figma-to-wordpress-studio/manifest.jsonplugins/figma-to-wordpress/manifest.json renamed to plugins/figma-to-wordpress-studio/manifest.json plugins/figma-to-wordpress/manifest.json renamed to plugins/figma-to-wordpress-studio/manifest.json

@@ -1,8 +1,8 @@
 {
-  "name": "figma-to-wordpress",
+  "name": "figma-to-wordpress-studio",
   "version": "0.1.0",
   "private": true,
-  "description": "Figma Desktop plugin for importing a Figma file into WordPress through WordPress Playground.",
+  "description": "Figma Desktop plugin for importing a Figma file into WordPress through WordPress Studio.",
   "license": "GPL-2.0-or-later",
   "scripts": {
     "build": "node scripts/build.mjs",

…ins/figma-to-wordpress/package-lock.json …ma-to-wordpress-studio/package-lock.jsonplugins/figma-to-wordpress/package-lock.json renamed to plugins/figma-to-wordpress-studio/package-lock.json plugins/figma-to-wordpress/package-lock.json renamed to plugins/figma-to-wordpress-studio/package-lock.json

@@ -45,7 +45,7 @@ if (watch) {
   await controllerContext.watch();
   await uiContext.watch();
   await writeUiHtml();
-  console.log("Watching Figma to WordPress plugin sources.");
+  console.log("Watching Figma to WordPress Studio plugin sources.");
 } else {
   await Promise.all([
     esbuild.build({

plugins/figma-to-wordpress/package.json …s/figma-to-wordpress-studio/package.jsonplugins/figma-to-wordpress/package.json renamed to plugins/figma-to-wordpress-studio/package.json plugins/figma-to-wordpress/package.json renamed to plugins/figma-to-wordpress-studio/package.json

@@ -3,7 +3,7 @@ import type { NormalizedAsset, NormalizedDocument, NormalizedSceneNode, PluginTo
 
 figma.showUI(__html__, { width: 420, height: 420, themeColors: true });
 
-const runnerEndpointStorageKey = "figma-to-wordpress-runner-endpoint";
+const runnerEndpointStorageKey = "figma-to-wordpress-studio-runner-endpoint";
 
 function postToUi(message: PluginToUiMessage) {
   figma.ui.postMessage(message);