Max-Null/dsh-chinese-thinking
Injects one fixed system-prompt section so the agent thinks and replies in Chinese, regardless of the user's language.
Listed
1
Session
Bundle verified
Preview
What it does
Injects one fixed system-prompt section so the agent thinks and replies in Chinese, regardless of the user's language.
Best for
- Chinese-only workflows that need every agent turn to think and reply in Chinese.
- Teams wanting one consistent, fixed language instruction applied before the persona section.
- Users who want Chinese enforcement without storage, tools, or mutable plugin state.
Not ideal for
- Multilingual workflows where the reply language should follow the user's language.
- Sessions that need to switch languages dynamically or customize the injected instruction.
- Hosts without the documented `@deepseek-ai/dsh-system-prompt` and Cordis peer services.
README
dsh-chinese-thinking
一个”小而美”的 DeepSeek Harness 插件，只做一件事：注入一条固定的 system-prompt section，让 agent 始终用中文思考和回复——无论用户用什么语言。
无存储、无工具、无状态。一条固定文本，前缀稳定、缓存安全。
注入的文案
始终使用中文进行思考和回复，无论用户使用什么语言。
用法
npm install @max-null/dsh-chinese-thinking
在你的 cordis.yml 加一条（system-prompt 由宿主已有）：
- id: chinese-thinking
name: '@max-null/dsh-chinese-thinking'
实现
ctx.systemPrompt.section({
name: 'chinese-thinking',
order: -90, // persona 之前（身份声明 -100 之后），每轮最先读到
text: '始终使用中文进行思考和回复，无论用户使用什么语言。',
})
SSID 系列
本插件属于 @max-null/* 插件系列——这一系列共同构成 SSID（思灵 · Seek Soul in Darkness） 桌面体验。SSID 是整合它们的盒：dsh-plugin-center · dsh-memory · dsh-chinese-thinking · dsh-guardian · dsh-habit。
This plugin belongs to the @max-null/* family — a set of plugins that together form the SSID (思灵 · Seek Soul in Darkness) desktop experience.
依赖（peerDependencies，由宿主提供）
@deepseek-ai/cordis、@deepseek-ai/dsh-system-prompt
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:Max-Null/dsh-chinese-thinking in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.