@yugoo-design/dsh-design-system-dsh

dsh plugin --profile web add @yugoo-design/dsh-design-system-dsh

Yugoo Design for DeepSeek Harness

Yugoo Design turns your DeepSeek Harness conversation into an interactive

workspace for ideation and design, with editable panels, structured knowledge

and guided iteration.

To install or update, give the [DSH installation guide](../companion/HOSTS.md#install-or-update-deepseek-harness)

to the Agent in your existing DSH conversation. It acquires the unified

yugoo-design product from npm and uses the product's release mapping to install

this aggregate and its internal modules. Request an exact published version, or

let the Agent resolve latest once and use that exact version for the operation.

Existing projects and host model/search settings must be preserved.

This README describes the DSH integration and its development references. The

historical checks below retain their original versions; use the selected

release's guide and manifest for a new installation.

Official DSH is a read-only Host compatibility target. This package uses public

Cordis, command, tool, Agent, interaction, subagent, Remote, and client-module

extension points and requires no DSH patch, fork, or Design-specific release.

Installing it adds direct Loader rows for generic Core, Panel, Studio, Design

Knowledge, the official Web App provider, and the official Web App content Kit.

DeepSeek Harness discovers each package's browser plugin through its own

dsh.client declaration; this distribution does not compile or hide a combined

client.

The Settings launcher source opens the full-page /design-studio/ workspace,

which uses the same Typert Remote and storage-domain-backed Studio service

without creating a Session or Agent. These source mechanisms do not establish

current Studio authoring or visual acceptance.

dsh-design-skills-web-app contains one Mindset plus self-contained Bundle

files, including optional ordinary Agent-facing scripts. Generic Core confines

their execution and gives them no Design Files or Git authority.

The official Web App Kit's 15 Bundles now declare their presentations in

panel.yaml, using shared components supplied by dsh-design-panel.

dsh-design-provider-web-app remains in this distribution for explicitly selected

native presentations and comparison; it is not the default presentation contract

of those declarative Bundles. Neither presentation layer owns generation,

validation, repair, or publication logic. Generic Core, Panel, and Studio do not

depend on the Web App Kit or its native provider. A Kit can revise its validated

panel definition or locale content without rebuilding the Host; introducing a

new shared runtime component or native UI surface requires a runtime release.

Installed-package native-equivalence acceptance remains separate from this

source declaration and is not established by the presence of 15 definitions.

File Workers negotiate the installed Host's public capabilities. Legacy Hosts

use their one-shot Subagent Runtime; RC3 uses the public Agent factory, as the

attached Producer and read-only reviewers do. Each Worker retains its exact

artifact grant, parent model route, depth limit and cancellation. Factory

children have real native Sessions and tool logs; they do not claim the

Subagent Runtime's manager catalog, events or capacity pool. A failed start is

reported rather than retried through a different backend.

Each configured Design Project owns one complete current definition tree at

design_kit/, separate from its design data in design_files/. Methods,

schemas, Panels, resources and scripts load from that project's Kit and mounted

Bundles. The library supplies the initial copy for a new project. Later library

edits do not replace existing project customizations; ask the Agent to compare

and apply wanted changes through the ordinary edit/validate/save/Git path.

Local content requires no release, version switch, upgrade wizard or remount.

Design data publication, human handoff and npm versions remain distinct.

Daily entry

DSH Web and Desktop use the same Core message producers. Plugin-authored

context, notices and delegated tasks carry the producer-owned source kind

yugoo-design; explicit user commands retain kind: user. Delivery still uses

the existing non-waking agent.inject() or delegated followup() operation.

The plugin does not rewrite Session history, replace the Host codec or translate

retired kind: plugin messages at runtime. UI presentation and Session protocol

version are separate compatibility boundaries.

Use /yugoo in the existing DSH conversation to open the project command help,

or /yugoo new <name>, /yugoo open <id|name|path> and /yugoo status to manage

Design Projects. These commands share the existing project service and native

conversation binding; they do not start a second host or change authentication.

/yugoo is the only registered project entry. Yugoo Design does not register

/design, even when that name is free, and does not offer it as a compatibility

alias. Another plugin's command remains untouched. A conflict on /yugoo fails

registration explicitly. Panel actions use /yugoo; internal service, tool and

package identifiers are not additional user command aliases.

Project storage

New Design Projects default to the system user's Documents directory under

YuGoo/Projects, using the same Core registry as Companion. Windows Documents

redirection and Linux XDG user directories are honored; WSL uses Linux storage.

An explicit Core projectsRoot takes precedence. This default affects only new

projects: existing projects, registry, native conversation bindings and runtime

state stay at their original paths. DSH authentication and host integration are

unchanged.

Installation target and current package composition

The product name is Yugoo Design. The single installation aggregate uses

@yugoo-design/dsh-design-system-dsh in both source and public npm metadata.

The other nine source packages and Loader identities keep their existing names;

their publi

…(truncated)