[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS4B1YP6GV26DSVTJF5YYD":3,"skill-same:01M7AS4B1YP6GV26DSVTJF5YYD":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AS4B1YP6GV26DSVTJF5YYD","dsh-find-simplifications",null,"Use when working in the deepseek-harness repo to find non-obvious simplification candidates, write proposed Agent Notes or inline TODO\u002FFIXME\u002FXXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surfaces.","Qiuzixiao\u002Fdeepseek-harness-desktop","Qiuzixiao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F120417469?v=4","01M7AS3GVP6K6CY963D6YR3613","Jar maker","01M7AS3GWP71XA2MZRRBM42Y41",0,"MIT","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdeepseek-harness\u002F.agents\u002Fskills\u002Fdsh-find-simplifications\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsh-find-simplifications\ndescription: 'Use when working in the deepseek-harness repo to find non-obvious simplification candidates, write proposed Agent Notes or inline TODO\u002FFIXME\u002FXXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surfaces.'\n---\n\n# Finding DeepSeek Harness Simplifications\n\nThis skill helps turn a broad \"find things to simplify\" request into evidence-backed Agent Notes that remove or collapse existing harness surface area. It is guidance, not a checklist: follow the code, keep judgment active, and prefer a few well-proven candidates over a pile of thin guesses.\n\n## Start With Repo Context\n\n- Read `AGENTS.md`, especially the pre-release stance and the conventions (including the tests-are-not-golden-truth and Agent Notes-are-not-golden-truth doctrines), plus [docs\u002Fdefensive-patterns.md](..\u002F..\u002F..\u002Fdocs\u002Fdefensive-patterns.md) and [docs\u002Ftesting.md](..\u002F..\u002F..\u002Fdocs\u002Ftesting.md).\n- Skim [docs\u002Farchitecture.md](..\u002F..\u002F..\u002Fdocs\u002Farchitecture.md) before judging anything under `packages\u002F`; simplifications that fight the service map or event taxonomy need extra evidence.\n- Use the Agent Note tree and its [rules](..\u002F..\u002Fnotes\u002FREADME.md) to understand intentional architecture. The most relevant implemented examples are [drop mutable session summary](..\u002F..\u002Fnotes\u002Fimplemented\u002Fsimplification\u002F2026-06-19-drop-mutable-session-summary.md), [shared persistence write coordinator](..\u002F..\u002Fnotes\u002Fimplemented\u002Farchitecture\u002F2026-06-18-shared-persistence-write-coordinator.md), [capability seams](..\u002F..\u002Fnotes\u002Fimplemented\u002Farchitecture\u002F2026-06-13-capability-seams.md), and the twin adapter \u002F dual persistence backend Agent Notes.\n- Treat dual LLM adapters and dual persistence backends as intentional by default. Do not propose deleting either twin\u002Fbackend as \"low effort\" unless the user explicitly overrides that constraint. Removing an unused method or hook inside a protected seam can still be valid if it does not collapse the protected design.\n\n## What Counts As A Strong Candidate\n\nA strong simplification removes, folds, or demotes something real and has clear evidence that the current design costs more than it buys:\n\n- A public method, event, config knob, registry notification, helper, package, durable event, or test artifact has no production consumer.\n- Tests or docs are the only consumers, and the behavior they pin is not load-bearing.\n- Two representations mirror the same fact, especially across durable session events and transient `agent\u002F*` events.\n- A seam has methods every implementation must support but no consumer uses.\n- A separate package exists only for test\u002Fdemo\u002Fsupport code and adds publish or dependency overhead.\n- A feature implements speculative product generality: multi-session\u002Fsession-load, background job rosters, live registry invalidation, mid-turn steering, tool-owned UI rendering, and similar designs with no product owner.\n- An invariant, rollback path, set of expected outputs, or special-case test exists only to protect an unused API.\n- Hand-rolled code reimplements what a well-maintained external package or a Node builtin at the engine floor already provides, and the swap would delete the implementation plus its dedicated tests ([dependency policy](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-07-26-dependencies-over-hand-rolling.md)).\n- The simplified behavior may differ slightly, but the new behavior is still reasonable and easier to explain.\n\nThin candidates are usually not enough for an Agent Note: deleting one typo, running `knip` once, removing an intentionally documented backend\u002Fadapter, or flagging \"this looks complex\" without call-site proof.\n\n## Survey Broadly\n\nUse parallel subagents when the user asks for breadth or many candidates. Give each agent a domain and require evidence, not guesses. Useful domains:\n\n- Agent loop and session log: turn\u002Fstep boundaries, steering, abort\u002Fcancel, durable events, replay, load\u002Fresume.\n- ACP automation and human UI APIs: prompt settlement and teardown on the protocol side; transcript rendering and interaction state on the UI side.\n- LLM\u002Ftools\u002Fsystem prompt: stream\u002Fgenerate APIs, assemblers, registries, tool schema defaults, presentation hooks.\n- Bash and tool execution: foreground\u002Fbackground split, job ownership, output spill files, executor methods.\n- Packages\u002Fexamples\u002Fscripts\u002Ftests: package splits, static inventories, redundant snapshot expected outputs, support packages.\n\nIf subagents are unavailable, simulate the same breadth yourself. Do not let the first good candidate stop the survey.\n\nStart with the largest production-code deltas. A broad simplification audit that stops after obvious unused symbols can miss the files where duplicated lifecycle or defensive machinery carries most of the cost.\n\n## Audit Trust And Lifecycle Boundaries\n\nFor every defensive copy, freeze, validator, and callback capture, name where the value came from and who owns it next. Same-process typed service\u002Fplugin calls ordinarily borrow readonly values; parsers, config loaders, queues, model\u002Ftool JSON, durable files, workers, processes, and wire decoders own or validate their data. Tests built around hostile getters, fake typed objects, callback replacement, or mutation after a same-process handoff are evidence of a potentially speculative contract, not automatic justification for keeping it.\n\nFor complex asynchronous code, draw the ownership graph and map each sentinel, readiness promise, cancellation path, disposer, and state flag to a distinct owner or transition. When several mechanisms mirror the same liveness or settlement fact, propose one transaction or lifecycle controller instead. Preserve separate machinery where it protects synchronous publication and rollback, callback containment, first-terminal-outcome arbitration, worker\u002Fprocess ownership, or dispose-to-quiescence.\n\n## Hand-Rolled Code Versus A Dependency\n\nIntroducing a dependency is a valid simplification move, not a policy exception: the [dependency policy](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-07-26-dependencies-over-hand-rolling.md) owns the bar. When surveying, ask of protocol parsers, framers, retry\u002Fbackoff loops, glob matchers, diff engines, and similar infrastructure: does a well-maintained npm package or a Node builtin at the repo's engine floor already do this?\n\nProve a dependency-swap candidate like any other, plus:\n\n- Read the hand-rolled implementation and name the exact surface the package covers; residual semantics the package does not cover count against the swap and stay in the Agent Note.\n- Check the package's health honestly (maintenance, adoption, transitive footprint) and prefer builtins when the engine floor has them.\n- Check the Agent Note tree first: schemastery, vendored Cordis, the twin adapters, and other recorded seams are settled — a swap that collapses one needs to beat the recorded rationale, not just cite the policy.\n- Weigh net deletion: implementation plus dedicated tests plus docs, minus the glue that remains. A wrapper that relocates the same complexity is not a win.\n\n## Prove Or Reject Each Candidate\n\nFor every symbol or behavior, classify consumers before writing:\n\n- Production corpus: `packages\u002F*\u002Fsrc`, `examples\u002F*\u002Fsrc`, `examples\u002F**\u002F*.yml`, runtime scripts, and loader\u002Fconfig paths.\n- Non-production corpus: tests, README\u002Fdocs, Agent Notes, snapshots, generated expected outputs, and comments.\n- Ambiguous corpus: examples and scripts that may be product smoke paths. Inspect usage before classifying.\n\nUse `rg` first. Good searches include the exact symbol, event name, package name, config key, method name with both `.name(` and `name(`, and any wire strings. Then read the call sites. `knip` can help, but it is not a substitute for understanding public interfaces, dynamic event names, tests, docs, and Cordis loader paths.\n\nReject or downgrade a candidate when:\n\n- A production caller exists and the simplification would be a feature decision rather than a cleanup.\n- The API is explicitly justified by an implemented Agent Note or a hard-won defensive pattern, and the new evidence does not beat that reason.\n- The removal would force unrelated churn without actually reducing the public API or required behavior.\n- The idea is correct but tiny. Add a targeted TODO\u002FFIXME\u002FXXX instead, using the urgency semantics in [docs\u002Fdevelopment.md](..\u002F..\u002F..\u002Fdocs\u002Fdevelopment.md).\n\n## Coalesce Superseded Agent Notes\n\nAudit the Agent Note tree when the user asks to reduce or coalesce it, or when the simplification being implemented makes an owning note obsolete. Do not expand every code-simplification survey into a repository-wide note audit.\n\nUse [`dsh-archive-agent-notes`](..\u002Fdsh-archive-agent-notes\u002FSKILL.md) for retention judgment and archive mechanics. Low-future-value implemented notes move as frozen triplets to `archived\u002F{kind}`; proposed notes are never archived; rejected notes that no longer prevent a tempting mistake are deleted. Do not edit an archived note while simplifying current prose or code.\n\nFollow the deletion rule in the [Agent Note rules](..\u002F..\u002Fnotes\u002FREADME.md#when-to-write-one); do not duplicate or weaken it here. For each candidate chain:\n\n1. Identify the current owner from shipped code, configuration, generated catalogs, package docs, newer Agent Notes, and inbound links; dates and titles are discovery hints, not proof.\n2. Classify the old note as fully or partially superseded. Any surviving behavior, current contract, durable format, compatibility obligation, or independently current rejected alternative makes it partial. Rationale that can be transferred to the current owner does not by itself make supersession partial.\n3. For full supersession, move every unique rationale, alternative, consequence, shipped verification evidence, and named coverage gap into the current owner. An inventory that only describes deleted implementation mechanics is not one of those decision facts.\n4. Repair every inbound link, then delete the English note, Chinese counterpart, and consistency record together.\n5. Search exact filenames, symbols, config keys, event names, and wire strings after the edit. Keep partial supersessions cross-linked and current.\n\nAn added-then-removed feature is a common full-supersession case. Let the removal note own the history only when the feature is absent from production code, configuration, schemas, durable or wire formats, migration, and compatibility behavior; no current documentation presents it as available; and no test exercises it as supported behavior. Removal rationale and tests that enforce absence may remain. Preserve why the feature originally existed, why that motivation no longer justified it, alternatives to full removal, the capability given up, conditions for reintroduction, and evidence that removal is complete. Old tests and implementation mechanics that verified only the deleted behavior are not current verification evidence.\n\nReject consolidation when the removal is only one transport, default, implementation, or presentation of a feature; when persisted data or compatibility handling survives; or when the removal note does not yet carry enough rationale to prevent accidental reintroduction. A current negative design decision may legitimately need its own note even though the removed implementation is gone.\n\n## Write The Agent Note\n\nCreate one file per durable proposal under `.agents\u002Fnotes\u002F\u003Clifecycle>\u002F\u003Cclass>\u002Fyyyy-mm-dd-topic.md`, following the lifecycle and classification rules in `.agents\u002Fnotes\u002FREADME.md`. Keep prose paragraphs on one physical line and use relative Markdown links.\n\nPrefer this structure, adjusting when the idea needs it:\n\n- `# Agent Note: \u003Caction-oriented title>`\n- `Status: proposed`\n- `## Problem`: name the current API, cite the relevant files, and state the consumer evidence. Separate production callers from tests\u002Fdocs.\n- `## Proposal`: say exactly what to remove, fold, demote, or rehome. Include tests, docs, READMEs, JSDoc, event-taxonomy, snapshot, and generated-file cleanup when relevant.\n- `## Why not keep it?` or `## What we give up`: make the strongest counterargument legible.\n- `## Acceptance criteria`: observable end state and gates.\n- `## Risks`: public API changes, behavior changes, future product wants, and why the tradeoff is still reasonable.\n\nBe concrete enough that an implementing PR can follow the trail. Avoid vague \"simplify this package\" Agent Notes. When a proposal overlaps an existing Agent Note, consolidate the useful details into the existing one rather than creating a duplicate.\n\n## Inline TODO Notes\n\nUse inline TODO\u002FFIXME\u002FXXX only for small, local cleanups that are clearly useful but not durable design decisions. Keep them short and actionable:\n\n- Name the smell with a stable tag, e.g. `TODO(double-default)` or `XXX(unused-default)`.\n- Explain why it is safe to revisit and what action would simplify it.\n- Do not add TODOs for speculative complaints or for behavior that needs an Agent Note-level decision.\n\n## When Folding Another PR Or Branch\n\nDiff the sibling branch against `origin\u002Fmaster`, not against the current PR branch, so you see its independent contribution. For each item:\n\n- Port non-overlapping Agent Notes or TODOs that meet the quality bar.\n- Consolidate overlapping material into the existing Agent Note that owns the topic.\n- Do not port duplicate or lower-confidence proposals just to preserve the count.\n- Update the PR body so reviewers see the true candidate count and scope.\n- Close the duplicate PR only when the user asked you to, or when you clearly own that housekeeping.\n\n## Validation And PR Hygiene\n\nFor docs-only Agent Note work, run at least `pnpm run doc-sync`, `pnpm run lint`, and `git diff --check`. For code comments or skill changes, also run the relevant validator when one exists. Select any other evidence from the outgoing diff; the pre-push hook contributes typecheck only.\n\nWhen opening or updating a PR, summarize:\n\n- How many Agent Notes and inline notes were added, consolidated, retained as partial supersessions, or deleted.\n- The main areas surveyed.\n- What was intentionally excluded.\n- Which checks passed.\n\nFor each consolidation group, name the old and current owners, state the evidence for full supersession, and explain why deletion is safe. If an added-then-removed scan finds no qualifying note, report that result and the representative partial cases retained.\n\nUse a draft PR while the survey is still expanding; mark ready only when the candidate set, review responses, and validation are settled.\n","# Finding DeepSeek Harness Simplifications\n\nThis skill helps turn a broad \"find things to simplify\" request into evidence-backed Agent Notes that remove or collapse existing harness surface area. It is guidance, not a checklist: follow the code, keep judgment active, and prefer a few well-proven candidates over a pile of thin guesses.\n\n## Start With Repo Context\n\n- Read `AGENTS.md`, especially the pre-release stance and the conventions (including the tests-are-not-golden-truth and Agent Notes-are-not-golden-truth doctrines), plus [docs\u002Fdefensive-patterns.md](..\u002F..\u002F..\u002Fdocs\u002Fdefensive-patterns.md) and [docs\u002Ftesting.md](..\u002F..\u002F..\u002Fdocs\u002Ftesting.md).\n- Skim [docs\u002Farchitecture.md](..\u002F..\u002F..\u002Fdocs\u002Farchitecture.md) before judging anything under `packages\u002F`; simplifications that fight the service map or event taxonomy need extra evidence.\n- Use the Agent Note tree and its [rules](..\u002F..\u002Fnotes\u002FREADME.md) to understand intentional architecture. The most relevant implemented examples are [drop mutable session summary](..\u002F..\u002Fnotes\u002Fimplemented\u002Fsimplification\u002F2026-06-19-drop-mutable-session-summary.md), [shared persistence write coordinator](..\u002F..\u002Fnotes\u002Fimplemented\u002Farchitecture\u002F2026-06-18-shared-persistence-write-coordinator.md), [capability seams](..\u002F..\u002Fnotes\u002Fimplemented\u002Farchitecture\u002F2026-06-13-capability-seams.md), and the twin adapter \u002F dual persistence backend Agent Notes.\n- Treat dual LLM adapters and dual persistence backends as intentional by default. Do not propose deleting either twin\u002Fbackend as \"low effort\" unless the user explicitly overrides that constraint. Removing an unused method or hook inside a protected seam can still be valid if it does not collapse the protected design.\n\n## What Counts As A Strong Candidate\n\nA strong simplification removes, folds, or demotes something real and has clear evidence that the current design costs more than it buys:\n\n- A public method, event, config knob, registry notification, helper, package, durable event, or test artifact has no production consumer.\n- Tests or docs are the only consumers, and the behavior they pin is not load-bearing.\n- Two representations mirror the same fact, especially across durable session events and transient `agent\u002F*` events.\n- A seam has methods every implementation must support but no consumer uses.\n- A separate package exists only for test\u002Fdemo\u002Fsupport code and adds publish or dependency overhead.\n- A feature implements speculative product generality: multi-session\u002Fsession-load, background job rosters, live registry invalidation, mid-turn steering, tool-owned UI rendering, and similar designs with no product owner.\n- An invariant, rollback path, set of expected outputs, or special-case test exists only to protect an unused API.\n- Hand-rolled code reimplements what a well-maintained external package or a Node builtin at the engine floor already provides, and the swap would delete the implementation plus its dedicated tests ([dependency policy](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-07-26-dependencies-over-hand-rolling.md)).\n- The simplified behavior may differ slightly, but the new behavior is still reasonable and easier to explain.\n\nThin candidates are usually not enough for an Agent Note: deleting one typo, running `knip` once, removing an intentionally documented backend\u002Fadapter, or flagging \"this looks complex\" without call-site proof.\n\n## Survey Broadly\n\nUse parallel subagents when the user asks for breadth or many candidates. Give each agent a domain and require evidence, not guesses. Useful domains:\n\n- Agent loop and session log: turn\u002Fstep boundaries, steering, abort\u002Fcancel, durable events, replay, load\u002Fresume.\n- ACP automation and human UI APIs: prompt settlement and teardown on the protocol side; transcript rendering and interaction state on the UI side.\n- LLM\u002Ftools\u002Fsystem prompt: stream\u002Fgenerate APIs, assemblers, registries, tool schema defaults, presentation hooks.\n- Bash and tool execution: foreground\u002Fbackground split, job ownership, output spill files, executor methods.\n- Packages\u002Fexamples\u002Fscripts\u002Ftests: package splits, static inventories, redundant snapshot expected outputs, support packages.\n\nIf subagents are unavailable, simulate the same breadth yourself. Do not let the first good candidate stop the survey.\n\nStart with the largest production-code deltas. A broad simplification audit that stops after obvious unused symbols can miss the files where duplicated lifecycle or defensive machinery carries most of the cost.\n\n## Audit Trust And Lifecycle Boundaries\n\nFor every defensive copy, freeze, validator, and callback capture, name where the value came from and who owns it next. Same-process typed service\u002Fplugin calls ordinarily borrow readonly values; parsers, config loaders, queues, model\u002Ftool JSON, durable files, workers, processes, and wire decoders own or validate their data. Tests built around hostile getters, fake typed objects, callback replacement, or mutation after a same-process handoff are evidence of a potentially speculative contract, not automatic justification for keeping it.\n\nFor complex asynchronous code, draw the ownership graph and map each sentinel, readiness promise, cancellation path, disposer, and state flag to a distinct owner or transition. When several mechanisms mirror the same liveness or settlement fact, propose one transaction or lifecycle controller instead. Preserve separate machinery where it protects synchronous publication and rollback, callback containment, first-terminal-outcome arbitration, worker\u002Fprocess ownership, or dispose-to-quiescence.\n\n## Hand-Rolled Code Versus A Dependency\n\nIntroducing a dependency is a valid simplification move, not a policy exception: the [dependency policy](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-07-26-dependencies-over-hand-rolling.md) owns the bar. When surveying, ask of protocol parsers, framers, retry\u002Fbackoff loops, glob matchers, diff engines, and similar infrastructure: does a well-maintained npm package or a Node builtin at the repo's engine floor already do this?\n\nProve a dependency-swap candidate like any other, plus:\n\n- Read the hand-rolled implementation and name the exact surface the package covers; residual semantics the package does not cover count against the swap and stay in the Agent Note.\n- Check the package's health honestly (maintenance, adoption, transitive footprint) and prefer builtins when the engine floor has them.\n- Check the Agent Note tree first: schemastery, vendored Cordis, the twin adapters, and other recorded seams are settled — a swap that collapses one needs to beat the recorded rationale, not just cite the policy.\n- Weigh net deletion: implementation plus dedicated tests plus docs, minus the glue that remains. A wrapper that relocates the same complexity is not a win.\n\n## Prove Or Reject Each Candidate\n\nFor every symbol or behavior, classify consumers before writing:\n\n- Production corpus: `packages\u002F*\u002Fsrc`, `examples\u002F*\u002Fsrc`, `examples\u002F**\u002F*.yml`, runtime scripts, and loader\u002Fconfig paths.\n- Non-production corpus: tests, README\u002Fdocs, Agent Notes, snapshots, generated expected outputs, and comments.\n- Ambiguous corpus: examples and scripts that may be product smoke paths. Inspect usage before classifying.\n\nUse `rg` first. Good searches include the exact symbol, event name, package name, config key, method name with both `.name(` and `name(`, and any wire strings. Then read the call sites. `knip` can help, but it is not a substitute for understanding public interfaces, dynamic event names, tests, docs, and Cordis loader paths.\n\nReject or downgrade a candidate when:\n\n- A production caller exists and the simplification would be a feature decision rather than a cleanup.\n- The API is explicitly justified by an implemented Agent Note or a hard-won defensive pattern, and the new evidence does not beat that reason.\n- The removal would force unrelated churn without actually reducing the public API or required behavior.\n- The idea is correct but tiny. Add a targeted TODO\u002FFIXME\u002FXXX instead, using the urgency semantics in [docs\u002Fdevelopment.md](..\u002F..\u002F..\u002Fdocs\u002Fdevelopment.md).\n\n## Coalesce Superseded Agent Notes\n\nAudit the Agent Note tree when the user asks to reduce or coalesce it, or when the simplification being implemented makes an owning note obsolete. Do not expand every code-simplification survey into a repository-wide note audit.\n\nUse [`dsh-archive-agent-notes`](..\u002Fdsh-archive-agent-notes\u002FSKILL.md) for retention judgment and archive mechanics. Low-future-value implemented notes move as frozen triplets to `archived\u002F{kind}`; proposed notes are never archived; rejected notes that no longer prevent a tempting mistake are deleted. Do not edit an archived note while simplifying current prose or code.\n\nFollow the deletion rule in the [Agent Note rules](..\u002F..\u002Fnotes\u002FREADME.md#when-to-write-one); do not duplicate or weaken it here. For each candidate chain:\n\n1. Identify the current owner from shipped code, configuration, generated catalogs, package docs, newer Agent Notes, and inbound links; dates and titles are discovery hints, not proof.\n2. Classify the old note as fully or partially superseded. Any surviving behavior, current contract, durable format, compatibility obligation, or independently current rejected alternative makes it partial. Rationale that can be transferred to the current owner does not by itself make supersession partial.\n3. For full supersession, move every unique rationale, alternative, consequence, shipped verification evidence, and named coverage gap into the current owner. An inventory that only describes deleted implementation mechanics is not one of those decision facts.\n4. Repair every inbound link, then delete the English note, Chinese counterpart, and consistency record together.\n5. Search exact filenames, symbols, config keys, event names, and wire strings after the edit. Keep partial supersessions cross-linked and current.\n\nAn added-then-removed feature is a common full-supersession case. Let the removal note own the history only when the feature is absent from production code, configuration, schemas, durable or wire formats, migration, and compatibility behavior; no current documentation presents it as available; and no test exercises it as supported behavior. Removal rationale and tests that enforce absence may remain. Preserve why the feature originally existed, why that motivation no longer justified it, alternatives to full removal, the capability given up, conditions for reintroduction, and evidence that removal is complete. Old tests and implementation mechanics that verified only the deleted behavior are not current verification evidence.\n\nReject consolidation when the removal is only one transport, default, implementation, or presentation of a feature; when persisted data or compatibility handling survives; or when the removal note does not yet carry enough rationale to prevent accidental reintroduction. A current negative design decision may legitimately need its own note even though the removed implementation is gone.\n\n## Write The Agent Note\n\nCreate one file per durable proposal under `.agents\u002Fnotes\u002F\u003Clifecycle>\u002F\u003Cclass>\u002Fyyyy-mm-dd-topic.md`, following the lifecycle and classification rules in `.agents\u002Fnotes\u002FREADME.md`. Keep prose paragraphs on one physical line and use relative Markdown links.\n\nPrefer this structure, adjusting when the idea needs it:\n\n- `# Agent Note: \u003Caction-oriented title>`\n- `Status: proposed`\n- `## Problem`: name the current API, cite the relevant files, and state the consumer evidence. Separate production callers from tests\u002Fdocs.\n- `## Proposal`: say exactly what to remove, fold, demote, or rehome. Include tests, docs, READMEs, JSDoc, event-taxonomy, snapshot, and generated-file cleanup when relevant.\n- `## Why not keep it?` or `## What we give up`: make the strongest counterargument legible.\n- `## Acceptance criteria`: observable end state and gates.\n- `## Risks`: public API changes, behavior changes, future product wants, and why the tradeoff is still reasonable.\n\nBe concrete enough that an implementing PR can follow the trail. Avoid vague \"simplify this package\" Agent Notes. When a proposal overlaps an existing Agent Note, consolidate the useful details into the existing one rather than creating a duplicate.\n\n## Inline TODO Notes\n\nUse inline TODO\u002FFIXME\u002FXXX only for small, local cleanups that are clearly useful but not durable design decisions. Keep them short and actionable:\n\n- Name the smell with a stable tag, e.g. `TODO(double-default)` or `XXX(unused-default)`.\n- Explain why it is safe to revisit and what action would simplify it.\n- Do not add TODOs for speculative complaints or for behavior that needs an Agent Note-level decision.\n\n## When Folding Another PR Or Branch\n\nDiff the sibling branch against `origin\u002Fmaster`, not against the current PR branch, so you see its independent contribution. For each item:\n\n- Port non-overlapping Agent Notes or TODOs that meet the quality bar.\n- Consolidate overlapping material into the existing Agent Note that owns the topic.\n- Do not port duplicate or lower-confidence proposals just to preserve the count.\n- Update the PR body so reviewers see the true candidate count and scope.\n- Close the duplicate PR only when the user asked you to, or when you clearly own that housekeeping.\n\n## Validation And PR Hygiene\n\nFor docs-only Agent Note work, run at least `pnpm run doc-sync`, `pnpm run lint`, and `git diff --check`. For code comments or skill changes, also run the relevant validator when one exists. Select any other evidence from the outgoing diff; the pre-push hook contributes typecheck only.\n\nWhen opening or updating a PR, summarize:\n\n- How many Agent Notes and inline notes were added, consolidated, retained as partial supersessions, or deleted.\n- The main areas surveyed.\n- What was intentionally excluded.\n- Which checks passed.\n\nFor each consolidation group, name the old and current owners, state the evidence for full supersession, and explain why deletion is safe. If an added-then-removed scan finds no qualifying note, report that result and the representative partial cases retained.\n\nUse a draft PR while the survey is still expanding; mark ready only when the candidate set, review responses, and validation are settled.\n",{"name":5,"description":7},"master","62087459d3d7f4149ee9a33bff63ed9ca4b6c1d8","deepseek-harness\u002F.agents\u002Fskills\u002Fdsh-find-simplifications","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop","https:\u002F\u002Fdshdesktop.cn","https:\u002F\u002Fgithub.com\u002FQiuzixiao","2026-09-10 18:31:27",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-find-simplifications",{"tool":37,"command":38},"bunx","bunx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-find-simplifications",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-find-simplifications","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdeepseek-harness\u002F.agents\u002Fskills\u002Fdsh-find-simplifications\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7AS86XE0PJQ0MCDH5DPZCFC","short-drama-domain","Short-drama project object map and task routing. Use when the user works with screenplay artifacts, episode scenes, continuity, diagnosis, revision, or delivery. This skill provides operational vocabulary and questions, not a mandatory writing style.","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-short-drama\u002Fmanaged-presets\u002Fscreenplay-v1\u002Fskills\u002Fshort-drama-domain\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7AS837QRW3BDY2W6PHXB2AB","creative-project-organization","从梗概开始创作、生成设定\u002F人物\u002F大纲\u002F正文等文件时，在首批落盘前规划内容分组和保存位置；新增独立交付物时复核布局。自动适配项目语言和命名习惯，也用于用户要求的项目整理。无需用户提出归档要求。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-short-drama\u002Fmanaged-presets\u002Fscreenplay-v1\u002Fskills\u002Fcreative-project-organization\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AS7YHQTH0H79BZGANZF6V5","skill-sink","技能沉淀机制：把创作中验证有效的经验、方法论与个人文风，提炼成可复用的 DSH skill。当创作中发现可复用经验、用户要沉淀个人文风、或要把反复出现的规则固化成技能时使用。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-plugin-desktop\u002Fresources\u002Fagent-presets\u002Fshort-drama\u002Fskills\u002Fskill-sink\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AS7S0NS2PQVSNFQFRES3PW","short-drama-zonggang","短剧创作总纲与情绪账务引擎方法论。以「恨账—存债\u002F付息\u002F兑付」债务系统为内核，覆盖选题、故事骨架、压爽循环与卡点、付费闸门、台词正文格式、验收自检与失效模式库。当用户要创作短剧剧本、立项选题、写分集大纲、写正文台词、设计付费卡点，或评审\u002F修改\u002F验收短剧时，先加载本 Skill。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-plugin-desktop\u002Fresources\u002Fagent-presets\u002Fshort-drama\u002Fskills\u002Fshort-drama-zonggang\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AS7KHM1F0V7HM33VDGAEQG","short-drama-structure","把已确认的故事前提排成短剧四幕二十拍、分集节奏和场次骨架（4×5 节拍表、卡点与高潮兑现）。当用户已有故事梗概，要求拆成四幕\u002F20 拍\u002F分集\u002F场次表、中段松散需要重排转折，或想设置悬念、反转、付费卡点及高潮兑现路径时使用。不适用于从零提炼创意、单场对白润色或平台投稿咨询。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-plugin-desktop\u002Fresources\u002Fagent-presets\u002Fshort-drama\u002Fskills\u002Fshort-drama-structure\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AS7EEA9D20P4R5BBSPNBCN","short-drama-scene","当用户提供剧本片段、分场或对白，要求更可拍\u002F更有戏\u002F减少解释\u002F改得口语化时调用；重点处理单场冲突、动作进出、状态变化、信息差、潜台词和对白瘦身。不适用于从零搭故事结构、设计整部剧的悬念卡点或行业投稿咨询。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-plugin-desktop\u002Fresources\u002Fagent-presets\u002Fshort-drama\u002Fskills\u002Fshort-drama-scene\u002FSKILL.md",[],[]]