1 files changed, 0 insertions, 51 deletions
diff --git a/skills/memory-map.md b/skills/memory-map.md
deleted file mode 100644
index b8c0f83..0000000
--- a/skills/memory-map.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-name: memory-map
-description: Maintain and query the persistent memory map at /memory/map.json for Agando/DarkMoto Systems.
-category: system
-tags: memory, persistence, context, map, agando
----
-
-## Purpose
-Keep a living index of projects, infrastructure, preferences, active issues, and session history so the AI never asks Agando to repeat himself.
-
-## File Location
-- `/memory/map.json` — primary memory map
-- `/memory/index.json` — session index (auto-generated)
-
-## Workflow
-
-### 1. Read Before Acting
-At the start of any session or when context is unclear:
-```bash
-read_file("memory/map.json")
-```
-
-### 2. Update After Significant Work
-After any task that changes status, fixes an issue, or adds knowledge:
-```bash
-# Read current map
-read_file("memory/map.json")
-
-# Modify relevant section(s)
-# Write back
-write_file("memory/map.json", <updated_json>)
-```
-
-### 3. Add Session Link
-Append to `recent_sessions` (keep last 10):
-```json
-{"date": "YYYY-MM-DD", "file": "memory/YYYY-MM-DD.json", "summary": "..."}
-```
-
-## Map Structure
-- `projects` — WebX11, clients, personal builds, stores
-- `infrastructure` — security stack, backup systems, constraints
-- `preferences` — communication style, UI needs (#00ff88, 48px touch targets)
-- `active_issues` — open tasks, blockers, manual steps required
-- `recent_sessions` — quick links to session logs
-
-## Rules
-- NEVER ask Agando for info already in the map.
-- If info is stale or wrong, update it immediately.
-- Use `session_save()` after complex tasks to populate index.json.
-- Keep `active_issues` accurate — remove resolved items.
-\ No newline at end of file