project-memory

Retrieve distilled context from past sessions to guide software tasks.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/eaasxt/Farmhand --skill project-memory-eaasxt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-memory
Source: https://github.com/eaasxt/Farmhand/tree/main/config/skills/project-memory
Command: npx skills add https://github.com/eaasxt/Farmhand --skill project-memory-eaasxt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve relevant context from past sessions before starting implementation. Use when beginning work on a task, when the user describes what to build, when about to write significant code, or when stuck on a problem that may have been solved before.

Core Features & Use Cases

  • Retrieve distilled rules, anti-patterns, and historical context to guide new work.
  • Reuse prior solutions to accelerate implementation and reduce rework.
  • Apply context when user describes features or when starting a bead/task.

Quick Start

To begin, retrieve past-session context before starting implementation.

Frequently Asked Questions about project-memory

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

FAQPage Schema
How do I retrieve context from past development sessions to guide new coding work?

Retrieve context from past development sessions by surfacing distilled rules, anti-patterns, and historical solutions before starting implementation. This coordinates context retrieval, review, and optional deep-dives to guide new software tasks.

When should I reuse past session memory during a software workflow?

Reuse past session memory at task initiation, when user describes features to build, before writing significant code, or when debugging and refactoring. Applying historical context at these points accelerates implementation and reduces rework.

What is the best way to stop repeating solved bugs when starting a new feature?

The best way to stop repeating solved bugs is to retrieve distilled rules and anti-patterns from past sessions. Reviewing historical context surfaces reusable solutions and guardrails before you write new code.

Can I apply historical development context before refactoring existing code?

Yes, you can apply historical development context before refactoring existing code. Retrieving past-session context surfaces relevant guardrails and prior solutions to guide safe refactoring decisions.

What past session knowledge do I need before starting a new software task?

Before starting a new software task, you need distilled rules, anti-patterns, and reusable solutions from past sessions. This historical context retrieval coordinates review and optional deep-dives to guide implementation.