operating-script

What problem does it solve?

This Skill removes the friction and inconsistency of manually writing and registering Gulp operational scripts by providing a standard template, naming conventions, and required registration steps to ensure tasks are discoverable and maintainable across environments.

Core Features & Use Cases

• Standardized Templates: Provides an ESM-based script skeleton with sections for configuration, helpers, JSDoc, and required help tasks.
• Naming & Task Conventions: Enforces file and Gulp task naming patterns ({category}_{env}.js and category:env:action) so teams maintain predictable task names.
• Integration Steps: Guides updating gulpfile.js, .env.example, and reusing shared helper modules to register and test new tasks.
• Use Case: When adding a staging deploy pipeline, scaffold deploy_stg.js with provision and deploy tasks, hook it into gulpfile.js, and validate with npx gulp deploy:stg:help.

Quick Start

Use the operating-script skill to generate a new Gulp task file (for example deploy_stg.js) following the template, add the required {category}:help task, update gulpfile.js imports, and confirm operation with npx gulp {category}:help.