reflection

Included with Lifetime

$97 forever

Self-improving meta-skill that learns from user corrections and updates the TARGET PROJECT's skill files. Only runs when user explicitly says "reflect". Commits all skill updates to Git.

General

What this skill does


# Reflection Skill

## Purpose

Improve future Claude Code sessions by learning from mistakes and user corrections.
Updates skill files in the **target project's** `.claude/skills/` directory.

This is a **meta-skill** - it modifies other skills based on session learnings.

## When to Run (Explicit Triggers Only)

Only activate when the user explicitly requests reflection:

- "reflect"
- "don't do this again"
- "remember this for next time"
- "update your skills"
- "learn from this"

**Never run automatically** - always wait for explicit user trigger.

## Where Rules Go

Rules are written to the **target project's** skill files (NOT the plugin repository):

| Rule Type | Target File |
|-----------|-------------|
| General conventions | `.claude/skills/conventions.md` |
| VILT patterns | `.claude/skills/vilt-patterns.md` |
| Project-specific | `.claude/skills/project-rules.md` |
| Unclear/mixed | `.claude/skills/lessons-learned.md` |

If the target project doesn't have `.claude/skills/`, create it with a starter structure.

## Process

1. **Analyse** the completed session
   - Review conversation for corrections
   - Identify repeated mistakes
   - Note stated preferences

2. **Extract** atomic, durable rules
   - One rule per concept
   - "Do X" or "Never Y" format
   - Date-stamped for tracking

3. **Check** for contradictions
   - Read existing skill files
   - Flag conflicting rules
   - Ask user to resolve

4. **Update** appropriate skill file(s)
   - Append to `## Learned Rules` section
   - Preserve existing formatting
   - Keep changes minimal

5. **Commit** changes separately from code
   - Use semantic commit message
   - Include rule summary in body

## Rule Quality Bar

A rule must be:

- **Durable**: Will apply to future work in this project
- **Actionable**: Clear imperative ("Always X", "Never Y")
- **Specific**: Not too broad or vague
- **Non-contradicting**: Doesn't conflict with existing rules

## Rule Format

```markdown
- [YYYY-MM-DD] RULE_TEXT (source: BRIEF_CORRECTION_CONTEXT)
```

Examples:
```markdown
- [2025-01-09] Always eager load relationships in service methods that return collections (source: booking service review)
- [2025-01-09] Never use axios - use Inertia router instead (source: corrected 3x in dashboard component)
- [2025-01-10] Use FloatingLabelInput for all form fields (source: user preference stated)
```

## Starter Skill Structure

When creating `.claude/skills/` in a new project:

```markdown
# Lessons Learned

## Purpose
Project-specific rules learned from Claude Code sessions.

## Learned Rules
<!-- Reflection appends here -->
```

## Git Commit Format

```
chore(skills): reflect session learnings

- Added: [rule summary]
- Source: [correction context]
- File: .claude/skills/[filename].md
```

## What NOT to Learn

Do not create rules for:
- One-time exceptions
- User's momentary preferences
- Context-specific decisions
- Temporary workarounds

Only learn patterns that should **always** apply.

Files: 1

Size: 3.1 KB

Complexity: 7/100

Category: General

Source: https://github.com/richardhowes/self-improvement-code-quality-plugin/tree/main/code-quality/skills/reflection

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts