Claude-Mem Architecture Pathfinder

thedotmack/claude-mem

Map feature flows, identify repeated concerns, and propose a unified architecture with source-linked handoff prompts.

Contenu mis à jour:

Dans la collectionClaude-Mem ↗
Voir sur GitHub
npx claude-mem install
116 859Étoiles10 141ForksDernier push du dépôt

À propos de ce Skill

Map feature flows, identify repeated concerns, and propose a unified architecture with source-linked handoff prompts.

Pourquoi ce choix

A reusable workflow from the Claude-Mem project. It is listed separately to explain this task; shared runtime and helper dependencies remain part of the upstream installation. The inherited gallery demonstrates the memory system, not this task’s specific output.

À quoi il sert

  • Understand duplicated systems before deciding how to refactor them.

How the workflow runs

  1. Step 1

    Discover feature boundaries and trace each primary flow with source locations.

  2. Step 2

    Compare within-feature and cross-feature duplication, preserving legitimate specialization.

  3. Step 3

    Write a unified architecture proposal and per-system implementation prompts.

Original pathfinder instructions

Expected result

A feature inventory, Mermaid flowcharts, duplication report, architecture proposal, and handoff prompts.

Original pathfinder instructions

Try a concrete request

  1. Example request

    After installing the required integration, ask your agent:

    Map our notification flows and propose how to consolidate the duplicated delivery paths.

Avant de l’utiliser

  • Source access and a host with delegated code discovery. Produces proposals; implementation is a subsequent task.
  • Use the original upstream files and follow the documented host integration. Model or third-party service usage can carry separate costs.

Agents compatibles

Claude CodeCodex CLI

Sources et références

Les sources originales sont liées ci-dessous. Les pistes pratiques sont des suggestions de la rédaction de SkillHey.