eshp--deep-dream

ESHP Deep Dream

ESHP (electric sheep pen) is a codebase level memory graph for maintaining information about the current project.

This skill is for doing deep maintenance on the graph, ensuring it is up to date and that the relationships are mapped correctly.

Important: prefer eshp recall <slug> and eshp scan <topic> to reading memory files directly.

Procedure

Ensure the git state is clean so we can commit the updated memory files.

Understand the current memory graph:

• eshp rels - list all relationships
• eshp tags - list all tags
• eshp summarise - list recently created and recalled memories

Understand the current codebase:

• High level goals
• Features and capabilities
• Developer guidance and lifecycle
• Any upcoming or planned features
• Issues, refactoring opportunities, etc

Ensure the memory graph is an accurate reflection of the project and covers planned and existing features, dev lifecycle, and crucial knowledge. Key question: if the code was removed could we recreate the project from the memory graph alone?

Maintain memory accuracy:

• use eshp scan <query> and eshp recall <slug> to check for accuracy
• use eshp tags and look for opportunities to consolidate similar tags
• use eshp rels and look for opportunities to consolidate similar relationships
• add any missing entries
• add any missing tags or relationships

When writing or updating notes, follow the eshp--write-node skill.

Run eshp diagnose and treat the output as a work queue. Address issues in priority order:

1. Dangling edges (broken links — fix immediately)
2. Orphaned nodes (unconnected — link or delete)
3. Notes with ## in body (format violation — split into separate notes)
4. Bloated notes (too long — split; the facts inside belong in separate nodes)

Once done commit the updated memory graph files as a new deep-dream commit.

Improve relationships

• Rels like 'related' and 'linked-to' don't provide much semantic meaning. Prefer specific relationships like 'caused', 'blocks', 'implements', 'waiting-for'.
• Do not use generic relationships if a more specific one exists. Replace vague names with precise ones as meaning becomes apparent.