Remember

Save key learnings, decisions, and gotchas into foxctl memory with typed classification.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill remember-joshka0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Remember
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-condensed/remember
Command: npx skills add https://github.com/joshka0/foxctl --skill remember-joshka0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remember helps you stop losing important insights—like gotchas, decisions, and recurring patterns—by saving them into foxctl memory so your future work can build on them.

Core Features & Use Cases

  • Memory capture: Store a single piece of knowledge (an insight) with a clear summary and label.
  • Typed organization: Categorize insights as gotcha, decision, pattern, or context to make retrieval more accurate.
  • Operator-friendly workflow: Use a simple prompt-style command to turn observations during development into persistent memory.

Quick Start

Save an architectural gotcha to memory by calling: /remember "The auth middleware must be registered before route handlers".

Frequently Asked Questions about Remember

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture engineering decisions and gotchas so they persist across sessions?

You can capture engineering decisions and gotchas by saving them into foxctl memory, which stores key learnings as persistent entries to preserve workflow context across development sessions.

What's the best way to store recurring development patterns for later retrieval?

Storing recurring development patterns requires writing memory entries with a specified content payload, using typed classification to distinguish gotchas, decisions, patterns, and context for accurate later retrieval.

Can I categorize saved knowledge entries by type like gotcha or pattern?

Yes, saved knowledge entries support typed classification, allowing you to categorize insights as gotcha, decision, pattern, or context to make retrieval more accurate during future development workflows.

How do I save an architectural insight to memory during a development workflow?

To save an architectural insight during development, use a simple prompt-style command to turn your observation into a persistent memory entry with a clear summary and label.

Why does important background context get lost between persistent sessions?

Background context gets lost between persistent sessions when it is not actively recorded, but saving key learnings into foxctl memory ensures important architectural choices and background context persist for future work.