design-patterns

Use when architecting solutions, identifying recurring problems, or improving code structure with proven patterns.

Security Scan

This is an instruction-only reference card about design patterns; it contains no code, installs, or credential requests and is internally consistent with its stated purpose.

Purpose & Capability

Name and description match the content: the skill is a reference for design/architecture patterns and only contains pattern summaries. Nothing requested (no env vars, binaries, or installs) is unrelated to that purpose.

Instruction Scope

SKILL.md is purely informational (lists patterns, anti-patterns, and short descriptions). It does not instruct the agent to run commands, read files, send data, or access credentials.

Install Mechanism

No install spec or code files are present. As an instruction-only skill, it writes nothing to disk and has minimal attack surface.

Credentials

The skill declares no environment variables, credentials, or config paths — appropriate for a read-only design-patterns reference.

Persistence & Privilege

always is false and the skill does not request elevated persistence or modifications to system/agent-wide configuration. Autonomous invocation is allowed (platform default) but the skill has no operations that would abuse that.

Assessment

This skill is a benign, read-only reference for design patterns and poses minimal technical risk because it has no code, installs, or credential access. Note that the source/homepage are unspecified—if provenance matters to you, verify the publisher or prefer a skill with a known homepage or author. Otherwise it’s safe to use as a static guidance tool; keep in mind recommendations are advisory and should be evaluated against your project context before applying them.

Creational Patterns

• Singleton — one instance globally (use sparingly, hard to test)
• Factory Method — delegate instantiation to subclasses
• Abstract Factory — families of related objects
• Builder — step-by-step complex object construction
• Prototype — clone existing objects

Structural Patterns

• Adapter — incompatible interfaces compatibility
• Decorator — add behavior without modifying class
• Facade — simplified interface to complex subsystem
• Proxy — control access to another object
• Composite — tree structures, treat individual/group uniformly

Behavioral Patterns

• Observer — event subscription/notification
• Strategy — swap algorithms at runtime
• Command — encapsulate actions as objects
• Chain of Responsibility — pass request through handler chain
• Template Method — define skeleton, let subclasses fill in
• State — change behavior when internal state changes
• Iterator — traverse collection without exposing internals

Modern Patterns

• Repository — abstract data layer from business logic
• Unit of Work — batch DB operations into a transaction
• CQRS — separate read and write models
• Saga — distributed transaction management
• Circuit Breaker — prevent cascading failures

Anti-Patterns to Avoid

• God Object — class that knows too much
• Spaghetti Code — no clear structure
• Golden Hammer — using one pattern for everything
• Premature Optimization — optimizing before profiling