35 RESULTS · “poc”
v2.12.0 · GPL-2.0
把 DeepSeek Harness 装进你的口袋：电脑上跑 dsh web，手机扫码即同步访问（局域网 + 公网，实时同屏）Put DeepSeek Harness in your pocket: run dsh web on your computer and access it synchronously by scanning a QR code on your phone (LAN + public network, real‑time screen mirroring)
v1.0.0 · MIT
不把整台机器交出去，只送出挡路的决定和下一步：DeepSeek Harness 的审批、ask_user_question 提问与结果回复，以飞书卡片发到手机——桌面优先、只出站；执行过程实时可见，下一段任务一键即开。
— · MIT
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Teach the user a new skill or concept, within this workspace.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Writing, exploit: shape raw material into an article, paragraph by paragraph.
Writing, explore: mine raw fragments, no structure yet.
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
Grill me about specs for the workflows I want to build, within this workspace.
Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.
Use when writing a PR body.
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
Implement the result of /to-spec and /to-tickets in code.
Stop. That last message did not land: re-pitch it.
Implement a piece of work based on a spec or set of tickets.
No description yet.