manifest-rules

Enforce BrainDrive plugin manifest, naming, and version rules across package.json and lifecycle_manager.py.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode --skill manifest-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manifest-rules
Source: https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode/tree/main/.claude/skills/manifest-rules
Command: npx skills add https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode --skill manifest-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BrainDrive plugin manifest and naming rules govern the validation of package.json fields, plugin naming conventions, and lifecycle consistency to ensure safe loading and predictable plugin behavior.

Core Features & Use Cases

  • Enforces kebab-case names in package.json and matching slug in lifecycle_manager.py
  • Ensures scope and version fields align across package.json, webpack.config.js, and the lifecycle data dictionary
  • Guides users through consistent naming, category alignment, and icon selection to prevent load-time errors

Quick Start

Validate your plugin project against the manifest and naming rules to ensure consistency.

Frequently Asked Questions about manifest-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate package.json fields for a BrainDrive plugin?

Plugin manifest validation checks package.json fields, enforces kebab-case names, verifies PascalCase slugs in lifecycle_manager.py, and ensures scope and version consistency across webpack.config.js and bundle_location to prevent load-time errors.

What naming conventions does a BrainDrive plugin manifest require?

A BrainDrive plugin manifest requires kebab-case names in package.json and matching PascalCase slugs in lifecycle_manager.py, ensuring scope consistency across webpack.config.js and bundle_location to prevent load-time errors.

How do I fix lifecycle_manager.py slug mismatches with package.json?

Fix slug mismatches by updating the lifecycle data dictionary in lifecycle_manager.py to use a PascalCase slug that aligns with the kebab-case plugin name in package.json, satisfying cross-file validation criteria.

Why does my BrainDrive plugin fail to load with scope inconsistencies?

Your plugin fails to load due to scope and version misalignment across package.json, webpack.config.js, and the lifecycle data dictionary, causing deviations that trigger load-time errors during cross-file validation.

Can I use different version numbers in package.json and webpack.config.js for plugins?

No, version fields must align across package.json, webpack.config.js, and the lifecycle data dictionary to detect deviations and prevent load-time errors.

What is the best way to ensure category alignment and icon selection for a plugin?

Validate your plugin project against the manifest and naming rules to ensure consistent category alignment, icon selection, and naming, preventing load-time errors and ensuring predictable plugin behavior.