superpowers-sage:wp-block-native

Build native Gutenberg blocks in Sage projects with block.json and Vite assets.

13|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/codigodoleo/superpowers-sage --skill superpowers-sage-wp-block-native
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-sage:wp-block-native
Source: https://github.com/codigodoleo/superpowers-sage/tree/main/skills/wp-block-native
Command: npx skills add https://github.com/codigodoleo/superpowers-sage --skill superpowers-sage-wp-block-native

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Native Gutenberg blocks in Sage projects without relying on ACF Composer, with a complete workflow from block.json to editor and dynamic rendering.

Core Features & Use Cases

  • Native blocks with block.json, edit.js, save.js, inner blocks, server-side render, and Vite-based asset pipeline in Sage.
  • Use cases include building complex editor UIs, transforms, variations, and dynamic content in WordPress with Sage.

Quick Start

Create a new Sage native block by wiring block.json, editor.js, and a PHP render, then load it in the editor to preview.

Frequently Asked Questions about superpowers-sage:wp-block-native

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

FAQPage Schema
How do I build native Gutenberg blocks in a Sage theme without ACF Composer?

Native Gutenberg blocks in Sage are built by wiring block.json with apiVersion 3, editor and view scripts, a Vite-based asset pipeline, and dynamic PHP rendering without relying on ACF Composer.

Does Sage support InnerBlocks and server-side rendering for native WordPress blocks?

Sage supports native Gutenberg blocks requiring InnerBlocks, transforms, variations, and server-side rendering through a Vite-based asset pipeline and dynamic PHP rendering.

How do I set up a Vite asset pipeline for WordPress block editor scripts in Sage?

Setting up a Vite asset pipeline for Sage native blocks involves configuring editor and view scripts within block.json and connecting them to the Vite build process for the WordPress editor.

What is the best way to create dynamic content blocks in WordPress without ACF?

Creating dynamic content blocks without ACF is achieved by building native Gutenberg blocks in Sage using block.json, server-side rendering, and dynamic PHP rendering templates.

Can I use block.json apiVersion 3 with InnerBlocks in Sage projects?

Block.json apiVersion 3 works with InnerBlocks in Sage projects by wiring native Gutenberg blocks and configuring the Vite-based asset pipeline for editor and view scripts.

Why use native Gutenberg blocks over ACF Composer for complex editor UIs in Sage?

Native Gutenberg blocks provide complex editor UIs, transforms, and variations in Sage without ACF Composer dependencies by utilizing block.json, InnerBlocks, and server-side rendering.