develop-opencode-plugins

OpenCode plugin development involves building and maintaining platform references and code within agentic/src/modules. It consolidates architecture patterns, tooling references, and integration guidance for consistent updates across the ecosystem.

To update or remove code in agentic/src/modules, apply OpenCode plugin development patterns with built-in best practices and safety checks. Centralized architecture references guide modifications while maintaining platform stability and consistency.

You need OpenCode plugin architecture references when onboarding engineers to platform development, performing wide refactors in agentic/src/modules, or integrating new tooling patterns within the agentic ecosystem.

The best way to structure OpenCode plugins for refactors is to follow consolidated integration patterns and architecture context. This ensures maintainability and consistent code organization across agentic/src/modules during updates.

Yes, you can use these OpenCode plugin development references for onboarding. They document architecture context, setup considerations, and best practices that help new engineers understand and contribute to agentic/src/modules effectively.

Updating code in agentic/src/modules without architecture references risks inconsistent modifications and broken integration patterns. Scattered documentation makes maintaining OpenCode plugins difficult and increases the chance of errors during refactoring.