Expert skills for etcd-druid development: plan/implement workflow with gated Gates, TDD, debugging, API change guidance, e2e testing, code review, domain glossary, agent briefs, and reference. Inspired by the Superpowers plugin system.
Use when writing GitHub issues for etcd-druid, etcd-backup-restore, or etcd-wrapper — generates durable, behavioral issue descriptions with complete acceptance criteria. Use for new issues, not for existing well-formed ones.
Use for any etcd-druid API field addition or modification — CEL validation, kubebuilder markers, two-commit generate workflow, CRD tests. Not for controller or test-only work.
Use before plan when the user asks for a feature or significant change — explores intent, requirements, and constraints before planning. Do not use for bug fixes with clear reproduction or trivial one-file changes.
Use when something is failing — test failures, reconciliation loops, backup errors, build failures in etcd-druid, etcd-backup-restore, or etcd-wrapper. Do not use for feature design or how-to questions.
Use when writing a new Druid Enhancement Proposal or reviewing an existing DEP draft for quality and completeness. Guides section-by-section authoring with best-practice heuristics, or scores existing drafts against a 25-dimension / 50-point rubric covering cross-repo impact (etcd-druid, etcd-backup-restore, etcd-wrapper) plus adjacent systems (VPA, Cluster Autoscaler, PDB), public-API discipline, terminology precision, controller boundaries, feature gates, breaking changes, CEL validations, metrics design, and Mermaid diagrams.
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ecosystem: etcd-druid · etcd-backup-restore · etcd-wrapper
Website: seshachalam-yv.github.io/etcd-druid-skills
A Claude Code plugin that makes your AI coding agent a capable etcd-druid contributor — not just a code writer, but a workflow-following engineer who knows the two-commit rule, picks the right test framework per repo, protects generated files, and won't push without your approval.
Without this plugin, an LLM working in etcd-druid makes the same mistakes every new contributor makes: editing zz_generated_* files, using the wrong test framework, skipping make revendor, placing CEL validation in the wrong file, jumping straight to code without a plan. This plugin encodes 15+ known footguns and a gated plan → implement → review workflow so those mistakes never reach your PR.
When you start a session in any etcd-druid, etcd-backup-restore, or etcd-wrapper checkout, the plugin auto-detects the repo, reads the relevant docs/development/ guide, and activates the right skills — no configuration required.
| Generic Claude on an API change task | With etcd-druid-skills |
|---|---|
|
|
| Requirement | Minimum |
|---|---|
| Claude Code | 1.x (any version with plugin support) |
| Claude model | claude-sonnet-4-5 or newer (Haiku floor was raised; Opus recommended for plan and implement) |
| Repos supported | gardener/etcd-druid, gardener/etcd-backup-restore, gardener/etcd-wrapper |
| OS | macOS, Linux (anywhere Claude Code runs) |
The plugin auto-detects which repo you are in at session start. It does not modify any repo files — all changes are in your Claude Code session context.
/plugin marketplace add seshachalam-yv/etcd-druid-skills
/plugin install etcd-druid-skills@seshachalam-yv-etcd-druid-skills
{
"extraKnownMarketplaces": {
"seshachalam-yv-etcd-druid-skills": {
"source": {
"source": "github",
"repo": "seshachalam-yv/etcd-druid-skills"
}
}
},
"enabledPlugins": {
"etcd-druid-skills@seshachalam-yv-etcd-druid-skills": true
}
}
Start a session in an etcd-druid checkout. You should see the orientation context (component overview, active repo, branch info). Then:
/etcd-druid:reference
If the reference card appears with your current git state, you're set.
/plugin marketplace update seshachalam-yv-etcd-druid-skills
npx claudepluginhub seshachalam-yv/etcd-druid-skills --plugin etcd-druid-skillsComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Browser automation and end-to-end testing MCP server by Microsoft. Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.