I built SpecLock because I was tired of AI coding assistants "remembering" my constraints then ignoring them when inconvenient.

The problem: Claude Code has auto-memory. Cursor has Memory Bank. But memory without enforcement is dangerous. Your AI remembers you use PostgreSQL — then switches to MongoDB because it "seemed better."

SpecLock adds active constraint enforcement: • You: "Don't ever touch the auth files" • AI: Locked • ...5 sessions later... • You: "Add social login" • AI: CONFLICT: This violates your lock. Should I proceed?

Key features: - Semantic conflict detection (synonym + negation, not just keywords) - Auto-guard related files (injects warnings into source code) - Works with Bolt.new, Lovable, Claude Code, Cursor - 19 MCP tools for memory, tracking, enforcement - Free & open source (MIT)

Demo: https://sgroy10.github.io/speclock/ GitHub: https://github.com/sgroy10/speclock npm: npm install speclock