Imported from Player-MINEPIG/dsh-tavern (
.agents/skills/dsh-tavern-development/SKILL.md). Install upstream withnpx skills add Player-MINEPIG/dsh-tavern --skill dsh-tavern-development. Copyright stays with the author.
DSH Tavern Development
Use project-specific evidence for the requested change. Shared architecture, completion criteria, permissions, and local validation commands live in AGENTS.md.
Read only what the task needs
- Release status, development plans, or conflicting sources: source authority.
- DSH APIs, Host/client lifecycle, installation compatibility, or runtime support: DSH compatibility.
- Product behavior: README and usage.
- Architecture and lifecycle: architecture and loader contract.
- HTTP or frontend interfaces: API and frontend integration.
- Message or prompt behavior: DSH message flow and prompt pipeline.
- Prompt Trace, historical provenance, or v3 consumers: Prompt API v3.
- Automated, Host, browser, or external integration acceptance: developer verification.
- Trust boundaries: security and RP secure mode.
These are topic entry points, not a reading checklist. Small edits can use the affected file and nearby evidence directly.
For API changes, distinguish current resources/configuration, runtime assembly, and historical assembly records; also distinguish source-field originals from assembled text. Check the linked contracts before proposing overlapping endpoints or treating one representation as another.
Use č£
é
/ assemble / assembly for prompt preparation in explanations and documentation. Preserve actual code identifiers such as compilePresetForDsh when referring to implementation.