builder-payload-smith

Maintain Discord API payload builders with validation and serialization rules.

1.1k|250|Updated Aug 12, 2015
One-click install
npx skills add https://github.com/discord-php/DiscordPHP --skill builder-payload-smith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: builder-payload-smith
Source: https://github.com/discord-php/DiscordPHP/tree/main/.agents/skills/builder-payload-smith
Command: npx skills add https://github.com/discord-php/DiscordPHP --skill builder-payload-smith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain Builder classes — outbound payload construction, validation, serialization, component handling, and fromPart symmetry. Use when changing Builders or outbound Discord API payloads.

Core Features & Use Cases

  • Ensure builders consistently produce valid Discord API payloads.
  • Enforce validation rules, serialization pathways, and component handling
  • Provide symmetry with in-memory parts via fromPart() and repository integration when applicable.

Quick Start

Load the builder-payload-smith skill when editing outbound payload builders to preserve correctness and reduce regression risk.

Frequently Asked Questions about builder-payload-smith

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

FAQPage Schema
How do I validate outbound Discord API payloads in PHP to prevent invalid requests?

Discord API payload validation is enforced by applying strict serialization rules and contract guidelines to builder classes, ensuring outbound payloads remain stable and valid before dispatch.

What is fromPart symmetry and why does it matter for Discord payload builders?

fromPart symmetry ensures outbound payload builders mirror in-memory repository parts, preventing mismatches between constructed payloads and internal state during Discord API interactions.

How do I maintain Discord builder classes when modifying outbound payload shapes?

Load the builder-payload-smith skill when editing builders to enforce validation rules, serialization pathways, and component handling, preserving payload correctness and reducing regression risk.

Does this approach to Discord payload serialization work with messages, components, and interactions?

Yes, the builder consistency rules cover messages, components, and interactions, enforcing core contract guidelines across all outbound Discord API payload shapes to prevent invalid data.

What's the best way to prevent regressions when changing Discord API payload structures?

Prevent regressions by applying structured validation and component handling rules to builder modifications, ensuring fromPart symmetry and serialization consistency across all outbound payloads.