common-conventions

What problem does it solve?

This Skill prevents inconsistent architecture, command-line usage, module placement, and resource-system changes across Edgion’s multiple binaries by providing shared conventions in one place.

Core Features & Use Cases

• Project-wide architecture overview: Understand how controller, gateway, and federation components work together at a high level.
• Unified CLI, config, and startup conventions: Follow consistent flag names, working-directory layout, logging initialization, and signal/shutdown expectations.
• Core module layering rules: Place new code under the correct bin-owned directories and avoid common directory/ownership anti-patterns.
• Resource system conventions: Follow the define_resources! approach, ResourceMeta/ResourceKind patterns, and how pre-parse builds runtime structures.
• Grouped-list design contract: Safely extend *_groups fields with schema, rolling-upgrade safety, controller resolution behavior, gateway logging rules, and required test coverage.

Quick Start

Read this Skill first, then follow the grouped-list pattern when extending any plugin or resource that introduces new *_groups fields.