skills.rest
delta-and-beta
delta-and-betaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architect-catalog-design

Outline data models, field schemas, and sync trade-offs for Braze catalogs.

Updated Apr 6, 2026
Search Tags:#architecture#data-modeling#schema-design#catalogs#braze#sync-async
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-catalog-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-catalog-design
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/architect-catalog-design
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-catalog-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Catalog design challenges are addressed by providing structured patterns for data models, field schemas, and trade-offs for sync/async operations in Braze catalogs.

Core Features & Use Cases

  • Data modeling guidance for catalogs: item structure, field types, and schema evolution.
  • Sync/async design patterns: recommendations for when to use immediate vs eventual consistency in catalog operations.
  • Selection design and personalization: guidance on building catalog selections and integrating with messages.

Quick Start

Provide a catalog design scenario and request a recommended data model and trade-offs.

Frequently Asked Questions about architect-catalog-design

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

FAQPage Schema
How do I design a data model for Braze catalogs?▼

Design Braze catalogs by defining item structures, field types, and item IDs to support personalization. This involves structuring data models and field schemas that align with your campaign requirements and selection design.

What's the best way to handle sync vs async data flows in Braze catalogs?▼

Handle sync vs async data flows by evaluating consistency needs for your catalog operations. Use sync for immediate updates during campaigns and async for eventual consistency when processing bulk data or background synchronization.

When do I need schema evolution for Braze catalog selections?▼

Schema evolution is needed when modifying field types or adding items to existing Braze catalog selections. It ensures personalization campaigns continue functioning correctly as your data model expands.

Can I use Braze catalogs for both campaigns and personalization selections?▼

Braze catalogs support both campaigns and personalization through selection design. You define data models with specific field schemas and item IDs that integrate directly with messages across various use cases.

What are the limitations of sync vs async operations in Braze catalog design?▼

Sync operations provide immediate consistency but may impact performance, while async operations offer eventual consistency suitable for bulk updates. Limitations depend on your API usage patterns and data modeling requirements.

Related Skills

Explore More Software Engineering Skills→
delta-and-betadelta-and-beta

analyst-data-objects

Provide Braze API data object schemas, field constraints, and example payloads.

Community
Advanced
delta-and-betadelta-and-beta

architect-ecommerce

Design scalable e-commerce to Braze integration architectures with canonical event ownership and product ID namespaces.

Community
Advanced
delta-and-betadelta-and-beta

strategist-catalog-strategy

Design catalog-driven personalization strategies using CSV or API imports, Liquid templates, and catalog triggers.

Community
Intermediate
delta-and-betadelta-and-beta

architect-data-pipelines

Design data pipeline architectures for Braze Decisioning Studio with governance and reverse ETL.

Community
Advanced