memory-bank-mcp: Instructions file for GitHub Copilot

Memory Bank — Copilot Instructions

Auto-generated by Memory Bank extension. Edit freely to customize.

This project uses the Memory Bank MCP server to persist context across AI sessions. You have access to Memory Bank MCP tools. USE THEM — they are not optional.

Mandatory Workflow (every task, no exceptions)

START of task

1. ⚠️ CALL THIS FIRST. Call get_instructions MCP tool to learn the full tool catalog and workflow (once per session)
2. Call get_context_digest to load current project state (tasks, issues, progress, decisions)
3. Read system-patterns.md (via read_memory_bank_file) to understand project conventions, architecture patterns, and coding standards
4. Use graph_search to find relevant knowledge graph entities

DURING task

1. Call track_progress after completing milestones
2. Call log_decision when making architectural/design choices
3. Call add_session_note for observations, blockers, or questions

END of task

1. Call update_active_context with updated tasks, issues, and next steps
2. Call track_progress with a final summary of what was accomplished
3. Update knowledge graph entities if project structure changed
4. Update system-patterns.md if new patterns, architecture, or conventions were introduced

If Memory Bank contains placeholder text

If any core file contains [Project description] or [Task 1] style placeholders, the Memory Bank has never been initialized. You MUST populate all core files with real project data from the workspace before doing any other work.

First-Time Initialization Procedure

When placeholder content is detected:

1. Scan workspace: package.json, README, config files, source directories
2. write_memory_bank_file for: product-context.md, active-context.md, progress.md, decision-log.md, system-patterns.md
3. graph_upsert_entity + graph_add_observation + graph_link_entities for major components
4. add_session_note → "Memory Bank initialized from workspace analysis."