Guidance for designing public programming interfaces, meaning the methods and data structures other code is allowed to use. It emphasizes adding only interfaces with real callers and making invalid uses impossible to compile.
Guidance for asking technical questions and reporting bugs so another developer can reproduce and answer them. It covers versions, environment details, minimal reproduction steps, expected and actual results, errors, and attempted fixes.
A Chinese-language guide for reviewing code changes, pull requests, and diffs. It prioritizes correctness, resource cleanup, security, matching documentation, and tests before style.
Guidance for writing Git commit messages using Conventional Commits, a common format such as fix, feat, or docs followed by a short description. It focuses on explaining why a change was made.
A structured method for finding the underlying cause of a software problem. It moves from reproducing the problem, to locating the responsible code, to testing a specific explanation, and then to fixing it with a regression test.
A step-by-step guide for building and installing a first DSH plugin. DSH is a software tool whose plugins can add tools, connect outside services, or respond to agent events.
Guidance for helping someone use DeepSeek Harness, a local runtime for coding agents, for the first time. It explains the runtime, profiles, workspace, permissions, and how extensions are discovered.
A guide for building and debugging plugins for DeepSeek Harness, a developer-preview tool built on the Cordis component framework. It explains how plugins are exported, loaded, and connected to services.
Instructions for quickly understanding an unfamiliar software project by tracing its purpose, entry point, main data flow, key abstractions, and external dependencies. They are written in Chinese.
An introductory guide to DeepSeek Harness, a system built from plug-ins, which are add-ons that provide capabilities such as skills, tools, or external connections.
A performance-improvement guide that requires measuring real behaviour before changing code. It explains how to identify bottlenecks, test one change at a time, and check that the change did not break anything.
A Chinese-language guide for planning substantial software changes before writing code. It asks you to clarify the goal, boundaries, constraints, existing code, implementation steps, risks, and how success will be tested.
A safe code-refactoring guide for changing code structure while keeping its external behavior the same. Refactoring means reorganizing code without changing what it does.
A Chinese-language guide for reviewing software security by tracing untrusted data from its source to the operations it reaches. It covers inputs such as requests, files, configuration, third-party responses, and AI output.
A test-first development guide, where tests are written before the code they check. TDD, or test-driven development, means first writing a test that fails, then writing the simplest code that makes it pass.
A web-research skill that gathers current information from original sources such as official documentation, source code, papers, and announcements. It marks uncertainty and avoids treating missing search results as proof that something does not exist.
A guide to writing project documentation, especially README files. It explains how tutorials differ from reference material and where each kind of information belongs.
A writing guide for Chinese technical documents such as READMEs, tutorials, blogs, and technical explanations. It focuses on direct conclusions, clear actions, natural Chinese, and consistent technical terms.