Ready-to-use Claude Code configuration for Dev and Ops work: global rules, 32 skills, hooks and memory scaffolding. Generic, no personal data, one script to install.
Use when writing infrastructure and DevOps automation shell scripts, with mandatory splitting into functions and files, stdout/stderr contract, idempotence, guardrails on operations that cut off access, log files and exit codes. Triggers on "bash script", "shell script", ".sh", "Makefile", "automate", "deployment…
Use when setting up or reviewing infrastructure and application logs, with a mandatory console presentation format (Ansible contract: TASK, outcomes, PLAY RECAP), stdout/stderr destination, run log, levels, secret redaction, rotation and retention. Covers Ansible, systemd and CI/CD specifics, and points to collecte.md…
Use when a Makefile becomes the entry point of a project, orchestrates several components or repositories, or grows beyond a few targets. Triggers on "Makefile", "make", "make target", "single entry point", "orchestrate the deployment", "make deploy", "make help", "one place to run everything".
Use when designing application and infrastructure metrics, with a mandatory naming convention, choice of type (counter, gauge, histogram), control of label cardinality, RED and USE methods, buckets and quantiles. Complements prometheus-grafana-setup, which covers the tooling. Triggers on "metrics", "measurements"…
Use when setting up distributed tracing with OpenTelemetry, W3C traceparent context propagation, span naming and granularity, attributes, error handling, head and tail sampling, correlation with logs and metrics. Triggers on "trace", "tracing", "distributed traces", "OpenTelemetry", "OTel", "span", "traceparent"…
Use when a Dockerfile or docker-compose.yml is written or modified, or for container hardening. Covers enterprise-grade Docker best practices and DevSecOps security, Dockerfile, multi-stage build, image hardening, secrets, vulnerability scanning, image signing, secured docker-compose. Triggers on "Docker"…
Use when creating, reorganizing or extending an Obsidian vault of technical documentation (cheat sheets, procedures, how-to notes), when the Obsidian graph is unreadable, wrongly colored or rearranges itself on every opening, or when Claude must find the user's usual methods in their notes. Triggers on "Obsidian"…
Use when a README, a doc or a presentation needs a readable architecture diagram with the tools' logos, in the draw.io style, or when a Mermaid diagram is considered too technical or unclear. Triggers on "schematic", "diagram", "architecture", "draw.io", "logos", "README image", "simpler diagram".
★not rated 2 yesterdayA74 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: