flutter-duit-bdui

This skill acts as an expert Flutter BDUI integration engineer, providing specialized support for Duit and the flutter_duit package. It is designed for developers who need to implement server-driven UI architectures where application layouts and states are determined by JSON payloads from a backend. The skill guides you through the complex lifecycle of XDriver management, ensuring that remote and static layouts are rendered correctly while maintaining Flutter's strict widget ownership rules. It covers the entire development lifecycle, from initial configuration and HTTP/WebSocket transport setup to advanced tasks like implementing custom widgets, capability delegates, and handling complex event streams.

• API version-aware implementation: Detects installed flutter_duit version to provide accurate, non-deprecated code patterns for XDriver and DuitViewHost.

• Flexible rendering modes: Instructions for XDriver.remote for server-driven screens and XDriver.static for local JSON fixtures or offline testing.

• Custom capability delegates: Deep technical guidance on extending the framework for logging, native module interaction, scripting, custom transport, and focus management.

• Lifecycle management: Expert advice on registering components, cleaning up resources, and managing driver state within StatefulWidget or appropriate architectural patterns.

• Troubleshooting and debugging: Systematic approaches to resolving rendering failures, theme inconsistencies, initialization errors, and memory leaks.

• Requires prior knowledge of the project's flutter_duit version constraints as defined in pubspec.yaml.

• Prevents common pitfalls like registering custom widgets after initial layout rendering or misusing global drivers.

• Prioritizes validation steps such as flutter analyze, flutter test, and formatting to ensure code stability.

• Explicitly warns against inventing server JSON schema or action payloads without inspecting existing backend contracts.

• Provides a clear fallback strategy: stops and requests more context if the API version cannot be verified, preventing the generation of speculative, non-compiling code.