wagtail-builder

Apply Wagtail CMS best practices for page modeling, headless API configuration, and code review.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/H2OSLabs/ssd --skill wagtail-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wagtail-builder
Source: https://github.com/H2OSLabs/ssd/tree/main/.claude/skills/wagtail-builder
Command: npx skills add https://github.com/H2OSLabs/ssd --skill wagtail-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill codifies Wagtail development best practices into a reusable guide, reducing rework and ensuring consistent architecture across projects.

Core Features & Use Cases

  • Policy-driven guidance for Page/Snippet modeling, Headless API setup, and StreamField organization.
  • Reusable rules & references covering RichText serialization, indexing, N+1 prevention, i18n, and translation workflows.
  • Phase-driven workflow (RED-GREEN-REFACTOR) inspired by Test-Driven Development for Skills.

Quick Start

Start by reviewing SKILL.md to understand the Red Flags, Core Decisions, and the Quick Reference. Then apply rules from rules/headless-api.md and rules/data-models.md during Wagtail project setup and reviews.

Frequently Asked Questions about wagtail-builder

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

FAQPage Schema
What are the best practices for Wagtail CMS page and snippet data modeling?

Standardize Wagtail CMS development by applying reusable references for page and snippet modeling, enforcing frontmatter entries, and defining anti-patterns to guide safe, scalable architecture across projects.

How do I configure a headless API in Wagtail for RichText serialization?

Configure Wagtail headless APIs by applying enforced rules for API serialization and indexing, ensuring RichText fields are properly structured for frontend consumption without N+1 query issues.

How do I organize StreamField blocks in Wagtail to avoid N+1 query problems?

Organize Wagtail StreamField components by applying reference rules for N+1 prevention and indexing, ensuring scalable data retrieval and efficient query execution across complex page structures.

Does Wagtail CMS support internationalization and translation workflows out of the box?

Wagtail CMS supports internationalization (i18n) by applying consolidated translation workflow rules and best practices, ensuring proper multilingual content configuration and scalable architecture across projects.

What is the best way to standardize Wagtail CMS code reviews across projects?

Standardize Wagtail CMS code reviews by implementing a phase-driven RED-GREEN-REFACTOR workflow and applying reusable references to enforce frontmatter entries, serialization rules, and anti-patterns.

When should I avoid using StreamField in Wagtail CMS development?

Avoid using Wagtail StreamField when your data modeling violates documented anti-patterns, specifically when API serialization rules cannot be met or when structures risk N+1 query prevention limits.