mikeparcewski/memory
skills/mem/SKILL.md
Memory storage, recall, and lifecycle management for maintaining context across sessions. This skill should be used when the user asks to "remember this", "store a decision", "recall what we did", "find past context", "save for later", "what did we learn", "what did we decide", or mentions persisting knowledge, decisions, or learnings. Use when: - "remember this for next time" - "store this decision" - "what did we do before" - "recall past context" - "save this pattern"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden memoryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 9:17 AM15.3s4 files scanned
SKILL.md
- name:
- memory
- description:
- |
Memory Management Skill
This skill provides guidance on effectively using Claude's memory system to persist knowledge, decisions, and learnings across sessions.
When to Use This Skill
- After completing significant work that yielded learnings
- When making architectural or design decisions
- When encountering and solving bugs that might recur
- When establishing patterns or preferences
- When needing to recall past context
Core Concepts
Memory Types - Choose the right type for durability:
episodic: What happened (90-day TTL)procedural: How to do things (permanent)decision: Choices and rationale (permanent)preference: User/project preferences (permanent)
Scope - Where memories live:
core: Global, cross-projectproject: Specific to current project
Importance - Affects decay rate:
high: 2x TTL multipliermedium: Standard TTLlow: 0.5x TTL multiplier
Quick Reference
In v9 the mem:* commands are removed. All memory operations go through wicked-brain:memory directly.
| Task | How |
|------|-----|
| Store a decision | Skill(skill="wicked-brain:memory", args="store \"...\" --type decision") |
| Find past context | Skill(skill="wicked-brain:memory", args="recall \"query\"") |
| Check memory health | Skill(skill="wicked-brain-status", args="") |
| Archive old memory | Skill(skill="wicked-brain:forget", args="mem_id") |
On-Demand Recall
Memories are pulled on-demand, not preloaded. When context is needed:
- Auto-triggered: Prompts like "why did we decide..." auto-search memories
- Manual fallback: If no context is injected and you need history, use:
Skill(skill="wicked-brain:memory", args="recall \"query terms\"")
When to proactively recall:
- User asks about past decisions but no memory was injected
- Task relates to previous work in the project
- Making decisions that should reference past rationale
- Debugging an issue that might have been solved before
Workflow Guides
| Task | Guide | |------|-------| | What to store and how to structure it | Storing Decisions | | Effective search and filtering | Effective Recall | | Managing memory lifecycle | Memory Lifecycle |
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026