Commit Graph

6 Commits

Author SHA1 Message Date
shehjad-dev addd899490 chore(plugin): bump to 0.6.0 2026-08-21 10:56:53 +06:00
shehjad-dev f2cfa23eaf feat(skill): add complete presentation workflow 2026-08-21 05:16:36 +06:00
SToneX a02aa747ce chore(plugin): bump to 0.5.1 (#42) 2026-08-20 17:46:47 +08:00
SToneX 16c99dbc15 chore(plugin): bump to 0.5.0 (#39) 2026-08-20 15:06:45 +08:00
shehjad-dev 59f7e45210 chore(plugin): bump to 0.4.4 2026-08-17 14:02:03 +06:00
Jason Zhou 1f5f6bcd1b feat(plugin): add DeepSeek Harness (dsh) packaging
A fourth shop window off the same `skills/superdesign/` tree. dsh reads no
`plugin.json`: it installs an npm package whose `package.json` declares
`dsh.bundle`, pointing at a config layer that mounts a `ctx.skills` provider.

    dsh plugin --profile <name> add github:superdesigndev/superdesign-skill

Two choices are load-bearing. The bundle is plain ESM with no build step,
because a git install fetches sources rather than build output and a `prepare`
script would force every user to allowlist a build before their first install
works. And it depends on no `@deepseek-ai/*` package, because an out-of-tree
bundle pulling an in-box one installs a second copy that drifts from the host's
- so it implements the `list`/`get` provider contract directly instead of
reusing `dsh-skill-filesystem`. The skill description is parsed out of SKILL.md
at runtime, so there is no second copy to keep in sync.

Verified against `@deepseek-ai/dsh@0.1.0-rc.6`: `dsh plugin add` appends the
bundle to the profile, `--dump-config` shows the `# == superdesign-dsh` layer,
and the package resolves from the profile and returns a valid candidate.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsD1EYGHk1an8DLL1yrzqK
2026-08-15 16:36:08 +10:00