design-patterns

To apply design patterns in BK-CI, use factory, strategy, observer, decorator, and template method patterns provided by this Skill. It documents practical code examples across pipelines, stores, and connectors to guide consistent coding practices and architectures.

You need the factory or strategy pattern in a Kotlin pipeline module when handling complex condition branches or plugin-based task creation. Replacing branches with these patterns achieves higher maintainability and modular decoupling for scalable code.

Yes, you need familiarity with Kotlin or Java to use BK-CI design patterns. The Skill requires understanding these languages and access to project code samples to properly apply reusable patterns across various modules.

The best way to decouple modules using observer patterns in BK-CI is implementing event listeners and post-processors. This Skill provides typical scenario references for event monitoring to achieve effective modular decoupling.

To implement plugin-based task creation, use the task factory and code repository factory patterns documented in this Skill. It provides practical BK-CI code examples to help developers quickly reuse and extend factories across modules.

BK-CI architecture suffers from poor maintainability when complex condition branches are hardcoded. Applying prescribed design patterns like strategy and observer replaces rigid branches with reusable, extensible structures, directly improving code maintainability and team collaboration.