orbit-fse-test

Validate theme.json structure and template hierarchy against WordPress Full-Site-Editing standards.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-fse-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orbit-fse-test
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-fse-test
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-fse-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify compatibility issues with Full-Site-Editing (FSE) for WordPress plugins or themes, ensuring they work seamlessly with the Site Editor.

Core Features & Use Cases

  • Theme.json Validation: Checks theme.json schema version and formatting against WordPress standards.
  • Template and Style Variations: Ensures templates and style variations are properly structured and compatible.
  • Block Locking: Verifies that critical parts of the site remain locked to prevent accidental changes in the Site Editor.
  • Use Case: For plugin and theme developers aiming to support FSE, this Skill provides essential checks to avoid breaking the editing experience.

Quick Start

Audit your plugin or theme for FSE compatibility using the command: claude "/orbit-fse-test Audit ~/plugins/my-plugin for FSE compatibility."

Frequently Asked Questions about orbit-fse-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my WordPress theme is compatible with Full-Site-Editing?

To check Full-Site-Editing compatibility, validate your theme.json structure and template hierarchy against WordPress FSE standards. This ensures your theme works seamlessly with the Site Editor without breaking the editing experience.

What does theme.json validation do for WordPress Site Editor compatibility?

Theme.json validation checks your schema version and formatting against WordPress standards. This verification ensures your configuration properly supports Full-Site-Editing features and Site Editor integration without structural conflicts.

How do I audit a plugin for FSE compatibility in WordPress?

You audit a plugin for FSE compatibility by checking its theme.json structure, template variations, and block locking rules against WordPress Full-Site-Editing standards. This prevents accidental changes to critical site parts in the Site Editor.

Do I need a PHP environment to test Full-Site-Editing compatibility?

Yes, you need a PHP and WordPress environment to execute Full-Site-Editing compatibility checks. The validation process uses the WordPress theme API to verify template hierarchy and theme.json structure against FSE standards.

Why does my WordPress template break in the Site Editor?

Templates break in the Site Editor when their structure does not match WordPress Full-Site-Editing standards. Validating template variations and ensuring critical blocks remain locked prevents structural conflicts and accidental editing changes.

Can I verify block locking rules for Full-Site-Editing compatibility?

Yes, you can verify block locking rules to ensure critical parts of your site remain locked. This Full-Site-Editing compatibility check prevents accidental changes to essential template areas within the WordPress Site Editor.