From ds
Reusable development patterns and guides for AI-assisted workflows. Use when asking about CLI design for agents, CLI location, config discovery, vault, commenting standards, snapshot testing, credential storage, Python project architecture, semantic zoom, skill writing, Claude tools, agent teams, extracting deterministic work, plugin authoring and distribution, beads/dolt setup, or showboat/rodney/chartroom agent documentation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ds:recipesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<essential_principles>
references/agent-skills.mdreferences/agentic-cli.mdreferences/beads-dolt-setup.mdreferences/claude-plugin-authoring.mdreferences/claude-tools.mdreferences/cli-location-discovery.mdreferences/comments.mdreferences/extract-deterministic.mdreferences/keyring-credential-storage.mdreferences/python-project-architecture.mdreferences/semantic-zoom.mdreferences/showboat-ecosystem.mdreferences/snapshot-testing.md<essential_principles>
Recipes are standalone reference documents -- each captures a proven pattern or practice for AI-assisted development. They are not step-by-step procedures; they are knowledge you read and apply.
Three categories:
| Category | Recipes | When to Use |
|---|---|---|
| AI Agent Patterns | semantic-zoom, agentic-cli, extract-deterministic, showboat-ecosystem | Designing AI interactions, CLI tools for agents, or agent-driven documentation |
| Development Practices | comments, agent-skills, claude-tools, snapshot-testing | Writing code, skills, or tests in this ecosystem |
| Distribution | claude-plugin-authoring | Packaging skills as installable Claude Code plugins |
| Architecture & Implementation | python-project-architecture, keyring-credential-storage, cli-location-discovery | Structuring Python projects, handling credentials, or CLI location/config discovery |
| Infrastructure & Setup | beads-dolt-setup | Setting up beads issue tracker with Dolt server on macOS |
</essential_principles>
What pattern or practice do you need guidance on?Wait for response before proceeding.
| Response | Reference |
|---|---|
| 1, "cli", "agentic", "safe", "flags", "non-interactive" | references/agentic-cli.md |
| 2, "deterministic", "extract", "script vs prompt" | references/extract-deterministic.md |
| 3, "zoom", "abstraction", "detail level", "semantic" | references/semantic-zoom.md |
| 4, "comment", "intent", "critical", "perf", "anchor" | references/comments.md |
| 5, "skill", "writing", "skill.md", "author" | references/agent-skills.md |
| 6, "tools", "task tool", "claude tools", "subagent", "task management" | references/claude-tools.md |
| 7, "snapshot", "testing", "syrupy", "approval" | references/snapshot-testing.md |
| 8, "architecture", "python project", "cli tool", "structure" | references/python-project-architecture.md |
| 9, "keyring", "credential", "password", "secret" | references/keyring-credential-storage.md |
| 10, "plugin", "marketplace", "distribute", "package", "install" | references/claude-plugin-authoring.md |
| 11, "location", "discovery", "vault", "find_vault", "cwd", "wrong directory", "config init", "bootstrap" | references/cli-location-discovery.md |
| 12, "beads", "dolt", "bd init", "dolt server", "issue tracker setup" | references/beads-dolt-setup.md |
| 13, "showboat", "rodney", "chartroom", "demo", "living docs", "agent documentation" | references/showboat-ecosystem.md |
| Other | Clarify intent, then select appropriate reference |
After identifying the reference, read it and apply its guidance to the user's situation.
<reference_index>
</reference_index>
<success_criteria>
</success_criteria>
npx claudepluginhub durandom/skills --plugin dsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.