design-patterns
Agents should invoke this skill when choosing patterns, designing traits/interfaces/components, deciding abstraction boundaries, evaluating dependency injection/callbacks, or comparing implementation approaches in Rust, TypeScript/React, or Django/Python.
Profile →npx skills add waybarrios/opencode-power-pack --skill design-patterns --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Design Patterns Pattern recommendations tailored to common tech stacks. Every pattern recommendation includes when to use it, when to avoid it, and the trade-offs. ## Quick Start ### Choose a Pattern 1. **Identify the problem:** What design challenge are you solving? 2. **Consider the context:** What language? What scale? How often will this change? 3. **Evaluate options:** 2-3 candidate patterns with trade-offs 4. **Recommend:** The best fit for *this specific context* (not the "best pattern in general") **The golden rule:** Patterns are tools, not goals. Use the simplest pattern that solves the problem. If no pattern fits, a plain function or struct is fine. --- ## Rust Patterns ### Newtype Pattern Wrap a primitive to add type safety and domain meaning. ```rust struct UserId(u64); struct OrderId(u64); // Now the compiler prevents mixing up UserId and OrderId fn get_order(user: UserId, order: OrderId) -> Order { ... } ``` **When to use:** When two values have the same underlying type but different meanings. **When to skip:** One-off uses where a type alias suffices. ### Builder Pattern Construct complex objects step by step. ```rust let config = ServerConfig::builder() .host("lo
- Quick Start
- Choose a Pattern
- Rust Patterns
- Newtype Pattern
- Builder Pattern
- Typestate Pattern
- Trait Objects vs Generics
- Error Handling Patterns
- TypeScript / React Patterns
- Compound Components
- Custom Hook Composition
- Discriminated Unions
- State Management Decision Tree
- Django / Python Patterns
What does the design-patterns skill do?
Agents should invoke this skill when choosing patterns, designing traits/interfaces/components, deciding abstraction boundaries, evaluating dependency injection/callbacks, or comparing implementation approaches in Rust, TypeScript/React, or Django/Python.
How do I install it?
Run `npx skills add waybarrios/opencode-power-pack --skill design-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From waybarrios/opencode-power-pack, a repository with 443 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.