eaa-design-communication-patterns

Standardize design documentation by loading centralized templates and schemas that enforce consistent data formats and project-wide standards. This prevents duplication and ensures all architecture documents adhere to uniform structures.

Shared utilities for preventing code duplication include reusable scripts, constants, and inter-agent messaging patterns. These resources centralize common logic so agents import standardized components like status codes instead of recreating them.

Yes, you can validate design documents using included shared schemas. The skill provides schema validation capabilities to ensure architecture and requirements documents conform to standardized data formats before processing.

You import shared constants for validation logic by accessing centralized resources provided for inter-agent messaging and standardized tasks. This allows your skill to reference common status codes and constants without hardcoding them.

No, this skill requires no external dependencies. It operates independently to provide shared utilities, templates, constants, and schemas directly through its internal scripts and references components.

You should avoid centralized templates for design patterns when your project requires highly customized documentation formats deviating from standardized architectures, or when inter-agent messaging standardization is not a priority.