validation-checklist

To validate a BrainDrive plugin before publishing, run a comprehensive checklist covering pre-build structure, manifest correctness, dependencies, and post-build packaging readiness across CLI and webpack configurations.

Common BrainDrive plugin build failure modes involve incorrect file presence, manifest errors, and packaging issues. You can fix them by following actionable remediation steps provided during post-build and runtime validation checks.

Verifying your plugin's SKILL.md frontmatter requires ensuring the file contains well-formed name and description fields. Pre-build validation checks confirm correct file presence and expected workflow across your project structure.

Yes, BrainDrive plugin validation covers both webpack and CLI configurations. The checklist enforces correct file presence and validates build readiness across these environments to ensure proper plugin lifecycle management.

You need to run runtime validation checks for a BrainDrive plugin after completing post-build packaging steps. This verifies plugin readiness and debugging capabilities directly within the BrainDrive environment before final publishing.

The best way to debug BrainDrive plugin lifecycle and dependency issues is applying a structured validation checklist that diagnoses failure modes and provides actionable remediation steps across pre-build and runtime phases.