What problem does it solve? Setting up a new DSH plugin repository by hand is error-prone: template placeholders get left behind, dependency and TypeScript configurations drift out of sync, and unverified skeletons accumulate behavior code before the baseline build is proven. This Skill turns scaffolding into a disciplined, auditable procedure. ## Core Features & Use Cases - Template Copy with Guardrails: Copies only source-controlled template files, excludes build artifacts and package-manager stores, and refuses to overwrite an existing non-empty target directory. - Identity Replacement: Systematically updates package name, Cordis plugin ids, configuration defaults, tests, and documentation, then greps for leftover template markers. - Dependency and TypeScript Alignment: Keeps peerDependencies, registry dev dependencies, tsconfig files, Vitest aliases, and cordis.patch.yml consistent for every planned host API import. - Baseline Verification: Runs install, self-containment checks, typecheck, tests, build, and prepare before any product behavior is added. - Use Case: After planning a new DSH Web plugin, hand off the target path, package name, and plugin id to produce a clean repository whose lockfile, build graph, and tests all pass from a fresh clone. ## Quick Start Use the dsh-plugin-scaffold skill to create a new standalone DSH plugin repository at my target path with my package name and plugin id, then run the full baseline verification.