Domain Radio Rules

Validate radio broadcasting entity hierarchies and business rules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lwilly3/api.audace --skill domain-radio-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Domain Radio Rules
Source: https://github.com/lwilly3/api.audace/tree/main/.github/skills/domain-radio-rules
Command: npx skills add https://github.com/lwilly3/api.audace --skill domain-radio-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all development strictly adheres to the established hierarchy, relationships, and business constraints specific to radio broadcasting operations, preventing common errors and maintaining data integrity.

Core Features & Use Cases

  • Enforces Hierarchy: Guarantees the correct EmissionShowSegment structure.
  • Validates Relationships: Ensures entities like Guests are linked to Segments, not Shows directly.
  • Enforces Business Rules: Checks for valid statuses, segment types, and duration constraints.
  • Use Case: When developing new features for show scheduling, this Skill acts as a guardian, automatically flagging any attempts to create a segment without a parent show or assign a presenter as a guest, thus preventing logical inconsistencies.

Quick Start

Ensure all new show segments are correctly associated with a parent show and have a valid type.

Frequently Asked Questions about Domain Radio Rules

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

FAQPage Schema
How do I validate radio broadcasting domain logic and entity hierarchy in my API?

To validate radio broadcasting domain logic, you need to enforce a strict Emission, Show, and Segment hierarchy. This ensures data integrity by checking entity relationships, correct many-to-many mappings, and predefined status enumerations.

What business rules are required for radio show scheduling and segment validation?

Radio show scheduling validation requires checking segment types and duration constraints, ensuring segments link to parent shows, and preventing guests from linking directly to shows to maintain logical consistency.

How do I prevent logical inconsistencies when linking guests to radio segments?

To prevent logical inconsistencies when linking guests, enforce rules so guests are linked only to Segments and not directly to Shows. This validates the correct many-to-many relationships within the radio domain.

Can I enforce predefined status and type enumerations for radio media management?

Yes, you can enforce predefined status and type enumerations for radio media management. The Skill checks data against established business constraints to guarantee adherence to valid statuses and segment types.

Why does my radio API data validation fail when creating a segment without a parent show?

Radio API data validation fails because creating a segment without a parent show breaks the strict Emission → Show → Segment hierarchy. Enforcing this structure prevents common errors and maintains data integrity.