create-plugin

Scaffold new plugins from a preset template with dependency and distribution rules.

3|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/NextSpark-js/nextspark --skill create-plugin-nextspark-js
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plugin
Source: https://github.com/NextSpark-js/nextspark/tree/main/.claude/skills/create-plugin
Command: npx skills add https://github.com/NextSpark-js/nextspark --skill create-plugin-nextspark-js

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of new plugins by providing a standardized template and enforcing critical dependency management and distribution rules, preventing common errors and ensuring consistency.

Core Features & Use Cases

  • Automated Scaffolding: Generates a new plugin directory with all necessary files and structure based on complexity.
  • Dependency Management Enforcement: Guides users to correctly declare dependencies, distinguishing between core and plugin-specific ones.
  • Distribution Rules: Clarifies how plugins are distributed (NPM packages) versus how their code is used in user projects (copied to contents/plugins/).
  • Use Case: A developer needs to add a new payment gateway integration to the SaaS platform. They use this Skill to quickly create the plugin structure, ensuring all dependencies are correctly managed and the plugin adheres to the platform's architecture.

Quick Start

Use the create-plugin skill to scaffold a new plugin named 'analytics' with service complexity.

Frequently Asked Questions about create-plugin

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

FAQPage Schema
How do I scaffold a new plugin in a monorepo?

Scaffolding a new plugin in a monorepo involves generating a standardized directory structure from a preset template, automating configuration and registration within user projects. This enforces mandatory dependency management and distribution rules to ensure architectural consistency.

What is the correct way to manage dependencies when developing a plugin?

Managing dependencies during plugin development requires distinguishing between core dependencies and plugin-specific ones. Enforcing correct dependency declaration prevents common errors and ensures that the plugin integrates seamlessly without causing version conflicts in the monorepo.

How are plugins distributed via NPM versus how they are used in user projects?

Plugins are distributed as NPM packages, but their code is copied directly into the `contents/plugins/` directory of user projects. This distribution model ensures that the plugin code is available locally within the project environment after installation.

Can I generate a plugin with specific complexity levels using a CLI?

Yes, you can generate a plugin with specific complexity levels using a CLI. The scaffolding process allows you to specify complexity, such as creating a new plugin named 'analytics' with service complexity, tailoring the generated files to your needs.

Why do I need a standardized template for creating new plugins?

A standardized template for creating new plugins prevents common errors by enforcing critical dependency management and distribution rules. It ensures consistency across the platform, streamlining the addition of new features like payment gateway integrations into a SaaS platform.