dsh-web: Skill for Claude Code

dsh-web Agent Coding

Root instructions own repository safety, branches, and merge gates. This skill owns the working method; it does not grant Git or release authorization.

Scope and implement

1. Confirm the root, branch, and dirty baseline before writing; preserve other sessions' files and index. Read only applicable directory instructions: packages for package work, docs for documentation, then the nearest owner.
2. Change the smallest owner: a plugin, skin, shared source, generator, or aggregate. Keep host/client/shared boundaries and browser platform-import/type-only SDK contracts in the package instructions. Modify generated copies through their source and generator, not by hand.
3. Follow Agent Note rules for non-trivial decisions. Reuse the owning note where appropriate; do not copy its lifecycle or format rules here.
4. Verify the affected behavior and review the diff. Run focused checks during edits, and the repository's complete required gates at merge/push/release boundaries, not after every local change. Report actual evidence and limitations; a commit is not delivery.

Context, delegation, and failure recovery

• Load task-relevant references, not the entire repository map. When authoring prompts, keep stable rules separate from changing evidence (queries, diffs, task state); place dynamic material after stable context where supported. Do not rewrite runtime-owned system/tool messages, assume cache hits, or change instruction priority for caching.
• Delegate independent, bounded work only when it helps. Select from available models by task difficulty, error cost, latency, and observed quality, not fixed provider aliases. Use capable reasoning for consequential ambiguity; do not infer that all documentation or static analysis is low-risk. Pass only necessary context and tools where the runtime permits.
• On a failing check, capture the exact log and exit code, reproduce with the narrowest useful command, fix the evidenced cause, and rerun the affected check. Separate pre-existing failures from regressions caused by this change; do not mix unrelated refactors into repairs.
• Stop repeating an approach when it adds no evidence or edits oscillate. State the obstacle, inspect a different cause or choose a materially different safe approach. Ask the user only for missing information, authorization, or a consequential choice; a retry count alone is not a reason to ask. Report an environment blocker rather than bypassing safety or weakening a gate.