dsh-plugin-scaffold

Creates standalone DSH plugin repositories from a self-contained template with baseline verification.

21|4|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/0xsline/dsh-spotlight --skill dsh-plugin-scaffold-0xsline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dsh-plugin-scaffold
Source: https://github.com/0xsline/dsh-spotlight/tree/main/.agents/skills/dsh-plugin-scaffold
Command: npx skills add https://github.com/0xsline/dsh-spotlight --skill dsh-plugin-scaffold-0xsline

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about dsh-plugin-scaffold

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

FAQPage Schema
How do I create a new DSH plugin repository from a template?▼

Provide the target path, package name, plugin id, description, dependency matrix, and template source directory. The skill copies source-controlled template files, replaces identity in package.json, src, tests, and cordis.patch.yml, then runs baseline verification commands.

What inputs are required before scaffolding a DSH plugin?▼

You must supply target, packageName, pluginId, description, plugin form, dependency matrix, target profile, invariant decision, distribution assumption, and the template source directory. Names are validated for scope policy and lowercase kebab-case plugin ids before any copying.

Can I scaffold into an existing non-empty directory?▼

No. If the target exists and is non-empty, the skill stops and asks whether the task is an audit or merge instead. It never replaces an existing directory as part of scaffolding.

Does the DSH plugin template allow local file or link dependencies?▼

No. The template forbids local link: and file: dependencies and forbids project references that leave the repository. Every fresh clone must resolve its build graph from its own manifest and pnpm lockfile.

What commands verify the scaffolded plugin baseline?▼

Run pnpm install, pnpm run verify:self-contained, pnpm run typecheck, pnpm test, pnpm run build, and pnpm run prepare from the target repository. Scaffolding is complete only when these pass or a concrete external blocker is reported.

Why does the scaffold keep two separate build paths?▼

The development path uses tsc -b with tsdown bundling emitted declarations, while the Git install path uses scripts/prepare.mjs with dedicated prepare tsconfigs bundling from src. Both must resolve only files and dependencies declared inside the repository.