DSH Plugins Marketplace

DSH Plugins

Plugins

/

dsh-uupm

d

dsh-uupm

Manifest valid

UI/UX Pro Max design-intelligence skill as a DeepSeek Harness bundle (unofficial, MIT, verified, reversible)

hasBundlePatch

UI/UX Pro Max for DeepSeek Harness

CI

Quick start (DSH Plugins page, three steps):

  1. Plugins → Add plugin → Install a third-party plugin
  2. Paste https://github.com/Chonwai/dsh-uupm#v1.0.5, tick the trust box, Enable now, restart DSH
  3. Load the skill with /ui-ux-pro-max (it also answers to its own trigger phrases)

@chonwai/dsh-uupm packages the UI/UX Pro Max design-intelligence skill as a DeepSeek Harness (DSH) bundle. It vendors the upstream skill body, its 17 catalog files, 22 stack CSVs and Python search scripts, and registers ui-ux-pro-max as one runtime skill with the package's own scripts/search.py path rendered in.

The vendored tree is upstream main @ 4f2dbb67 (2026-11-08), 80 commits after the released v2.15.0 tag (a38d04c3); upstream skill.json still reports 2.15.0, so this tree is newer than the release. The pin is the commit, not the tag (see NOTICE).

An independent community integration: not affiliated with or endorsed by the UI/UX Pro Max project or by DeepSeek. MIT, no runtime dependencies, no build step, no telemetry.

Scope rule (read this first): the bundle registers in the host/global skill layer. The Web app mounts skill-filesystem inside the agent preset's scope and disables the host-level filesystem row, so a file-level copy under ~/.agents/skills, $DSH_HOME/skills, or a project .agents/skills lives in the nearer preset layer and wins the name outright — the bundle cannot override it. Move the file copy out of the skills root to activate the bundle; see Migrating from a file-level install below. A profile install does not mean the row is the winning catalog entry while such a copy exists.

Demo

Example dashboard built from a generated design system

An example dashboard built from a MASTER.md that this skill generated for the query "internal analytics dashboard" (--design-system --persist -p "Ops Console"). The page is a hand-written HTML implementation of that generated token set, not a benchmark, not a score, and not a template the skill emits: the skill returns the design system (palette, typography, spacing, pattern, anti-patterns), a builder still writes the markup. Sources: examples/ops-console/ (index.html + the design-system/ops-console/MASTER.md it was built from).

What it is

  • One skill, registered at mount time. lib/index.js reads the vendored skills/ui-ux-pro-max/SKILL.md, substitutes its 17 {{SCRIPT_PATH}} macros with the absolute path of this package's scripts/search.py, and calls ctx.skills.register({ name, description, source: 'bundled', content, resourceBase: { kind: 'directory', path: skillDir } }). The model sees the upstream workflow plus a working absolute command path; resourceBase lets it reach data/ and scripts/.
  • Vendored data and scripts. data/** and scripts/** are byte-identical to the upstream checkout named in NOTICE (sha256 pins in checksums.txt), minus __pycache__/*.pyc and the upstream repo-only scripts/tests/ directory. validate_data.py is the shipped data gate; the upstream unittest suite is not shipped (see Known upstream limitations).
  • The skill body is rendered, not hand-edited. tools/vendor-upstream.sh renders SKILL.md from the upstream base template and the generic-agent platform manifest. The only differences from upstream are the resolved {{TITLE}} / {{DESCRIPTION}} / {{QUICK_REFERENCE}} macros and the deliberately unresolved {{SCRIPT_PATH}} token; no prose was changed.
  • Plugin-page metadata. locale/en.json, locale/zh.json and an original icon.svg give the bundle a card with a title and description.
  • Deliberately small surface. No client half, no composer pill, no settings/Config schema, no prompt section, no hooks, no telemetry. The host half only reads files inside its own package.

Why a bundle instead of copying the skill files

Copying the rendered skill into ~/.agents/skillsThis bundle
Shows up in PluginsNoYes — installed bundle with title, description, toggle/remove
Script pathsMust be rewritten by hand per machineSubstituted at mount time from the package location
On/off and removalManual file deletionPlugins page toggle / remove
VersioningYou track checksums yourselfPackage version + checksums.txt pins
UpdatesManual re-copyRe-vendor with one script, reinstall

The file-level route remains simpler if you never want the plugin lifecycle. This bundle is for people who want the skill to arrive with the package, with pinned bytes and a documented update path.

Requirements

  • DeepSeek Harness 0.2.2-rc.1 (engines.dsh: ">=0.2.2-rc.1 <0.3.0").
  • Node.js >= 22 (inherited from the Harness).
  • Python 3 for the skill's CLI searches (python3 --version). The scripts use the standard library only — no third-party packages, no network. Without Python the skill body still loads, but the search.py commands cannot run; the upstream body tells the model to ask you to install Python rather than doing it itself.
  • A managed DSH profile (the Desktop app's desktop profile, or a CLI-managed profile). The Desktop app's profile is managed by the app: install through the Web Plugins page or the plugin_manager tool, not dsh plugin add.

Install

All three routes are in INSTALL.md:

  1. Plugins page (recommended): Plugins → Add plugin → install a third-party plugin → paste this directory's absolute path.
  2. plugin_manager tool: plugin_manager(action: "install_bundle", target: "/abs/path/to/dsh-uupm").
  3. Local dev link (CLI-managed profiles only): dsh plugin add /abs/path/to/dsh-uupm links the checkout.

Restart DSH after installing or toggling. Profile bundle rows are composed when the DSH host boots; a new session or a page reload does not re-compose them, and plugin_manager showing installed/enabled is profile state, not proof that the running host mounted the row. See INSTALL.md.

The package is private on purpose: v1 installs from a local checkout, and no npm release is planned.

What you get

  • The skill ui-ux-pro-max in the session skill catalog (runtime provider). Its description states the upstream inventory: 80 searchable styles (51 active), 192 product palettes/reasoning profiles, 74 font pairings, 25 chart types, 17 GSAP presets, 105 icon rows (100 curated icons + 5 guidance rows), 22 stacks.

  • The upstream workflow: --design-system, --domain, --stack, design dials, RTL support, and the app-UI checklists — as written upstream.

  • Working commands, e.g.:

    python3 /abs/path/to/dsh-uupm/skills/ui-ux-pro-max/scripts/search.py \
      "fintech dashboard" --design-system
    
  • No always-on instruction text: unlike a rules bundle, this package costs nothing per request until the skill is loaded.

How the skill layer actually resolves this name

Three facts from the DSH source decide which ui-ux-pro-max a Web session sees:

  1. @deepseek-ai/dsh-web-app/presets/standard.patch.yml mounts skill-filesystem inside the agent preset's scope.
  2. @deepseek-ai/dsh-web-app/cordis.patch.yml disables the host-level skill-filesystem row ("presets own local discovery").
  3. @deepseek-ai/dsh-skill merges the global layer with the viewing scope's chain: the nearest layer's entry wins a duplicate name outright, and rank only orders duplicates inside one layer.

This bundle is a host row, so it registers in the global layer. Any file-level ui-ux-pro-max under ~/.agents/skills, $DSH_HOME/skills, or a project .agents/skills is discovered by the preset's filesystem provider and therefore sits in the nearer scoped layer, which wins unconditionally. The bundle cannot override it; the catalog entry remains the file copy (79/50/119 in this machine's old copy). Removing the file copy makes the bundle visible live (the filesystem watcher refreshes the catalog at the next pre-step); installing the bundle itself still needs a host restart.

The bundle's data is newer than this machine's old copy: that copy is main@56ea9cf (79 searchable styles / 50 active / 119 UX guidelines), while this bundle is main@4f2dbb67 (80 / 51 / 120).

Migrating from a file-level install (required for bundle to take effect)

Preflight — if this prints the warning, the copy will shadow the bundle:

test -d ~/.agents/skills/ui-ux-pro-max && echo "WARNING: file-level copy will shadow the bundle"

Back up and move the copy out of every skills root the preset scans:

mkdir -p ~/.dsh-backup
mv ~/.agents/skills/ui-ux-pro-max ~/.dsh-backup/ui-ux-pro-max-$(date +%F)
test -d "${DSH_HOME:-$HOME/.dsh}/skills/ui-ux-pro-max" && \
  mv "${DSH_HOME:-$HOME/.dsh}/skills/ui-ux-pro-max" \
     ~/.dsh-backup/ui-ux-pro-max-dsh-$(date +%F)

Also move any project-local <repo>/.agents/skills/ui-ux-pro-max out of that directory. Do not delete the backup until the bundle is verified.

The removal is picked up by the filesystem watcher: wait for the next pre-step (or send a message) and skill("ui-ux-pro-max") should now show Base directory: …/dsh-uupm/skills/ui-ux-pro-max and the 80/51/120 description, without restarting DSH. Restarting DSH is still required for bundle installs, and its catalog refresh will not help while a scoped copy exists. Nothing in this package deletes, moves or edits the file copy for you; this is a manual migration.

Out of scope in v1

Named so nobody waits for them: no composer pill or other client UI, no settings/Config schema or options, no system-prompt section, no telemetry, no upstream CLI, and none of the six upstream sub-skills (banner-design, brand, design, design-system, slides, ui-styling). No npm publish: the package stays private and installs from a checkout.

Known upstream limitations (audited 2026-11-09)

These are properties of the vendored upstream data and scripts, not of the bundle. They were measured against this package's copy on 2026-11-09; treat them as usage guidance, not defects we can fix without diverging from upstream.

  • --design-system silently falls back to a generic system. An off-topic, empty or non-English query returns a complete, confident-looking design system instead of "no match": "kubernetes ingress" yields pattern Hero + Features + CTA for category General, "電商後台 深色 儀表板" yields the same default, and the JSON has no fallback/confidence flag (design_system.reasoning_default is the only trace). Treat design-system output as a proposal to check, not a match.
  • --domain google-fonts retrieval is unreliable. Classification fields are sparse (Classifications ~55%, Variable Axes ~28%), so BM25 degrades to category matching: "geometric sans" returns Noto Sans Lycian first and "geometric sans variable" returns Noto Emoji first. Verify font suggestions by hand before recommending them.
  • High --variance can override product fit. --design-system for an internal analytics dashboard with --variance 8 selects Brutalism (best for design portfolios and counter-culture brands) while keeping the enterprise pattern and colors. Dials tune style, not relevance; state the desired direction in the query instead of relying on a high variance value.
  • "105 icons" overcounts. icons.csv has 105 rows: 100 curated icons + 4 Style Config rows + 1 Guideline row. Treat it as ~100 icons; the extra rows are useful guidance, not icons.
  • The upstream website is stale. uupm.cc advertises 57 styles / 95 palettes / 56 pairings / 8 stacks (checked 2026-11-09 in the audit), while this tree contains 80 searchable styles (51 active), 192 palettes, 74 pairings and 22 stacks. Believe the data, not the marketing page.
  • This bundle is newer than this machine's file-level copy. The ~/.agents/skills/ui-ux-pro-max copy is main@56ea9cf (79 searchable styles / 50 active / 119 UX guidelines); this bundle is main@4f2dbb67 (80 / 51 / 120). The difference is visible in the catalog description.

Verified vs unverified

Every claim below is executable from the package directory. Verified on macOS 27.2 (arm64), Node 22.21.1, Python 3.13.1. The two optional tests print SKIP and exit 0 when no extracted DSH package tree is present; SKIP is not verification — only a real PASS line counts.

CheckCommandResult
Offline gatebash tests/offline-check.shRESULT: PASS (92 checks)
Host smokenode tests/host-smoke.mjs11/11 passed
Registry smoke (optional)node tests/registry-smoke.mjs with DSH_ASAR_MODULES pointing at an extracted app.asar’s @deepseek-ai (default /tmp/dsh-asar/dsh/node_modules/@deepseek-ai)3/3 passed
Scope smoke (optional)node tests/scope-smoke.mjs, same DSH_ASAR_MODULES4/4 passed
JS syntaxnode --check lib/index.jsexit 0
Vendored searchPYTHONDONTWRITEBYTECODE=1 python3 skills/ui-ux-pro-max/scripts/search.py "fintech dashboard" --design-systemprints a full design system, exit 0
Data gatePYTHONDONTWRITEBYTECODE=1 python3 skills/ui-ux-pro-max/scripts/validate_data.pyOK: validated 12 domain files, 22 stack files, and ui-reasoning.csv

Layer precedence is shipped as the optional tests/scope-smoke.mjs. It uses the real SkillRegistry and the real createScope from an extracted DSH tree, mounts the bundle in the global layer, then registers a synthetic skill-filesystem provider inside a child scope. It asserts: the scoped provider wins the name (despite the bundle's lower rank number), the global layer still holds the bundle, and disposing the scoped layer makes the bundle visible to the scoped view (the live-flip shape). It does not mount the actual dsh-web-app preset — that wiring is source-read plus the observed live flip below. Without an extracted DSH tree it prints SKIP and exits 0.

Upstream's own unittest suite is not shipped. Four of its modules (test_catalog_refresh, test_catalog_summary_line_endings, test_relevance_evaluator, test_skill_script_paths) resolve the upstream monorepo root at import time, so they fail in any installed copy; the suite was healthy only inside the upstream repo. The shipped data gate is validate_data.py; the bundle's gates are checksums.txt, tests/offline-check.sh and tests/host-smoke.mjs.

Live flip (observed 2026-11-09, reported by the operator, not re-run by this repo): after moving ~/.agents/skills/ui-ux-pro-max out of the skills root, the running host's catalog changed from 79/50/119 to 80/51/120 without a restart, and skill("ui-ux-pro-max") returned Base directory: /Users/…/dsh-uupm/skills/ui-ux-pro-max. That is the exact prediction of the scope rule above and of tests/scope-smoke.mjs. Profile installation alone (dependency + bundle row + include:uupm + plugin_manager installed/enabled) was already true while the old copy was still winning, so it is not evidence of activation.

Unverified (stated so nobody reads more into the table):

  • npm publication. The package is private: true and not published to npm. Install from the git tag or the release tarball (see INSTALL); the @chonwai/dsh-uupm name is not resolvable from the npm registry.
  • Plugins page rendering of the localized title/description and the icon. The Plugins-page flow (paste URL → trust → Enable now → restart) was not re-tested end-to-end for this release; the install that was verified is the profile-level dependency + bundle row described above.
  • Non-macOS hosts and DSH versions other than 0.2.2-rc.1.
  • Tag-to-tree equality. The supplied checkout is a shallow clone at 4f2dbb67 with no tag object; the tree is 80 commits after the v2.15.0 tag (a38d04c3), and upstream skill.json still reports 2.15.0. The pin is the commit actually vendored; no tag equality is claimed (see NOTICE).

Development

npm test                  # acceptance gate: offline checks, prints RESULT: PASS
npm run check             # node --check on lib/ and tests/
npm run smoke             # offline host smoke suite
npm run registry-smoke    # real dsh-skill registry load-path test (needs extracted DSH modules)
npm run scope-smoke       # real scope/layer precedence test (needs extracted DSH modules)

Re-vendoring (the sustainability path):

bash tools/vendor-upstream.sh 4f2dbb67e64969a9a30ab00742f2d55d66ddec2b \
  --repo /path/to/ui-ux-pro-max-skill
# or, from an existing checkout without git refs:
bash tools/vendor-upstream.sh --from-dir /path/to/checkout \
  --ref 4f2dbb67e64969a9a30ab00742f2d55d66ddec2b

It copies data/ and scripts/ (dropping the upstream repo-only tests/), re-renders SKILL.md, and rewrites checksums.txt (version read from package.json) plus provenance.json (upstream, full ref, skillJsonVersion); it then runs the gates and is idempotent. Update the Source: commit line in NOTICE to the new provenance.json.ref — tests/offline-check.sh fails when they disagree, so the pin cannot drift. Always run Python with PYTHONDONTWRITEBYTECODE=1 when testing the package, because __pycache__/*.pyc are excluded by design and the offline check fails if they appear.

Repository layout

lib/index.js                 host half: read, render, register, dispose
cordis.patch.yml             one insert row: id uupm -> @chonwai/dsh-uupm
skills/ui-ux-pro-max/        vendored skill: SKILL.md, data/**, scripts/** (no tests/)
locale/{en,zh}.json          plugin-page title/description/detail
icon.svg                     original icon
checksums.txt                sha256 pins for every vendored file (versioned header)
provenance.json              upstream URL, full vendored commit, skill.json version
tools/vendor-upstream.sh     re-vendor + re-render + checksums + tests
tests/offline-check.sh       static acceptance gate
tests/host-smoke.mjs         fake-Cordis mount test for the host half
tests/registry-smoke.mjs     optional real dsh-skill registry load-path test
tests/scope-smoke.mjs        optional real scope/layer precedence test
INSTALL.md                   install / scope+layering / migration / updates / rollback
NOTICE                        upstream attribution and modification statement

Part of the @chonwai/dsh-* series

Independent DSH bundles, each one vendoring an upstream skill tree at a pinned commit with the same gates (checksums, offline gate, host smoke, release check):

BundleWhat it packages
dsh-gsap-skillsThe 8 official GSAP instruction skills (core, timeline, ScrollTrigger, plugins, React, frameworks, utils, performance)
dsh-uupm (this repo)UI/UX Pro Max design intelligence: 17 catalogs, 22 stack CSVs, Python search scripts
dsh-reinRein — Ponytail for DSH: six skills, a scoped always-on ruleset, and a composer-dock pill

License and attribution

MIT — see LICENSE. The skill body, data and scripts are vendored from UI/UX Pro Max (MIT, Copyright (c) 2024 Next Level Builder); see NOTICE for the pinned commit, the modification statement and the upstream license text. The icon is original artwork for this bundle.

Comments

Loading…