superpowers-sage:modeling

Name: superpowers-sage:modeling
Availability: InStock
Author: codigodoleo

Classify Sage/Bedrock content into static fields, CPTs, options pages, or relationships.

13|Updated Mar 19, 2026

Search Tags:#architecture #wordpress #content-modeling #acf #sage #cpt #poet

Ready to run

npx skills add https://github.com/codigodoleo/superpowers-sage --skill superpowers-sage-modeling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers-sage:modeling
Source: https://github.com/codigodoleo/superpowers-sage/tree/main/skills/modeling
Command: npx skills add https://github.com/codigodoleo/superpowers-sage --skill superpowers-sage-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content modeling for Sage/Bedrock — classify as CPT ACF fields Blade component Livewire component or Options Page, Poet CPT configuration, ACF Composer fields vs GUI, relational content, static vs dynamic, content architecture decisions, config/poet.php, modeling before building, content classification matrix

Core Features & Use Cases

Provide a clear framework to decide when to use static fields, dynamic CPTs, Options Pages, or relational fields in Sage/Bedrock projects.
Include guidance on Poet for CPTs, ACF field groups, and data relationships to ensure scalable architectures.
Include a decision checklist and a portable output format to communicate the modeling plan to teams and automation scripts.

Quick Start

Identify content blocks and components in a Sage/Bedrock project and decide the appropriate data model before implementation.

Frequently Asked Questions about superpowers-sage:modeling

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

FAQPage Schema

How do I plan content modeling for a Sage or Bedrock WordPress project?▼

Plan content modeling by classifying Sage or Bedrock content into static fields, dynamic CPTs, options pages, or relationships using a decision matrix to ensure scalable architecture and maintainability before implementation.

When should I use ACF fields versus Poet CPTs for WordPress content architecture?▼

Choose ACF fields for static or component-level data and Poet CPTs for dynamic, repeatable content structures. This classification ensures maintainable architecture by correctly matching data persistence models to content needs.

Does this content modeling approach work with ACF Composer and Blade components?▼

Yes, the approach integrates with ACF for fields and Poet for CPT configuration, guiding decisions between ACF Composer fields versus GUI and how to appropriately model data for Blade components within Sage projects.

What is the best way to structure relational content in a Bedrock project?▼

Structure relational content by applying the content classification framework, deciding between static fields, dynamic CPTs, or relational fields to establish scalable data relationships before building components.

How do I configure config/poet.php before building custom post types?▼

Configure Poet CPTs by planning the content architecture first, using the provided decision checklist to define dynamic content needs, then applying that modeling plan directly to your config/poet.php file.