wp-studio 1.7.7-beta1 → 1.7.7

package/dist/cli/wp-files/agent-skills/wp-block-themes/SKILL.md

@@ -1,116 +0,0 @@
----
-name: wp-block-themes
-description: "Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching)."
-compatibility: "Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI."
----
-
-# WP Block Themes
-
-## When to use
-
-Use this skill for block theme work such as:
-
-- editing `theme.json` (presets, settings, styles, per-block styles)
-- adding or changing templates (`templates/*.html`) and template parts (`parts/*.html`)
-- adding patterns (`patterns/*.php`) and controlling what appears in the inserter
-- adding style variations (`styles/*.json`)
-- debugging “styles not applying” / “editor doesn’t reflect theme.json”
-
-## Inputs required
-
-- Repo root and which theme is targeted (theme directory if multiple exist).
-- Target WordPress version range (theme.json version and features vary by core version).
-- Where the issue manifests: Site Editor, post editor, frontend, or all.
-
-## Procedure
-
-### 0) Triage and locate block theme roots
-
-1. Run triage:
-   - `node skills/wp-project-triage/scripts/detect_wp_project.mjs`
-2. Detect theme roots + key folders:
-   - `node skills/wp-block-themes/scripts/detect_block_themes.mjs`
-
-If multiple themes exist, pick one and scope all changes to that theme root.
-
-### 1) Create a new block theme (if needed)
-
-If you are creating a new block theme from scratch (or converting a classic theme):
-
-- Prefer starting from a known-good scaffold (or exporting from a WP environment) rather than guessing file layout.
-- Be explicit about the minimum supported WordPress version because `theme.json` schema versions differ.
-
-Read:
-- `references/creating-new-block-theme.md`
-
-After creating the theme root, re-run `detect_block_themes` and continue below.
-
-### 2) Confirm theme type and override expectations
-
-- Block theme indicators:
-  - `theme.json` present
-  - `templates/` and/or `parts/` present
-- Remember the style hierarchy:
-  - core defaults → theme.json → child theme → user customizations
-  - user customizations can make theme.json edits appear “ignored”
-
-Read:
-- `references/debugging.md` (style hierarchy + fastest checks)
-
-### 3) Make `theme.json` changes safely
-
-Decide whether you are changing:
-
-- **settings** (what the UI allows): presets, typography scale, colors, layout, spacing
-- **styles** (how it looks by default): CSS-like rules for elements/blocks
-
-Read:
-- `references/theme-json.md`
-
-### 4) Templates and template parts
-
-- Templates live under `templates/` and are HTML.
-- Template parts live under `parts/` and must not be nested in subdirectories.
-
-Read:
-- `references/templates-and-parts.md`
-
-### 5) Patterns
-
-Prefer filesystem patterns under `patterns/` when you want theme-owned patterns.
-
-Read:
-- `references/patterns.md`
-
-### 6) Style variations
-
-Style variations are JSON files under `styles/`. Note: once a user picks a style variation, that selection is stored in the DB, so changing the file may not “update what the user sees” automatically.
-
-Read:
-- `references/style-variations.md`
-
-## Verification
-
-- Site Editor reflects changes where expected (Styles UI, templates, patterns).
-- Frontend renders with expected styles.
-- If styles aren’t changing, confirm whether user customizations override theme defaults.
-- Run the repo’s build/lint scripts if assets are involved (fonts, custom JS/CSS build).
-
-## Failure modes / debugging
-
-Start with:
-
-- `references/debugging.md`
-
-Common issues:
-
-- wrong theme root (editing an inactive theme)
-- user customizations override your defaults
-- invalid `theme.json` shape/typos prevent application
-- templates/parts in wrong folders (or nested parts)
-
-## Escalation
-
-If upstream behavior is unclear, consult canonical docs:
-
-- Theme Handbook and Block Editor Handbook for `theme.json`, templates, patterns, and style variations.

package/dist/cli/wp-files/agent-skills/wp-block-themes/references/creating-new-block-theme.md

@@ -1,37 +0,0 @@
-# Creating a new block theme
-
-Use this file when you need to create a new block theme or convert a theme to block theme structure.
-
-## Two practical starting points
-
-1. **Export from a WP environment**
-   - Use the official “Create Block Theme” plugin to generate/export a theme from the Site Editor.
-   - This tends to produce a structure aligned with current WordPress behavior.
-
-2. **Create the minimal filesystem structure**
-   - Create a theme folder with:
-     - `style.css` (theme header)
-     - `theme.json` (global settings/styles)
-     - `templates/index.html` (minimum viable template)
-     - `parts/header.html` and `parts/footer.html` (recommended)
-
-## References
-
-- Create Block Theme plugin:
-  - https://wordpress.org/plugins/create-block-theme/
-- Block theme structure:
-  - https://developer.wordpress.org/themes/block-themes/theme-structure/
-- Required templates:
-  - https://developer.wordpress.org/themes/block-themes/templates-and-template-parts/
-
-## theme.json version choice (compatibility)
-
-`theme.json` has schema versions. Pick the highest version that matches your minimum supported WordPress version.
-
-References:
-
-- Theme Handbook introduction:
-  - https://developer.wordpress.org/themes/global-settings-and-styles/introduction-to-theme-json/
-- Theme.json version 3 dev note:
-  - https://make.wordpress.org/core/2024/06/19/theme-json-version-3/
-

package/dist/cli/wp-files/agent-skills/wp-block-themes/references/debugging.md

@@ -1,24 +0,0 @@
-# Debugging block theme issues
-
-## Styles not applying
-
-Fast checks:
-
-1. Confirm you edited the active theme (Site Editor → theme).
-2. Check if user customizations exist (they override theme defaults).
-3. Validate `theme.json` structure (typos can prevent styles from applying).
-
-Remember the hierarchy:
-
-- core defaults → theme.json → child theme → user customizations
-
-## Templates/parts not showing
-
-- Ensure files are in the correct folders (`templates/`, `parts/`).
-- Template parts must not be nested in subdirectories.
-
-## Style variations not updating
-
-- If a user already selected the variation, the selection is stored in the DB.
-- Test with a fresh site/user or reset customizations when appropriate.
-

package/dist/cli/wp-files/agent-skills/wp-block-themes/references/patterns.md

@@ -1,18 +0,0 @@
-# Patterns (filesystem patterns)
-
-Use this file when adding patterns that should be available in the inserter.
-
-## Filesystem patterns
-
-- Put patterns in `patterns/*.php`.
-- Patterns are registered automatically by WordPress core based on file headers.
-
-Upstream reference:
-
-- https://developer.wordpress.org/themes/patterns/
-
-## Practical guardrails
-
-- Keep pattern markup stable; changing block names inside patterns can break older content in subtle ways.
-- If a pattern should not be inserted directly by users, mark it as non-inserter / internal-only (per upstream header conventions).
-

package/dist/cli/wp-files/agent-skills/wp-block-themes/references/style-variations.md

@@ -1,14 +0,0 @@
-# Style variations (`styles/*.json`)
-
-Use this file when adding or debugging style variations.
-
-Key points:
-
-- Style variations are JSON files in `styles/`.
-- Users can pick a style variation in the UI.
-- Once selected, the choice is stored in the DB (so “changing the JSON file” may not update what a user already selected).
-
-Upstream reference:
-
-- https://developer.wordpress.org/themes/global-settings-and-styles/style-variations/
-

package/dist/cli/wp-files/agent-skills/wp-block-themes/references/templates-and-parts.md

@@ -1,16 +0,0 @@
-# Templates and template parts
-
-Use this file when creating or editing HTML templates/parts.
-
-## Key folders
-
-- `templates/` for templates.
-- `parts/` for template parts.
-
-Template parts must not be nested in subdirectories.
-
-Upstream references:
-
-- Templates + parts overview: https://developer.wordpress.org/themes/block-themes/theme-structure/
-- Template parts details: https://developer.wordpress.org/themes/block-themes/template-parts/
-

package/dist/cli/wp-files/agent-skills/wp-block-themes/references/theme-json.md

@@ -1,59 +0,0 @@
-# `theme.json` guidance
-
-Use this file when changing global settings/styles or per-block styling.
-
-## High-level structure
-
-Common top-level keys:
-
-- `version`
-- `settings` (what the UI exposes / allows)
-- `styles` (default appearance)
-- `customTemplates` and `templateParts` (optional, to describe templates and parts)
-
-Upstream references:
-
-- Theme Handbook: https://developer.wordpress.org/themes/global-settings-and-styles/
-- Block Editor Handbook (often more current): https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-json/
-- Theme JSON living reference: https://developer.wordpress.org/block-editor/reference-guides/theme-json-reference/theme-json-living/
-- Theme JSON version 3 (dev note): https://make.wordpress.org/core/2024/06/19/theme-json-version-3/
-
-## Practical guardrails
-
-- Prefer presets when you want editor-visible controls (colors, font sizes, spacing).
-- Prefer `styles` when you want consistent defaults without requiring user choice.
-- Be careful with specificity: user global styles override theme defaults.
-
-## WordPress 6.9 additions
-
-**Form element styling:**
-- Style text inputs and selects via `styles.elements` (e.g., `styles.elements.input`, `styles.elements.select`).
-- Supports border, color, outline, shadow, and spacing properties.
-- Note: Focus state styling is not yet available in 6.9.
-
-**Border radius presets:**
-- Define presets in `settings.border.radiusSizes` for visual selection in the border radius control.
-- Users can still enter custom values.
-
-```json
-{
-  "settings": {
-    "border": {
-      "radiusSizes": [
-        { "name": "Small", "slug": "small", "size": "4px" },
-        { "name": "Medium", "slug": "medium", "size": "8px" },
-        { "name": "Large", "slug": "large", "size": "16px" }
-      ]
-    }
-  }
-}
-```
-
-**Button pseudo-classes:**
-- Style Button block hover and focus states directly in theme.json.
-- No longer requires custom CSS for simple button state styling.
-
-References:
-
-- Border radius presets: https://make.wordpress.org/core/2025/11/12/theme-json-border-radius-presets-support-in-wordpress-6-9/
-- Form element styling: https://developer.wordpress.org/news/2025/11/how-wordpress-6-9-gives-forms-a-theme-json-makeover/

package/dist/cli/wp-files/agent-skills/wp-block-themes/scripts/detect_block_themes.mjs

@@ -1,117 +0,0 @@
-import fs from "node:fs";
-import path from "node:path";
-
-const DEFAULT_IGNORES = new Set([
-  ".git",
-  "node_modules",
-  "vendor",
-  "dist",
-  "build",
-  "coverage",
-  ".next",
-  ".turbo",
-]);
-
-function statSafe(p) {
-  try {
-    return fs.statSync(p);
-  } catch {
-    return null;
-  }
-}
-
-function existsDir(p) {
-  const st = statSafe(p);
-  return Boolean(st && st.isDirectory());
-}
-
-function readJsonSafe(p) {
-  try {
-    return JSON.parse(fs.readFileSync(p, "utf8"));
-  } catch {
-    return null;
-  }
-}
-
-function findFilesRecursive(repoRoot, predicate, { maxFiles = 6000, maxDepth = 10 } = {}) {
-  const results = [];
-  const queue = [{ dir: repoRoot, depth: 0 }];
-  let visited = 0;
-
-  while (queue.length > 0) {
-    const { dir, depth } = queue.shift();
-    if (depth > maxDepth) continue;
-
-    let entries;
-    try {
-      entries = fs.readdirSync(dir, { withFileTypes: true });
-    } catch {
-      continue;
-    }
-
-    for (const ent of entries) {
-      const fullPath = path.join(dir, ent.name);
-      if (ent.isDirectory()) {
-        if (DEFAULT_IGNORES.has(ent.name)) continue;
-        queue.push({ dir: fullPath, depth: depth + 1 });
-        continue;
-      }
-      if (!ent.isFile()) continue;
-
-      visited += 1;
-      if (visited > maxFiles) return { results, truncated: true };
-      if (predicate(fullPath)) results.push(fullPath);
-    }
-  }
-
-  return { results, truncated: false };
-}
-
-function summarizeTheme(repoRoot, themeJsonPath) {
-  const json = readJsonSafe(themeJsonPath);
-  const rel = path.relative(repoRoot, themeJsonPath);
-  const rootDir = path.dirname(rel);
-
-  const templatesDir = path.join(repoRoot, rootDir, "templates");
-  const partsDir = path.join(repoRoot, rootDir, "parts");
-  const patternsDir = path.join(repoRoot, rootDir, "patterns");
-  const stylesDir = path.join(repoRoot, rootDir, "styles");
-
-  const hasTemplates = existsDir(templatesDir);
-  const hasParts = existsDir(partsDir);
-
-  return {
-    themeRoot: rootDir,
-    themeJson: rel,
-    version: typeof json?.version === "number" ? json.version : null,
-    hasTemplates,
-    hasParts,
-    hasPatterns: existsDir(patternsDir),
-    hasStyles: existsDir(stylesDir),
-    isBlockTheme: hasTemplates || hasParts,
-  };
-}
-
-function main() {
-  const repoRoot = process.cwd();
-
-  const { results: themeJsonFiles, truncated } = findFilesRecursive(repoRoot, (p) => path.basename(p) === "theme.json", {
-    maxFiles: 8000,
-    maxDepth: 12,
-  });
-
-  const themes = themeJsonFiles.map((p) => summarizeTheme(repoRoot, p));
-
-  const report = {
-    tool: { name: "detect_block_themes", version: "0.1.0" },
-    repoRoot,
-    truncated,
-    count: themes.length,
-    themes,
-  };
-
-  process.stdout.write(`${JSON.stringify(report, null, 2)}\n`);
-}
-
-main();
-

package/dist/cli/wp-files/agent-skills/wp-plugin-development/SKILL.md

@@ -1,112 +0,0 @@
----
-name: wp-plugin-development
-description: "Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging."
-compatibility: "Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI."
----
-
-# WP Plugin Development
-
-## When to use
-
-Use this skill for plugin work such as:
-
-- creating or refactoring plugin structure (bootstrap, includes, namespaces/classes)
-- adding hooks/actions/filters
-- activation/deactivation/uninstall behavior and migrations
-- adding settings pages / options / admin UI (Settings API)
-- security fixes (nonces, capabilities, sanitization/escaping, SQL safety)
-- packaging a release (build artifacts, readme, assets)
-
-## Inputs required
-
-- Repo root + target plugin(s) (path to plugin main file if known).
-- Where this plugin runs: single site vs multisite; WP.com conventions if applicable.
-- Target WordPress + PHP versions (affects available APIs and placeholder support in `$wpdb->prepare()`).
-
-## Procedure
-
-### 0) Triage and locate plugin entrypoints
-
-1. Run triage:
-   - `node skills/wp-project-triage/scripts/detect_wp_project.mjs`
-2. Detect plugin headers (deterministic scan):
-   - `node skills/wp-plugin-development/scripts/detect_plugins.mjs`
-
-If this is a full site repo, pick the specific plugin under `wp-content/plugins/` or `mu-plugins/` before changing code.
-
-### 1) Follow a predictable architecture
-
-Guidelines:
-
-- Keep a single bootstrap (main plugin file with header).
-- Avoid heavy side effects at file load time; load on hooks.
-- Prefer a dedicated loader/class to register hooks.
-- Keep admin-only code behind `is_admin()` (or admin hooks) to reduce frontend overhead.
-
-See:
-- `references/structure.md`
-
-### 2) Hooks and lifecycle (activation/deactivation/uninstall)
-
-Activation hooks are fragile; follow guardrails:
-
-- register activation/deactivation hooks at top-level, not inside other hooks
-- flush rewrite rules only when needed and only after registering CPTs/rules
-- uninstall should be explicit and safe (`uninstall.php` or `register_uninstall_hook`)
-
-See:
-- `references/lifecycle.md`
-
-### 3) Settings and admin UI (Settings API)
-
-Prefer Settings API for options:
-
-- `register_setting()`, `add_settings_section()`, `add_settings_field()`
-- sanitize via `sanitize_callback`
-
-See:
-- `references/settings-api.md`
-
-### 4) Security baseline (always)
-
-Before shipping:
-
-- Validate/sanitize input early; escape output late.
-- Use nonces to prevent CSRF *and* capability checks for authorization.
-- Avoid directly trusting `$_POST` / `$_GET`; use `wp_unslash()` and specific keys.
-- Use `$wpdb->prepare()` for SQL; avoid building SQL with string concatenation.
-
-See:
-- `references/security.md`
-
-### 5) Data storage, cron, migrations (if needed)
-
-- Prefer options for small config; custom tables only if necessary.
-- For cron tasks, ensure idempotency and provide manual run paths (WP-CLI or admin).
-- For schema changes, write upgrade routines and store schema version.
-
-See:
-- `references/data-and-cron.md`
-
-## Verification
-
-- Plugin activates with no fatals/notices.
-- Settings save and read correctly (capability + nonce enforced).
-- Uninstall removes intended data (and nothing else).
-- Run repo lint/tests (PHPUnit/PHPCS if present) and any JS build steps if the plugin ships assets.
-
-## Failure modes / debugging
-
-- Activation hook not firing:
-  - hook registered incorrectly (not in main file scope), wrong main file path, or plugin is network-activated
-- Settings not saving:
-  - settings not registered, wrong option group, missing capability, nonce failure
-- Security regressions:
-  - nonce present but missing capability checks; or sanitized input not escaped on output
-
-See:
-- `references/debugging.md`
-
-## Escalation
-
-For canonical detail, consult the Plugin Handbook and security guidelines before inventing patterns.

package/dist/cli/wp-files/agent-skills/wp-plugin-development/references/data-and-cron.md

@@ -1,19 +0,0 @@
-# Data storage, cron, and upgrades
-
-Use this file when adding persistent storage, background jobs, or upgrade routines.
-
-## Data storage
-
-- Prefer Options API for small config/state.
-- Use custom tables only when needed; store schema version and provide upgrade paths.
-
-## Cron
-
-- Ensure tasks are idempotent (may run late or multiple times).
-- Provide a manual trigger path for debugging (WP-CLI or admin-only action).
-
-## Database safety note
-
-If using `$wpdb->prepare()`, avoid building queries with concatenated user input.
-Recent WordPress versions support identifier placeholders (`%i`) but you must not assume it exists without checking capabilities or target versions.
-

package/dist/cli/wp-files/agent-skills/wp-plugin-development/references/debugging.md

@@ -1,19 +0,0 @@
-# Debugging quick routes
-
-## Plugin doesn’t load / fatal errors
-
-- Confirm correct plugin main file and header.
-- Check PHP error logs and `WP_DEBUG_LOG`.
-- If the repo is a site repo, confirm you edited the correct plugin under `wp-content/plugins/`.
-
-## Activation hook surprises
-
-- Hooks must be registered at top-level.
-- Activation runs in a special context; avoid assuming other hooks already ran.
-
-## Settings not saving
-
-- Confirm `register_setting()` is called.
-- Confirm the option group matches the form.
-- Confirm capability checks and nonces.
-

package/dist/cli/wp-files/agent-skills/wp-plugin-development/references/lifecycle.md

@@ -1,33 +0,0 @@
-# Activation, deactivation, uninstall
-
-Use this file for lifecycle changes and data cleanup.
-
-## Activation / deactivation hooks
-
-- `register_activation_hook( __FILE__, 'callback' )`
-- `register_deactivation_hook( __FILE__, 'callback' )`
-
-Guardrails:
-
-- These hooks must be registered at top-level (not inside other hooks).
-- If you flush rewrite rules, ensure rules are registered first (often via a shared function called both on `init` and activation).
-
-Upstream reference:
-
-- https://developer.wordpress.org/plugins/plugin-basics/activation-deactivation-hooks/
-
-## Uninstall
-
-Preferred approaches:
-
-- `uninstall.php` (runs only on uninstall)
-- `register_uninstall_hook()`
-
-Guardrails:
-
-- Check `WP_UNINSTALL_PLUGIN` before running destructive cleanup.
-
-Upstream reference:
-
-- https://developer.wordpress.org/plugins/plugin-basics/uninstall-methods/
-

package/dist/cli/wp-files/agent-skills/wp-plugin-development/references/security.md

@@ -1,29 +0,0 @@
-# Security guardrails (plugin work)
-
-Use this file when making security fixes or when handling any input/output.
-
-## Nonces + permissions
-
-- Nonces help prevent CSRF, not authorization.
-- Always pair nonces with capability checks (`current_user_can()` or a more specific capability).
-
-Upstream reference:
-
-- https://developer.wordpress.org/apis/security/nonces/
-
-## Sanitization and escaping
-
-Golden rule:
-
-- sanitize/validate on input, escape on output.
-
-Practical rules:
-
-- never process the entire `$_POST` / `$_GET` array; read explicit keys
-- use `wp_unslash()` before sanitizing when needed
-- use prepared statements for SQL; avoid interpolating user input into queries
-
-Common review guidance:
-
-- https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/
-

package/dist/cli/wp-files/agent-skills/wp-plugin-development/references/settings-api.md

@@ -1,22 +0,0 @@
-# Settings API (admin options)
-
-Use this file when adding settings pages or storing user-configurable options.
-
-Core APIs:
-
-- `register_setting()`
-- `add_settings_section()`
-- `add_settings_field()`
-
-Upstream references:
-
-- Settings API overview: https://developer.wordpress.org/plugins/settings/settings-api/
-- Register settings: https://developer.wordpress.org/plugins/settings/registration/
-- Add settings fields: https://developer.wordpress.org/plugins/settings/settings-fields/
-
-Practical guardrails:
-
-- Use `sanitize_callback` to validate/sanitize data.
-- Use capability checks (commonly `manage_options`) for settings screens and saves.
-- Escape values on output (`esc_attr`, `esc_html`, etc.).
-

package/dist/cli/wp-files/agent-skills/wp-plugin-development/references/structure.md

@@ -1,16 +0,0 @@
-# Plugin structure and loading
-
-Use this file when introducing or refactoring a plugin architecture.
-
-## Core concepts
-
-- Main plugin file contains the plugin header and bootstraps the plugin.
-- Prefer predictable init:
-  - minimal boot file
-  - a loader/class that registers hooks
-  - admin-only code behind admin hooks
-
-Upstream reference:
-
-- https://developer.wordpress.org/plugins/plugin-basics/
-