Problem Statement

The plugins/ directory currently lacks a standardized folder structure. Each plugin has grown its own layout organically, making it hard for contributors to navigate, add new plugins consistently, or maintain existing ones. There are no enforced conventions for where src/"kinds", tests, or assets should live within a plugin folder.

Proposed Solution

Define and document a standardized folder architecture for the plugins/ directory. Refactor all existing plugins to conform to it.

Use Cases

• Use case 1: A new contributor creating a plugin follows the documented structure without reading other plugins for patterns.
• Use case 2: CI or tooling can reliably locate tests, headers, and xmake targets using predictable paths.

Impact

• No changes to engine behavior.
• Include path changes in existing plugins may require updates in consuming code.

Additional Context

N/A

Related Issues

• N/A