agentleFS
Sign inStart free
MeshJSMeshJS/evolving-claude-skills/.claude/skills/journey/SKILL.md

journey

Skill4 starsChanged 9 months agoApache-2.0View on GitHub

Create session learning logs that persist institutional memory across Claude Code sessions.

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create or update session learning logs that persist institutional memory across Claude Code sessions.

    line 12
  2. Very specific:

    Use /journey for a quick standalone capture.

    line 14
  3. Distinctive:

    After completing significant work in a session

    line 19
  4. Distinctive:

    After discovering important patterns or learnings

    line 20
  5. Distinctive:

    After making architectural decisions

    line 21
  6. Distinctive:

    After fixing non-trivial bugs

    line 22
  7. Distinctive:

    When the session contains knowledge worth preserving

    line 23
  8. Distinctive:

    After a session refactoring API authentication:

    line 136

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Journey Skill

Create or update session learning logs that persist institutional memory across Claude Code sessions.

Use /journey for a quick standalone capture. For end-of-session automation that also evolves skills, use /wrap-up instead.

When to Use

Use /journey when:

  • After completing significant work in a session
  • After discovering important patterns or learnings
  • After making architectural decisions
  • After fixing non-trivial bugs
  • When the session contains knowledge worth preserving

Commands

Create New Journey

/journey {title}

Creates a new journey file with a summary of the current session.

List Journeys

/journey --list

Shows all existing journeys.

Read Journey

/journey --read {filename}

Reads a specific journey file.

Show Recent

/journey --recent

Shows the 5 most recent journeys.

Arguments

  • $0 - Journey title describing the main work done

Journey File Format

Journeys are saved to .claude/journeys/ with naming: YYYY-MM-DD-{slug}.md

Template Structure

# Journey: {Title}

**Date:** YYYY-MM-DD
**Tags:** #tag1 #tag2 #tag3

## Summary

1-3 sentences describing what was accomplished and why it matters.

## What Was Done

1. **First major item**
   - Details
   - More details

2. **Second major item**
   - Details

## Key Learnings

- **Learning 1**: Explanation with context
- **Learning 2**: Explanation with context

## Files Changed

| File | Change |
|------|--------|
| `path/to/file.ts` | Brief description |

## Patterns Discovered

### Pattern Name
\`\`\`code
// Example code showing the pattern
\`\`\`

## Decisions Made

| Decision | Rationale |
|----------|-----------|
| Choice made | Why it was made |

## Connected To

- Related skills, files, or future work

Writing Guidelines

Summary

  • Be concise but specific
  • Mention the "why" not just the "what"
  • Future Claude sessions should understand the context

Key Learnings

  • Focus on insights that prevent future mistakes
  • Include code patterns when relevant
  • Explain the "gotcha" moments

Tags

Common tags:

  • #bugfix - Bug fixes
  • #feature - New features
  • #refactor - Code restructuring
  • #api - API-related work
  • #database - Database changes
  • #auth - Authentication/authorization
  • #testing - Test-related work
  • #tooling - Build/dev tooling
  • #performance - Performance work
  • #meta - Claude Code/skills work

Example Usage

After a session refactoring API authentication:

/journey API Auth Refactor

Claude will create .claude/journeys/2026-02-08-api-auth-refactor.md with:

  • Summary of what was refactored
  • Key learnings about the auth flow
  • Files that were changed
  • Patterns discovered (like token refresh handling)

Purpose

Journeys create institutional memory that:

  1. Helps future sessions avoid repeating mistakes
  2. Documents decisions and their rationale
  3. Preserves patterns and best practices
  4. Tracks the evolution of the codebase

Unlike git commits (which track what changed), journeys track why and what was learned.

Download now (ZIP)

  • Other versions9 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 9

    1. butterbase-ai/butterbase-skills★ 535same name
    2. butterbase-ai/butterbase-plugin★ 534same name
    3. me2resh/apexyard★ 532same name
    4. whawkinsiv/solo-founder-skills★ 260same name
    5. whawkinsiv/claude-code-skills★ 258same name
    6. kv0906/pm-kit★ 138same name
    7. tonydzi/second-brain-starter-kit★ 6same name
    8. Thalisu/SKILLS★ 1same name
    9. weg-9000/Orange-pm★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use payments, inbox and 1 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • OpenAISkill

      payments

      Stripe payments integration guidance — native Vercel Marketplace setup, checkout sessions, webhook handling, subscription billing, and the Stripe SDK. Use when implementing payments, subscriptions, or processing transactions.

      Also in 4 projects that use this

    • kv0906Skill

      inbox

      Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

      Also in 3 projects that use this

    • Itsokay-coSkill

      discover

      Automated pattern discovery — finds what correlates with your best and worst sleep nights. Scans workouts, meals, caffeine, tags, gut scores, and timing patterns. Use when the user wants to know what actually affects their sleep.

      Also in 3 projects that use this

  • In this repository2 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free