new-plugin

Scaffold a new grid plugin with manifest, tests, and documentation.

48|4|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/OysteinAmundsen/toolbox --skill new-plugin-oysteinamundsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-plugin
Source: https://github.com/OysteinAmundsen/toolbox/tree/main/.github/skills/new-plugin
Command: npx skills add https://github.com/OysteinAmundsen/toolbox --skill new-plugin-oysteinamundsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a standardized blueprint to rapidly add a new grid plugin with a canonical structure and integrated docs.

Core Features & Use Cases

  • Scaffolds the plugin directory under libs/grid/src/lib/plugins/<plugin-name>/ with a complete file set and barrel exports.
  • Enforces a consistent manifest, tests, demos, and documentation workflow to ensure quality and maintainability.
  • Enables onboarding of new plugin authors by providing a repeatable, drop-in template for production-grade plugins.

Quick Start

Follow the outlined scaffold to create libs/grid/src/lib/plugins/<plugin-name>/ and implement the plugin with tests and docs.

Frequently Asked Questions about new-plugin

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

FAQPage Schema
How do I scaffold a new grid plugin directory with TypeScript?

A grid plugin scaffold requires a manifest, unit tests, accessibility considerations, and documentation to ensure production quality. Enforcing this workflow maintains plugin consistency and maintainability across the grid system.

Does scaffolding a grid plugin include unit tests and documentation?

Yes, scaffolding a grid plugin enforces unit tests, accessibility considerations, and documentation as part of the workflow. This ensures production-grade quality and maintainability for the new plugin.

What files are required when adding a new grid plugin?

Required files for a new grid plugin include barrel exports, a manifest with metadata, unit tests, and documentation. The scaffold places these under libs/grid/src/lib/plugins/<plugin-name>/ with integration steps across libs/grid and docs.

Why do I need a manifest and accessibility checks for my grid plugin?

A manifest and accessibility checks are needed to enforce consistent metadata and quality standards across grid plugins. This workflow ensures your plugin meets production requirements and integrates properly with the grid system.