Memory/feedback rules documented but not consistently applied during sessions

Problem

Claude Code has a persistent memory system where user feedback and rules are stored across sessions. However, the agent repeatedly violates documented rules even when they exist in memory, requiring the user to correct the same mistakes multiple times.

Examples of repeated violations

1. npx tsc --noEmit rule - Memory explicitly says CRITICAL: Always use npx tsc --noEmit. Violated 3 times across sessions, generating 279+ .js artifacts each time.

1. Jira defect field defaults - Memory documents that severity=low and businessImpact=no should always be used. Agent set severity=high and businessImpact=high on two defects in the same session.

1. Jenkins report extraction - Memory contains the complete procedure. Agent still fumbled through multiple failed attempts before getting it right.

1. Commit hygiene - Memory says never commit MCP/Claude infrastructure files. Agent included unrelated MCP tool changes in a project commit.

1. Zephyr folder paths - Memory documents the exact folder convention. Agent guessed a wrong path instead of checking where sibling test cases are located.

Root cause

The agent optimizes for speed over correctness. It rushes to execute actions without first consulting its own memory/feedback system.

Expected behavior

Before executing any action that has documented rules, the agent should consult its memory system and follow the documented procedures exactly.

Impact

The user has to repeatedly correct the same mistakes, which erodes trust and wastes time.