fse-block-theme-development

Codify WordPress FSE block themes with design tokens, templates, and patterns into reproducible workflows.

16|5|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/PMDevSolutions/Flavian --skill fse-block-theme-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fse-block-theme-development
Source: https://github.com/PMDevSolutions/Flavian/tree/main/.claude/skills/fse-block-theme-development
Command: npx skills add https://github.com/PMDevSolutions/Flavian --skill fse-block-theme-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FSE Block Theme Development provides a structured approach for building WordPress Full Site Editing themes, ensuring that design systems live in theme.json and templates drive layout rather than hardcoded styles.

Core Features & Use Cases

  • Establish a design-system-first workflow for FSE themes, including theme.json, templates, and template parts.
  • Create or migrate to block themes that leverage tokens for colors, typography, and spacing, enabling variations and accessibility.
  • Use cases include creating new themes from scratch, refactoring classic themes, and iterating on style variations across multiple templates and blocks.

Quick Start

Create a new theme under themes/theme-name, then begin with a minimal theme.json and a templates/index.html as the ultimate fallback.

Frequently Asked Questions about fse-block-theme-development

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

FAQPage Schema
How do I build a WordPress block theme using theme.json design tokens?

Build a block theme by establishing a design-system-first workflow that codifies colors, typography, and spacing into theme.json tokens. This approach drives layout through templates and template parts rather than hardcoding styles, ensuring reproducible styling and accessibility across the site.

What is the minimal file structure required for an FSE block theme?

An FSE block theme requires a minimal root structure under themes/theme-name/ containing style.css, theme.json, and templates/index.html. The index.html file serves as the ultimate fallback template, while theme.json manages the design tokens for the entire theme.

How do I migrate a classic WordPress theme to Full Site Editing?

Migrate a classic theme to Full Site Editing by refactoring hardcoded styles into theme.json design tokens and converting traditional PHP templates into block-based templates and template parts. This establishes a token-driven styling workflow that enables style variations and accessibility compliance.

Can I create style variations across multiple templates and blocks in FSE?

Create style variations across multiple templates and blocks by leveraging token-driven styling within theme.json. By codifying design tokens for colors, typography, and spacing, you can iterate on style variations globally without hardcoding values into individual templates.

Why should I use design tokens instead of hardcoded styles in block patterns?

Use design tokens instead of hardcoded styles to ensure accessibility and maintainability across block patterns. Codifying values into theme.json creates a reproducible workflow that prevents style duplication, enables easy style variations, and enforces a consistent design system throughout the theme.

FSE block theme development not working with hardcoded CSS values?

FSE block theme development enforces token-driven styling to avoid hardcoding CSS values. When styles are hardcoded directly in templates or block patterns, the theme.json design system is bypassed, breaking style variations and reproducibility across the site.