Skip to content
Skills Library
Programming · Writing

write-design-pattern

/write-design-pattern

Write a design pattern catalog entry. Use when the user asks to document a design pattern, add a pattern to the catalog, or after a refactoring session identifies a reusable pattern.

Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Write a design pattern catalog entry. Use when the user asks to document a design pattern, add a pattern to the catalog, or after a refactoring session identifies a reusable pattern.

Original author description

Write a design pattern catalog entry. Use when the user asks to document a design pattern, add a pattern to the catalog, or after a refactoring session identifies a reusable pattern.

How it works

  1. Steps
  2. Guidelines
Original SKILL.md headings · 50 lines, 337 words
SKILL.md preview
---
name: write-design-pattern
description: Write a design pattern catalog entry. Use when the user asks to document a design pattern, add a pattern to the catalog, or after a refactoring session identifies a reusable pattern.
user-invokable: true
---

# Design Pattern Catalog Entry

Create or update a pattern entry in `design-pattern-catalog/<category>/<pattern-name>.md`.

## Steps

1. **Determine category and name** — use AskUserQuestion if not clear from context. Use kebab-case for the pattern name. Category examples: `commands`, `testing`, `architecture`.

2. **Read existing entries** — check `design-pattern-catalog/` for existing entries to maintain consistency in structure and tone.

3. **Write the entry** — `design-pattern-catalog/<category>/<pattern-name>.md` with these sections:

### `# Pattern Name`

### `## Problem`
State the general principle, not a specific symptom. 1-2 sentences. Specific examples belong in later sections.

### `## Structure` or `## Example`
Choose the appropriate section based on the pattern type:

**Use `## Structure`** for patterns that define collaborating elements (e.g., Command + Assembler):
A table of key elements, their files, and responsibilities. Lead each row with the key element, not the filename.

| Key Element | File | Responsibility |
|-------------|------|---------------|
| ... | `...` | ... |

#### `### Reference implementation` (within Structure)
Bullet list of symbols and their files. Format: `SymbolName` in `path/to/file.py`. No line numbers — they're too unstable.

**Use `## Example`** for patterns about code organization or refactoring, with `### Before` and `### After` subsections showing the concrete change.

### `## Testing Strategies` (when applicable)
One subsection per strategy. Each starts with **What is tested:** naming the specific element under test. Include example references as `path/to/test_file.py` — `test_function_name`.

### `## When to Apply`
Bullet list of conditions where the pattern is appropriate.

### `## Key Principles`
Bullet list of bold-titled principles. These are the memorable takeaways.

## Guidelines

- **No code samples** — reference files and symbols instead; the catalog points to living code, not duplicated snippets
- **No line numbers** — use `path/to/file` — `symbol_name` format for references
- **Lead with the key element** — in tables and bullet lists, put the symbol/concept first, then the file
- **Testing strategies name what is tested** — each strategy starts with the specific class or function under test
- **Concise** — a catalog entry is a reference guide, not a tutorial

Versions

The database has no other skills named write-design-pattern.

Database snapshot: 13.11.2026 · package version 89fbb05fe193 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100design-patterns
    Identifies, implements, and refactors code using standard Design Patterns (GoF + Modern). Use when: design pattern, refactor pattern, strategy pattern, observer pattern, factory pattern, singleton.
  • 100design-pattern-implementation
    Reviews how design patterns are used or misused across the codebase and where patterns would help. Use when evaluating architecture, pattern fit, or over-engineering.
  • 100code-pattern-extractor
    Analyze codebases to identify reusable code patterns, duplications, and implementation patterns for future development. Use when refactoring code, identifying technical debt, finding opportunities for abstraction, or documenting common patterns in a directory or module. Outputs…
  • 100authoring-patterns
    Convert validated playground templates or HTML compositions into reusable pattern files (*.examples.ts) in the pattern library. Use this skill whenever the user wants to save, persist, store, or catalog a template, prototype, composition, or playground result as a reusable…
  • 100python-refactoring
    Python refactoring catalog with 83 patterns covering immutability, class design, control flow, architecture, OO metrics, and Python idioms. Analyze code for smells and apply numbered refactoring patterns with before/after examples. Use when the user invokes /refactor or…
  • 90learn-pattern
    Save a new error pattern to memory for future recognition. When you discover a new error pattern and its fix, use this to remember it. Saved to patterns.yaml, matched during investigate_alert and debug_prod.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.