Design Patterns
nimadorostkar/Claude-Skills-collectionUse 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.
At a glance
git clone --depth 1 https://github.com/nimadorostkar/Claude-Skills-collection
cp -r Claude-Skills-collection/skills/development/design-patterns ~/.claude/skills/design-patterns
Setup, runtime and requirements describe nimadorostkar/Claude-Skills-collection, the repo this skill ships in.
Also in nimadorostkar/Claude-Skills-collection
View the repoUse when auditing or building accessible interfaces. Covers WCAG 2.2 AA conformance, semantic HTML, keyboard navigation, screen-reader behav...
Use when building an LLM agent that uses tools over multiple steps. Covers tool design, the agent loop, error recovery, termination, human c...
Use when writing project instructions for a coding agent (CLAUDE.md, AGENTS.md, or equivalent). Covers what belongs in them, what does not,...
Use when an agent needs state that survives a session or a context compaction. Covers what to persist, file-based memory, structuring notes...
Use when building Angular applications. Covers standalone components, signals, RxJS discipline, change detection, dependency injection, and...
Use when designing or reviewing an HTTP API. Covers resource modeling, status codes, pagination, idempotency, versioning, error formats, and...
Use when a significant technical decision needs to be recorded. Produces Architecture Decision Records that capture context, options, the de...
Use when defining AWS infrastructure with the CDK. Covers construct design, stack organization, environment configuration, testing infrastru...
Use when reducing cloud spend. Covers finding the actual cost drivers, right-sizing, commitment discounts, storage lifecycle, the hidden cos...
Use when building serverless systems on AWS. Covers Lambda design, cold starts, event-driven patterns with EventBridge and SQS, idempotency,...
Use when designing asynchronous job processing. Covers queue selection, idempotency, retry and backoff policy, scheduling, poison messages,...
Use when testing a trading strategy on historical data. Covers the biases that make a backtest lie, realistic costs, walk-forward validation...