pattern-learn
Use when the user wants to extract a reusable pattern from recent work and store it for future use. "Save this as a pattern", "remember this approach", "learn from this commit".
What this skill does
# pattern-learn
Mine a reusable pattern from concrete code. Store with provenance + searchable description.
## Method
1. **Source.** What's the source — a recent commit? A file? A PR? A code block in chat?
2. **Distil.**
- **Pattern name** — 2-4 words, descriptive
- **Problem it solves** — one sentence
- **Shape** — code template (with placeholders) or structural description
- **When to use** — explicit triggers
- **When NOT to use** — anti-trigger
3. **Capture to memory** with `kind: pattern`. Provenance edges link to the source code.
4. **Index.** Make sure it's discoverable via `mem_search` — descriptive description + tags.
## Output shape
```
Pattern: <name>
Problem: <one sentence>
Shape:
```<language>
<code template with placeholders>
```
When to use:
- <trigger>
- <trigger>
When NOT to use:
- <anti-trigger>
Source: <file:line / commit SHA>
Captured: <memory id> (search via mem_search { query: "<keywords>" })
```
## Rules
- **Patterns are concrete + named.** "Use a factory" is not a pattern. "TestDataFactory.createAccounts(N) returning List<Account>" is.
- **Source is mandatory.** Pattern without origin = mythology.
- **Anti-trigger required.** "Don't use when X" prevents misapplication.
- **Capture is once per pattern.** Don't re-learn the same pattern; update the existing one.
## Anti-patterns
- Generic patterns ("use SOLID")
- Patterns extracted from one-off code (need 2+ instances to be a pattern)
- Patterns without when-NOT-to-use
- Patterns no one will retrieve (description doesn't match how anyone would search)
## When NOT to use
- One-off code — not a pattern
- Pattern already documented elsewhere — link, don't duplicate
- Pre-pattern — code not yet structured enough
## Subagent dispatch
- `Explore` for finding all instances of the pattern (validates it IS a pattern)
- Memory MCP for capture
- Optional `archaeologist` for git context
## Value over native CC
CC won't naturally extract + structure + persist patterns with provenance. The capture-with-discovery-context IS the value. Future `mem_search` retrieves the pattern when relevant.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.