What problem does it solve? Implementing a DeepSeek Harness (DSH) plugin involves many subtle rules—Cordis Loader export shapes, fiber-owned effect disposal, Schemastery config validation, invariant companions, and bundle metadata—that are easy to get wrong and cause silent unload or registration bugs. ## Core Features & Use Cases - Plugin form enforcement: Preserves the correct function-plugin namespace export or service-plugin default export so the Cordis Loader never drops inject, Config, or apply. - Lifecycle and config rules: Requires every registry contribution to be a fiber-owned effect, validates configuration with Schemastery, and keeps credentials out of defaults, logs, and tests. - Invariant and metadata maintenance: Keeps src/invariant.ts, package.json exports, and cordis.patch.yml synchronized with the code, plus JSDoc and README contract documentation. - Use Case: After planning and scaffolding a new DSH Web plugin, use this Skill to implement the approved handoff—producing validated config, declared injections, disposable registrations, an invariant companion, updated docs, and focused tests. ## Quick Start Use the dsh-plugin-implement skill to implement the planned standalone DSH plugin including its invariant, documentation, and focused tests.
