What problem does it solve? Writing a SharpPS.Shells pipeline incorrectly leads to common failures: pipelines that should have been plain functions, leaked machine-specific paths, builds that silently fail, and abort logic that kills cleanup steps. This Skill encodes the module's authoring rules so new workspace pipelines follow the established conventions from the start. ## Core Features & Use Cases - Pipeline vs Function Decision: Enforces the architectural rule that pipelines orchestrate ordered sequences with shared state while public functions do the actual work. - Standard Processor Patterns: Provides the 00-Help and 01-Resolve-Configuration templates, sharpps.config key conventions, and the $arguments shared-state model. - Correct Failure Handling: Teaches warn-and-abort semantics via $arguments["Aborted"], LASTEXITCODE reset, and ErrorActionPreference handling for native build commands. - Use Case: When adding a release pipeline to a project repo, use this Skill to scaffold Pipelines/release/ with properly ordered NN-*.ps1 processors, config-driven settings, and a verification checklist before shipping. ## Quick Start Ask the AI to create a new SharpPS.Shells pipeline named release in the current workspace with build, package, and verify steps following the authoring conventions.
