A curated library of 137 production-grade skills for Claude and other AI coding agents.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when fixing a reported bug end to end. Enforces a disciplined sequence — reproduce, write a failing test, fix minimally, verify, prevent recurrence — and blocks the common failure mode of patching symptoms.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when building command-line tools. Covers argument design, exit codes, streams and piping, progress output, configuration precedence, and behavior that respects the shell.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when reviewing a pull request, diff, or branch. Produces severity-ranked findings covering correctness, security, performance, and maintainability, with concrete fixes rather than opinions.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when a bug's cause is unknown. Applies a hypothesis-driven method — reproduce, isolate, instrument, prove — instead of speculative edits, and covers profiler, debugger, and log-based investigation.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when choosing how to structure code for a recurring problem. Covers the patterns that earn their keep, the ones that usually do not, and how to recognize when a pattern is being applied for its own sake.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when the code's vocabulary does not match the business's. Establishes a ubiquitous language, models domain concepts as explicit types, and identifies bounded contexts.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when incrementally modernizing a legacy system without a rewrite. Covers characterization tests, seams, the strangler pattern, and sequencing migrations so the system stays shippable throughout.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when improving the structure of code without changing its behavior. Covers safe refactoring sequences, characterization tests, and knowing when to stop.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when orienting in an unfamiliar codebase. Produces a map of the architecture, entry points, data flow, conventions, and the parts most likely to surprise you — before any code is changed.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when code has grown hard to hold in your head. Applies complexity limits, dependency reduction, and encapsulation to bring functions and modules back under a readable ceiling.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when designing a system or service before implementation. Produces a design covering data model, API surface, failure modes, scaling limits, and the trade-offs that were actually decided.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when defining AWS infrastructure with the CDK. Covers construct design, stack organization, environment configuration, testing infrastructure code, and safe deployment.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when reducing cloud spend. Covers finding the actual cost drivers, right-sizing, commitment discounts, storage lifecycle, the hidden costs of data transfer and logging, and avoiding false savings.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when building serverless systems on AWS. Covers Lambda design, cold starts, event-driven patterns with EventBridge and SQS, idempotency, step functions, and the limits that shape the architecture.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when verifying a system's resilience by injecting controlled failure. Covers hypothesis-driven experiments, blast-radius control, failure injection techniques, and running game days safely.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex needs its repo
Use when building or fixing a delivery pipeline. Covers pipeline structure, caching, test parallelization, deployment strategies, secrets, and making the pipeline fast enough that people do not route around it.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when designing cloud infrastructure. Covers network topology, identity and least privilege, multi-AZ and multi-region trade-offs, managed versus self-hosted decisions, and designing for cost.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when building or debugging container images. Covers multi-stage builds, layer caching, image size, non-root users, signal handling, and the security defaults most Dockerfiles get wrong.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use during and after a production incident. Covers triage, mitigation before diagnosis, communication, and blameless postmortems that produce action items someone actually does.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when deploying to or debugging Kubernetes. Covers workload configuration, resource requests and limits, probes, rollout strategy, networking, and the failure modes that produce CrashLoopBackOff and OOMKilled.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when diagnosing network failures: connection refused, timeouts, TLS errors, DNS problems, and intermittent failures. Covers layer-by-layer isolation and the tools that answer each question.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when instrumenting a system or when an incident cannot be diagnosed from existing telemetry. Covers structured logging, metrics, distributed tracing, SLOs, and alerts that are worth waking someone for.
nimadorostkar/Claude-Skills-collection
Skill Claude CodeCodex
Use when establishing reliability practice. Covers SLOs and error budgets, capacity planning, graceful degradation, load shedding, retry and timeout policy, and the arithmetic of availability.
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: