skills.rest
BrainDriveAI
BrainDriveAIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

plugin-anatomy

Describe BrainDrive plugin layers, module federation, and lifecycle management.

Updated Feb 1, 2026
Search Tags:#architecture#frontend#backend#plugin#lifecycle#module-federation#braindrive
One-click install
npx skills add https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode --skill plugin-anatomy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-anatomy
Source: https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode/tree/main/.claude/skills/plugin-anatomy
Command: npx skills add https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode --skill plugin-anatomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understanding BrainDrive plugin structure and architecture helps teams plan, discuss, and communicate plugin designs before implementation.

Core Features & Use Cases

  • Provides a clear map of BrainDrive's plugin layers (Frontend, Backend, and Metadata) and how they interact.
  • Describes Module Federation usage, lifecycle management, and plugin registration conventions to prevent collisions.
  • Includes guidance on typical plugin layouts, file naming, and integration points for settings, UI, and APIs.

Quick Start

Inspect this skill to understand core plugin anatomy and apply the architecture concepts to your own plugin project.

Frequently Asked Questions about plugin-anatomy

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

FAQPage Schema
What is the architecture of a BrainDrive plugin?▼

BrainDrive plugin architecture consists of three layers: Frontend, Backend, and Metadata. It defines how components interact, manage lifecycle, and register to prevent collisions.

How do I structure my BrainDrive plugin folders and files?▼

Structure your BrainDrive plugin using modular folder conventions that separate frontend, backend, and metadata layers. This layout organizes integration points for settings, UI, and APIs.

Does BrainDrive use Module Federation for plugin lifecycle management?▼

Yes, BrainDrive uses Module Federation for plugin loading and lifecycle management. It handles dynamic component integration and ensures proper plugin registration conventions.

How do I separate frontend and backend boundaries in my plugin?▼

Separate frontend and backend boundaries by defining distinct integration points within the plugin architecture. Ensure the frontend manages UI components while the backend handles API logic.

What metadata is required for BrainDrive plugin registration?▼

BrainDrive plugin registration requires a compliant metadata model. This model defines the plugin identity, capabilities, and integration points to prevent naming collisions across the system.

Can I plan my plugin structure before writing code?▼

Yes, you can plan your plugin structure before implementation by outlining the three plugin layers, metadata model, and frontend/backend boundaries. This prevents architectural collisions.

Related Skills

Explore More Software Engineering Skills→
4tikhonov4tikhonov
3

project-init

Initialize a FIRE project by detecting workspace type and generating standards templates.

Community
Basic
mjwestcottmjwestcott
7

scaffold

Scaffold fullstack Python + React or Rust CLI projects from boilerplates.

Community
Intermediate
erxeserxes
4.1k

module-federation-expose

Manage Module Federation exposes in erxes frontend plugin configuration files.

Official
Advanced
msichtermanmsichterman

vercel-react-native-skills

Apply React Native and Expo performance best practices to components, lists, animations, and images.

Community
Advanced