cookieMonsterDev {Skill Title}
Ground {domain} answers in the reference files bundled with this skill instead of improvising definitions. Each {item, e.g. "pattern" / "principle"} has a reference file explaining it{, and a folder of runnable examples in popular languages — delete this clause if the skill has no code examples}.
When to Use
- The user names {an item} directly ("show me the {item} in {language}")
- The user describes a problem that maps to {an item} ("{example problem phrasing}")
- The user asks to compare {items} ("{item A} vs {item B}?")
- The user wants existing code or design refactored toward {an item}
Workflow
- Identify the {item(s)} from the user's question using the catalog below.
- Read the reference file at
references/<item>.mdfor the explanation, applicability, trade-offs, and related {items}. - Read the language example at
examples/<item>/<item>.<ext>when the user works in (or asks for) a specific language. Adapt it to their domain rather than pasting the generic example verbatim. (Delete this step if the skill has no code examples.) - Answer with: what the {item} does, when to use it (and when not to), and {code/guidance} adapted to the user's context.
If the user's problem does not match any {item} cleanly, say so — do not force {an item} where a simpler solution fits.
{Domain} Catalog
Group {items} into the categories that make sense for this domain (creational/structural/behavioral, principle/practice, layer/tier, etc.). One table per category.
{Category 1}
{One-line description of what this category of items has in common.}
| {Item} | Intent | Reference |
|---|---|---|
| {Item A} | {What it does, in one line} | references/{item-a}.md |
| {Item B} | {What it does, in one line} | references/{item-b}.md |
{Category 2}
{One-line description of what this category of items has in common.}
| {Item} | Intent | Reference |
|---|---|---|
| {Item C} | {What it does, in one line} | references/{item-c}.md |
Examples
Each {item} has a folder examples/<item>/ with self-contained, runnable examples named <item>.<ext>.
Choosing languages
Only add an example file when the language genuinely supports the skill's concepts — do not ship a file in every language for completeness.
| Skill type | Include | Omit | Rule |
|---|---|---|---|
| OOP paradigm (classes, inheritance, pillars, SOLID) | Python, C++, Java, C#, JavaScript, PHP, Swift | C, Go, Rust | Requires first-class classes. Note idiomatic mappings in reference Language Notes only. |
| Design patterns (GoF, composable techniques) | Python, C, C++, Java, C#, JavaScript, Rust, Go, PHP, Swift | — | Patterns are idiomatically adapted (C emulates with structs/function pointers; Go/Rust use interfaces/traits). |
| Other catalog skills | Pick per item | — | Omit a language when the item is built into the language or has no honest mapping. |
List only the languages your skill actually ships in the table below and in the skill description frontmatter.
| Language | File | Notes |
|---|---|---|
| {Language} | <item>.{ext} |
{Any gap or idiomatic substitution for this language} |
A language file may be absent per {item} when it does not translate meaningfully; the {item}'s reference file notes such gaps and idiomatic alternatives in Language Notes.
Answering Guidelines
- Prefer the language's/domain's idiomatic form over a literal textbook description.
- Mention trade-offs and simpler alternatives, not just the mechanics.
- When comparing {items}, read both reference files and contrast intent, not structure.
- Do not recommend {a commonly-overused item}, or any {item}, as a default; {items} are solutions to specific forces, not style goals.