dsh.fish

The plugin hub for DeepSeek Harness — discovery, distribution and one-command install for every kind of artifact the harness can load.

The harness is built on "everything is a plugin" but ships no registry: its README asks authors to tag repositories with the dsh-plugin topic and leaves discovery there. This is that registry, plus the install path on both ends.

What it indexes

Six artifact kinds, each taken from something the harness really loads, each with its own install mechanism:

Kind	What it is	How it installs
Bundle	npm package declaring dsh.bundle.patch	dsh plugin --profile <p> add <spec>
Profile	ordered dsh.profile.bundles stack	one add per bundle, in order
Skill	SKILL.md bundle or flat Markdown	files written under $DSH_HOME/skills
MCP server	external Model Context Protocol server	a dsh-mcp-client row in the profile patch
Agent preset	directory holding one agent.cordis.yml	written to $DSH_HOME/.agent-presets/<id>
Hook bridge	Claude Code / Codex hook bridge	a bridge plugin row in the profile patch

Two ways in

From a browser — search, filter by kind and category, read the plan, copy the command.

From inside your agent — install the hub's own plugin and let the agent do it:

dsh plugin --profile web add github:stvlynn/dsh.fish#main

It registers four tools: hub_search, hub_show, hub_install and hub_account. Signing in uses the OAuth device flow — the plugin prints a code, you approve it in a browser, and the harness gets a token.

Both paths resolve the same install plan from the same domain code, so the command on the website and the one the agent runs cannot drift apart.

Repository layout

backend/    Domain-Driven Design: domain, application, infrastructure, interfaces
frontend/   Feature-Sliced Design: app, pages, widgets, features, entities, shared
packages/
  dsh-plugin-hub/   the `dsh-hub` bundle users install into their harness
docs/       architecture, layer conventions, operations, ADRs

Both halves deploy as one Cloudflare Worker: Hono at /api/*, React Router SSR everywhere else, D1 for the catalog and Better Auth's tables, KV for sessions and rate limiting, and a Cron Trigger that re-crawls every six hours.

Ten languages

Every page is served in English, Simplified and Traditional Chinese, Japanese, Korean, Spanish, French, German, Brazilian Portuguese and Russian, under a path prefix — /ja/browse, /zh-CN/a/<id> — with English unprefixed at the root.

A directory only ranks if it is found, so the multilingual surface is part of the product rather than a translation layer bolted on: reciprocal hreflang across all ten, canonical URLs that fold filters and profile previews away, schema.org markup on every plugin page, indexable /kind/<kind> and /category/<category> landing pages instead of query-string filters, and a sitemap set that lists every indexed plugin in every language with its real lastmod.

The catalog itself stays language-neutral: an artifact's summary and readme are whatever its author wrote, and the frame around them is what gets translated. See docs/seo/ and docs/frontend/i18n.md.

Development

pnpm install
pnpm --filter @dsh-fish/backend run db:generate   # regenerate migrations
pnpm run db:migrate:local                          # apply to local D1
pnpm run dev                                       # http://localhost:5173

Quality gates:

pnpm run typecheck
pnpm run test
pnpm run test:e2e
pnpm run build

The social card is generated, not drawn. Re-run it when the palette changes:

pnpm --filter @dsh-fish/frontend run og:build

Deployment, bindings and secrets: docs/operations/deployment.md.

Documentation

Start with AGENTS.md (same file as CLAUDE.md) for the ground rules, then:

• docs/project/architecture.md — system architecture and the artifact taxonomy
• docs/decisions/adr-0001-plugin-hub-architecture.md — why it is built this way
• docs/frontend/ — FSD conventions
• docs/backend/ — DDD conventions
• docs/seo/ — multilingual URLs, indexation, structured data, crawling

License

MIT