io.github.sgroy10/speclock

Official

by sgroy10 · JavaScript

AI Constraint Engine — enforces CLAUDE.md and .cursorrules as laws. 51 MCP tools.

Model Context Protocol (MCP) Server: io.github.sgroy10/speclock

The io.github.sgroy10/speclock MCP server is described as an AI Constraint Engine that enforces project rules defined in CLAUDE.md and .cursorrules. It includes 51 MCP tools and is positioned to prevent AI coding tools from crossing constraints already written in those files.

🛠️ Key Features

AI constraint enforcement
Uses CLAUDE.md and .cursorrules as rule sources
51 MCP tools
Topics include: mcp, mcp-server, ai-safety, ai-guardrails, constraint-enforcement, pre-commit

🚀 Use Cases

Constrain Claude Code and Cursor behavior to match CLAUDE.md and .cursorrules
Apply guardrails across AI coding tools (listed: Claude Code, Cursor, Codex, Windsurf)

⚡ Developer Benefits

Centralizes “what not to change” in CLAUDE.md and .cursorrules
Reduces deviations by enforcing written project constraints through MCP tools

⚠️ Limitations

Enforcement is tied to the specified rules files mentioned (CLAUDE.md, .cursorrules); other files are not described in the provided excerpt

Topics

ai-codingclaude-codecursordeveloper-toolsmcpmcp-serverai-safetycode-qualityconstraint-enginepre-commitagents-mdcopilotwindsurfai-guardrailsclaude-code-pluginconstraint-enforcementcodex-plugincursor-plugingemini-cli-extension

README.md39 KBView on GitHub

SpecLock

Rules files tell AI what not to change.
SpecLock enforces them.

Stop Claude Code, Cursor, Codex, Windsurf, and other AI coding tools from crossing project constraints you already wrote in CLAUDE.md, AGENTS.md, and .cursorrules.

CI MCP 51 tools

Install · See a block · Claude Code plugin · Website · Saves Wall

Why another rules tool? Rules files are context. They can be forgotten, diluted, or overridden during a long coding session. SpecLock turns those rules into checks that run before edits, shell commands, and commits.

See the difference

text

CLAUDE.md:  Never modify the authentication system.

You:        Add social login to the login page.

Without SpecLock
Claude:     I'll update the auth flow and add an OAuth provider...

With SpecLock (strict mode)
SpecLock:   BLOCKED — conflicts with "Never modify the authentication system"
            Match: login → auth → authentication
            The action was denied before the files changed.

SpecLock uses semantic conflict detection rather than simple keyword matching. It catches indirect actions such as “clean up old patient data,” “streamline checkout,” or “temporarily disable MFA” when they violate an active constraint.

60-second setup

Run this from the project you want to protect:

bash

npx speclock@latest protect          # reads existing AI rule files; advisory by default
npx speclock@latest doctor           # confirms rules, hooks, and integration

When the advisory output looks right, enable blocking:

bash

npx speclock@latest protect --strict

No account is required. SpecLock runs locally by default, and advisory mode never blocks a change.

Install as a Claude Code plugin

Inside Claude Code, run:

text

/plugin marketplace add sgroy10/speclock
/plugin install speclock@speclock-marketplace

Then protect the current project once:

bash

npx speclock@latest protect          # warnings only
npx speclock@latest protect --strict # block confirmed conflicts

The plugin automatically starts SpecLock's MCP server and checks Claude Code Write, Edit, and Bash actions before execution. It includes all 51 MCP tools and works alongside your existing CLAUDE.md.

Install on other coding agents

SpecLock is packaged for multiple agent ecosystems, but the enforcement level depends on what each host exposes:

Platform	Install/discovery path	Protection level
Claude Code	Native marketplace plugin above	Native pre-action checks for `Write`, `Edit`, and `Bash`
Gemini CLI	Install this repository as a Gemini extension	MCP-assisted checks plus project context
Cursor	Agent Plugin / Cursor marketplace package	MCP-assisted checks plus rules
Codex	Repository Codex plugin in `plugins/speclock`	MCP-assisted checks plus `$speclock-guardrails` skill
GitHub Copilot CLI	Add this repository as a plugin marketplace	MCP-assisted checks plus bundled plugin context
Cline	MCP server; curated marketplace submission in progress	MCP-assisted checks
Windsurf	`speclock mcp install windsurf`	MCP-assisted checks plus rules
Any Git client or CI	`speclock protect`	Commit/CI enforcement independent of the coding agent

MCP-assisted means the agent can call SpecLock before acting; it does not guarantee interception. Use speclock protect --strict and CI when a constraint must be enforced regardless of the client.

SpecLock has a different job from memory and skills: memory recalls context, skills provide procedures, and SpecLock verifies planned actions against explicit constraints. It reduces constraint drift; it cannot guarantee factual correctness or make a model hallucination-free.

Repository installs supported by current clients:

bash

gemini extensions install https://github.com/sgroy10/speclock
copilot plugin marketplace add sgroy10/speclock
copilot plugin install speclock@speclock-marketplace

What you get

Capability	What it does
Pre-action checks	Reviews Claude Code writes, edits, and shell commands before they run
Semantic constraints	Detects synonyms, euphemisms, compound requests, and indirect violations
Git enforcement	Adds a second guard at commit time
Advisory and strict modes	Start with warnings; opt in to hard blocking when ready
Audit trail	Records decisions in a tamper-evident HMAC chain
MCP integration	Exposes 51 tools to Claude Code, Cursor, Codex, Windsurf, and Cline
Shareable save receipts	Shows what SpecLock prevented with `speclock wins`

Proven in the open

10,000+ npm downloads before the native Claude Code plugin release.
1,043 automated tests across 24 suites, including adversarial conflicts, false-positive cases, patch analysis, enforcement, auth, and compliance.
MIT licensed and inspectable end to end.
Local-first defaults with optional remote features clearly separated.

Commands you will use most

bash

speclock protect                      # extract constraints and install project protection
speclock protect --strict             # enable hard enforcement
speclock doctor                       # verify the complete setup
speclock check "action description"   # preview whether an action conflicts
speclock add-lock "rule"              # add a constraint explicitly
speclock list-locks                    # inspect active constraints
speclock enforce hard|advisory         # switch enforcement mode
speclock mcp install <client>          # Claude Code, Cursor, Windsurf, Cline, or Codex
speclock wins                          # create a shareable save receipt

Full reference: npx speclock@latest help

New in v5.8.0

Portable Agent Plugin packaging for Cursor-compatible discovery.
Gemini CLI extension packaging with MCP startup and constraint context.
Codex plugin with a $speclock-guardrails skill and pinned MCP server.
GitHub Copilot CLI compatibility through the repository marketplace.
Explicit per-platform enforcement labels: native hook, MCP-assisted, or Git/CI.

More links and project badges

Smithery · Badge gallery · Sandeep Roy

The Problem

AI coding tools have memory now. Claude Code has CLAUDE.md. Cursor has .cursorrules. Mem0 exists.

But memory without enforcement is useless.

Your AI remembers you use PostgreSQL — then switches to MongoDB because it "seemed better." Your AI remembers your auth setup — then rewrites it while "fixing" a bug. You said "never touch the payment logic" 3 sessions ago — the AI doesn't care.

Remembering is not respecting. No existing tool stops the AI from breaking what you locked.

How It Works

You set constraints. SpecLock enforces them — across sessions, across tools, across teams.

code

speclock lock "Never modify auth files"           → auto-guards src/auth/*.ts
speclock lock "Database must stay PostgreSQL"      → catches "migrate to MongoDB"
speclock lock "Never delete patient records"       → catches "clean up old data"
speclock lock "Don't touch the payment flow"       → catches "streamline checkout"

The semantic engine doesn't do keyword matching. It understands:

"clean up old data" = deletion (euphemism detection)
"streamline checkout" = modify payment flow (synonym + concept mapping)
"temporarily disable logging" = disable logging (temporal evasion detection)
"Update UI and also drop the users table" = hidden violation (compound splitter)

And it knows what's safe:

"Enable audit logging" when the lock says "Never disable audit logging" → no conflict (intent alignment)

Quick Start by Platform

Bolt.new / Aider / Any npm Platform

bash

npx speclock setup --goal "Build my app" --template nextjs

Creates SPECLOCK.md, injects rules into package.json, generates .speclock/context/latest.md. The AI reads these automatically.

Claude Code

Install the plugin using the commands above. For MCP-only setup without the plugin hooks, add this to .mcp.json:

json

{
  "mcpServers": {
    "speclock": {
      "command": "npx",
      "args": ["--yes", "speclock@5.8.0", "serve", "--project", "."]
    }
  }
}

Cursor / Windsurf / Cline

Same config — add to .cursor/mcp.json or equivalent.

Lovable (No Install)

Go to Settings → Connectors → New MCP server
Enter URL: https://speclock-mcp-production.up.railway.app/mcp
Paste project instructions into Knowledge

Why SpecLock Over Alternatives?

	Claude Memory	Mem0	`.cursorrules`	SpecLock
Remembers context	Yes	Yes	Manual	Yes
Blocks the AI from breaking things	No	No	No	Yes
Semantic conflict detection	No	No	No	Yes — covered by adversarial tests
Tamper-proof audit trail	No	No	No	HMAC-SHA256 chain
Hard enforcement (AI cannot proceed)	No	No	No	Yes
SOC 2 / HIPAA compliance exports	No	No	No	Yes
Encrypted storage (AES-256-GCM)	No	No	No	Yes
RBAC + API key auth	No	No	No	4 roles
Policy-as-Code DSL	No	No	No	YAML rules
Works on Bolt.new, Lovable, etc.	No	No	No	Yes

Other tools remember. SpecLock enforces.

Semantic Engine

Not keyword matching — semantic analysis with an optional Gemini Flash hybrid for grey-zone and cross-domain cases. The repository includes adversarial, false-positive, question-framing, patch-gateway, and diff-analysis test suites.

Category	Detection	Example
Direct violations	100%	"Delete the auth module" vs lock "Never modify auth"
Euphemistic attacks	100%	"Clean up old patient data" = deletion
Temporal evasion	100%	"Temporarily disable MFA" = disable MFA
Dilution attacks	100%	Violation buried in multi-part request
Compound sentences	100%	"Update UI and also drop users table"
Synonym substitution	100%	"Sunset the API" = remove the API
Payment brand names (11 gateways)	100%	"Add Razorpay" / "Implement PayU" vs "Must use Stripe"
Salary/payroll cross-vocab	100%	"Optimize salary" vs "Payroll records locked"
Safety system bypass	100%	"Disable safety interlock" = bypass safety
Unknown domains (via Gemini)	100%	Gaming, biotech, aerospace, music, legal
Safe actions (true negatives)	0% FP	"Change the font" correctly passes auth locks

Under the hood: 65+ synonym groups · 80+ euphemism mappings · domain concept maps (fintech, e-commerce, IoT, healthcare, SaaS, payments, gaming, telecom, government) · intent classifier · compound sentence splitter · temporal evasion detector · verb tense normalization · UI cosmetic detection · safe-intent patterns · passive voice parsing — all in pure JavaScript. Gemini Flash hybrid for grey-zone cases ($0.01/1000 checks).

Hard Enforcement

Two modes:

code

Advisory (default):  AI gets a warning, decides what to do
Hard mode:           AI is BLOCKED — MCP returns isError, AI cannot proceed

bash

speclock enforce hard   # Enable hard mode — violations above threshold are blocked

Configurable threshold — default 70%. Only HIGH confidence conflicts block.
Override with reason — speclock override <lockId> "JIRA-1234: approved by CTO" (logged to audit trail)
Auto-escalation — lock overridden 3+ times → auto-flags for review

Enterprise Security

API Key Auth + RBAC

bash

speclock auth create-key --role developer --name "CI Bot"
# → sk_speclock_a1b2c3... (shown once, stored as SHA-256 hash)

Role	Read	Write Locks	Override	Admin
`viewer`	Yes	—	—	—
`developer`	Yes	—	With reason	—
`architect`	Yes	Yes	Yes	—
`admin`	Yes	Yes	Yes	Yes

AES-256-GCM Encryption

bash

export SPECLOCK_ENCRYPTION_KEY="your-secret"
speclock encrypt   # Encrypts brain.json + events.log at rest

PBKDF2 key derivation (100K iterations). Authenticated encryption. HIPAA 2026 compliant.

HMAC Audit Chain

Every event gets an HMAC-SHA256 hash chained to the previous event. Modify anything — the chain breaks.

bash

$ speclock audit-verify

✓ Audit chain VALID — 247 events, 0 broken links, no tampering detected.

Compliance Exports

bash

speclock export --format soc2    # SOC 2 Type II report (JSON)
speclock export --format hipaa   # HIPAA PHI protection report
speclock export --format csv     # All events for auditor spreadsheets

Policy-as-Code

Declarative YAML rules for organization-wide enforcement:

yaml

# .speclock/policy.yml
rules:
  - name: "HIPAA PHI Protection"
    match:
      files: ["**/patient/**", "**/medical/**"]
      actions: [delete, modify, export]
    enforce: block
    severity: critical

  - name: "No direct DB mutations"
    match:
      files: ["**/models/**"]
      actions: [delete]
    enforce: warn
    severity: high

Import and export policies between projects. Share constraint templates across your organization.

REST API v2

Real-time constraint checking, patch review, and autonomous systems:

bash

# Patch Gateway (v5.1)
POST /api/v2/gateway/review        { description, files, useLLM }

# AI Patch Firewall (v5.2)
POST /api/v2/gateway/review-diff   { description, files, diff, options }
POST /api/v2/gateway/parse-diff    { diff }

# Typed constraint checking
POST /api/v2/check-typed    { metric, value, entity }
POST /api/v2/check-batch    { checks: [...] }

# SSE streaming (real-time violations)
GET  /api/v2/stream

# Spec Compiler
POST /api/v2/compiler/compile  { text, autoApply }

# Code Graph
GET  /api/v2/graph/blast-radius?file=src/core/memory.js
GET  /api/v2/graph/lock-map
POST /api/v2/graph/build

51 MCP Tools

Memory — goal, locks, decisions, notes, deploy facts

Tool	What it does
`speclock_init`	Initialize SpecLock in project
`speclock_get_context`	Full context pack (the key tool)
`speclock_set_goal`	Set project goal
`speclock_add_lock`	Add constraint + auto-guard files
`speclock_remove_lock`	Soft-delete a lock
`speclock_add_decision`	Record architectural decision
`speclock_add_note`	Add pinned note
`speclock_set_deploy_facts`	Record deploy config

Enforcement — conflict detection, hard blocking, overrides

Tool	What it does
`speclock_check_conflict`	Semantic conflict check against all locks
`speclock_set_enforcement`	Switch advisory/hard mode
`speclock_override_lock`	Override with reason (audit logged)
`speclock_override_history`	View override audit trail
`speclock_semantic_audit`	Analyze git diff against locks
`speclock_detect_drift`	Scan for constraint violations
`speclock_audit`	Audit staged files pre-commit

Tracking & Sessions — changes, events, session continuity

Tool	What it does
`speclock_session_briefing`	Start session + full briefing
`speclock_session_summary`	End session + record summary
`speclock_log_change`	Log a change with files
`speclock_get_changes`	Recent tracked changes
`speclock_get_events`	Full event log (filterable)
`speclock_checkpoint`	Git tag for rollback
`speclock_repo_status`	Branch, commit, diff summary

Intelligence — suggestions, health, templates, reports

Tool	What it does
`speclock_suggest_locks`	AI-powered lock suggestions
`speclock_health`	Health score + multi-agent timeline
`speclock_apply_template`	Apply constraint template
`speclock_report`	Violation stats + most tested locks

Enterprise — audit, compliance, policy, telemetry

Tool	What it does
`speclock_verify_audit`	Verify HMAC chain integrity
`speclock_export_compliance`	SOC 2 / HIPAA / CSV reports
`speclock_policy_evaluate`	Evaluate policy rules
`speclock_policy_manage`	CRUD for policy rules
`speclock_telemetry`	Opt-in usage analytics

Typed Constraints — numerical, range, state, temporal (v5.0)

Tool	What it does
`speclock_add_typed_lock`	Add typed constraint (numerical/range/state/temporal)
`speclock_check_typed`	Check proposed values against typed constraints
`speclock_list_typed_locks`	List all typed constraints
`speclock_update_threshold`	Update typed lock thresholds

Spec Compiler & Code Graph — NL→constraints, dependency analysis (v5.0)

Tool	What it does
`speclock_compile_spec`	Compile natural language into structured constraints
`speclock_build_graph`	Build/refresh code dependency graph
`speclock_blast_radius`	Calculate blast radius of file changes
`speclock_map_locks`	Map locks to actual code files

Patch Gateway & AI Patch Firewall — change review, diff analysis (v5.1/v5.2)

Tool	What it does
`speclock_review_patch`	ALLOW/WARN/BLOCK verdict for proposed changes
`speclock_review_patch_diff`	Diff-native review with signal scoring + unified verdict
`speclock_parse_diff`	Parse unified diff into structured changes (debug/inspect)

Universal Rules Sync & Incident Replay — cross-tool sync, session replay (v5.3)

Tool	What it does
`speclock_sync_rules`	Sync constraints to Cursor, Claude, Copilot, Windsurf, Gemini, Aider, AGENTS.md
`speclock_list_sync_formats`	List all available sync formats
`speclock_replay`	Replay a session's activity — what AI tried and what was caught
`speclock_list_sessions`	List available sessions for replay
`speclock_drift_score`	0-100 project integrity metric — how much AI deviated from intent
`speclock_coverage`	Lock Coverage Audit — find unprotected code areas
`speclock_strengthen`	Grade locks and suggest stronger versions

CLI

bash

# Setup
speclock setup --goal "Build my app" --template nextjs

# Constraints
speclock lock "Never modify auth files" --tags auth,security
speclock lock remove <id>
speclock check "Add social login"              # Test before doing

# Enforcement
speclock enforce hard                          # Block violations
speclock override <lockId> "JIRA-1234"         # Override with reason

# Audit & Compliance
speclock audit-verify                          # Verify HMAC chain
speclock export --format soc2                  # Compliance report
speclock audit-semantic                        # Semantic pre-commit

# Git
speclock hook install                          # Pre-commit hook
speclock audit                                 # Audit staged files

# Templates
speclock template apply safe-defaults          # Vibe coding seatbelt (5 locks)
speclock template apply solo-founder           # Indie builder essentials (3 locks)
speclock template apply hipaa                  # HIPAA healthcare (8 locks)
speclock template apply api-stability          # API contract protection (6 locks)
speclock template apply nextjs                 # Next.js constraints
speclock template apply security-hardened      # Security hardening

# Sync to AI tools
speclock sync --all                            # Sync to ALL tools
speclock sync --format cursor                  # Cursor only
speclock sync --format claude                  # Claude Code only
speclock sync --preview windsurf               # Preview without writing

# Incident Replay
speclock replay                                # Replay last session
speclock replay --list                         # List sessions
speclock replay --session <id>                 # Replay specific session

# Project Health
speclock drift                                 # Drift Score (0-100)
speclock drift --days 7                        # Last 7 days only
speclock coverage                              # Lock Coverage Audit
speclock strengthen                            # Grade and improve locks

# Share & Stats
speclock wins                                  # Shareable "Save Receipt" (screenshot it!)
speclock wrapped                               # All-time + monthly recap (alias: recap)
speclock stats                                 # Your local usage dashboard
speclock badge                                 # Print README badges (6 variants + live badge)

# Auth
speclock auth create-key --role developer
speclock auth rotate-key <keyId>

# Policy
speclock policy init                           # Create policy.yml
speclock policy evaluate --files "src/auth/*"  # Test against rules

Full command reference: npx speclock help

Auto-Guard

When you lock something, SpecLock finds related files and injects a warning the AI sees when it opens them:

code

speclock lock "Never modify auth files"
→ Auto-guarded 2 files:
  🔒 src/components/Auth.tsx
  🔒 src/contexts/AuthContext.tsx

The AI opens the file and sees:

javascript

// ============================================================
// SPECLOCK-GUARD — DO NOT MODIFY THIS FILE
// LOCKED: Never modify auth files
// ONLY "unlock" or "remove the lock" is permission to edit.
// ============================================================

Architecture

code

┌──────────────────────────────────────────────────┐
│     AI Tool (Claude Code, Cursor, Bolt.new...)    │
└────────────┬──────────────────┬──────────────────┘
             │                  │
   MCP Protocol (51 tools)    npm File-Based
             │              (SPECLOCK.md + CLI)
             │                  │
┌────────────▼──────────────────▼──────────────────┐
│            SpecLock Core Engine                    │
│                                                    │
│  Semantic Engine ─── 65+ synonym groups            │
│  HMAC Audit ──────── SHA-256 hash chain            │
│  Enforcer ────────── advisory / hard block         │
│  Auth + RBAC ─────── 4 roles, API keys             │
│  AES-256-GCM ─────── encrypted at rest             │
│  Policy DSL ──────── YAML rules                    │
│  Compliance ──────── SOC 2, HIPAA, CSV             │
│  SSO ─────────────── Okta, Azure AD, Auth0         │
└──────────────────────┬───────────────────────────┘
                       │
                 .speclock/
                 ├── brain.json        (project memory)
                 ├── events.log        (HMAC audit trail)
                 ├── policy.yml        (policy rules)
                 ├── auth.json         (API keys — gitignored)
                 └── context/
                     └── latest.md     (AI-readable context)

3 npm dependencies. Zero runtime dependencies for the semantic engine. Pure JavaScript.

Configuration

Variable	Default	Description
`SPECLOCK_API_KEY`	—	API key for authenticated access
`SPECLOCK_ENCRYPTION_KEY`	—	Enables AES-256-GCM encryption at rest
`SPECLOCK_NO_PROXY`	`false`	Set `true` for heuristic-only mode (~250ms). Skips the Gemini proxy (~2s)
`SPECLOCK_LLM_KEY`	—	Your own LLM API key (Gemini/OpenAI/Anthropic)
`GEMINI_API_KEY`	—	Google Gemini API key for hybrid conflict detection
`SPECLOCK_TELEMETRY`	`false`	Opt-in anonymous usage analytics

Tip: The heuristic engine alone scores 95%+ accuracy at ~250ms. The Gemini proxy adds cross-domain coverage but takes ~2s. For fastest response, set SPECLOCK_NO_PROXY=true.

Test Results

Pre-publish gate runs all 24 suites before every npm publish. If any test fails, publish is blocked.

Suite	Tests	Pass Rate	What it covers
Real-World Testers	111	100%	5 developers, 30+ locks, diverse domains
Adversarial Conflict	46	100%	Euphemisms, temporal evasion, compound sentences
Phase 4 (Multi-domain)	91	100%	Fintech, e-commerce, IoT, healthcare, SaaS
Sam (Enterprise HIPAA)	124	100%	HIPAA locks, PHI, encryption, RBAC
Auth & Crypto	114	100%	API keys, RBAC, AES-256 encryption
John (Indie Dev Journey)	86	100%	8-session Bolt.new build with 5 locks
Diff-Native Review	76	100%	Interface breaks, schema changes, API impact
Patch Gateway	57	100%	ALLOW/WARN/BLOCK verdicts, blast radius
Compliance Export	50	100%	SOC 2, HIPAA, CSV formats
Enforcement	40	100%	Hard/advisory mode, overrides
Audit Chain	35	100%	HMAC-SHA256 chain integrity
Code Graph	33	100%	Import parsing, blast radius, lock mapping
Spec Compiler	24	100%	NL→constraints parsing, auto-apply
Typed Constraints	13	100%	Numerical, range, state, temporal validation
Claude Regression	9	100%	Vue detection, safe-intent, patch gateway
Question Framing	9	100%	"What if we..." and "How hard would it be..."
REST API v2	9	100%	Typed constraint endpoints, SSE
PII/Export Detection	8	100%	SSN, email export, data access violations
Guardian (Protect)	47	100%	Zero-config rule file extraction
Total	1043	100%	24 suites, 15+ domains

Reproducible project test gate: all 1,043 repository tests pass on v5.8.0. These are project-maintained automated scenarios, not third-party certification; run them yourself with npm test.

Tested across: fintech, e-commerce, IoT, healthcare, SaaS, gaming, biotech, aerospace, payments, payroll, robotics, autonomous systems, telecom, insurance, government. All 11 Indian payment gateways detected. Zero false positives on UI/cosmetic actions.

Simulated Developer Journeys

John scenario — Indie developer on Bolt.new

8 sessions building an ecommerce app. 5 locks (auth, Firebase, Supabase, shipping, Stripe). Every direct violation caught. Every euphemistic attack caught ("clean up auth", "modernize database", "streamline serverless"). Zero false positives on safe actions (product page, cart, dark mode). 86/86 tests passed.

Sam scenario — Senior engineer building a HIPAA hospital ERP

10 sessions with 8 HIPAA locks. Every violation caught — expose PHI, remove encryption, disable audit, downgrade MFA, bypass FHIR. Euphemistic HIPAA attacks caught ("simplify data flow", "modernize auth"). Full auth + RBAC + encryption + compliance export workflow verified. 124/124 tests passed.

Pricing

Tier	Price	What you get
Free	$0	10 locks, conflict detection, MCP, CLI
Pro	$19/mo	Unlimited locks, HMAC audit, compliance exports
Enterprise	$99/mo	+ RBAC, encryption, SSO, policy-as-code

Changelog

Prior-version feature tours. The Quick Start and What's New sections above cover v5.7.0–v5.8.0 — this section preserves details on features shipped in v5.0–v5.5.

v5.4 — Drift Score, Lock Coverage, Lock Strengthener

Drift Score. How much has your AI-built project drifted from your original intent? Only SpecLock can answer this — because only SpecLock knows what was intended vs what was done.

bash

$ speclock drift

Drift Score: 23/100 (B) — minor drift
Trend: improving | Period: 30 days | Active locks: 8

Signal Breakdown:
  Violations:      6/30  (4 violations in 12 checks)
  Overrides:       5/20  (1 override)
  Reverts:         3/15  (1 revert detected)
  Lock churn:      0/15  (0 removed, 3 added)
  Goal stability:  0/10  (1 goal change)
  Session gaps:    9/10  (3/5 unsummarized)

README badge: ![Drift Score](https://img.shields.io/badge/drift_score-23%2F100-brightgreen.svg)

Lock Coverage Audit. SpecLock scans your codebase and tells you what's unprotected:

bash

$ speclock coverage

Lock Coverage: 60% (B) — partially protected

  [COVERED] CRITICAL authentication   2 file(s)
  [EXPOSED] CRITICAL payments         1 file(s)
  [COVERED] CRITICAL secrets          0 file(s)
  [COVERED] HIGH     api-routes       2 file(s)

Suggested Locks (ready to apply):
  1. [CRITICAL] payments (1 file at risk)
     speclock lock "Never modify payment processing or billing without permission"

Like a security scanner, but for AI constraint gaps.

Lock Strengthener. Your locks might be too vague. SpecLock grades each one and suggests improvements:

bash

$ speclock strengthen

Lock Strength: 72/100 (B) — 3 strong, 1 weak

[WEAK  ] 45/100 (D)  "don't touch auth"
          Issue: Too vague — short locks miss edge cases
          Issue: No specific scope
          Suggested: "Never modify, refactor, or delete auth..."

[STRONG] 90/100 (A)  "Never expose API keys in client-side code, logs, or error messages"

v5.3 — Universal Rules Sync, Incident Replay, Safety Templates

Universal Rules Sync. One command syncs your SpecLock constraints to every AI coding tool:

bash

speclock sync --all

code

SpecLock Sync Complete
  ✓ Cursor             → .cursor/rules/speclock.mdc
  ✓ Claude Code        → CLAUDE.md
  ✓ AGENTS.md          → AGENTS.md (Linux Foundation standard)
  ✓ Windsurf           → .windsurf/rules/speclock.md
  ✓ GitHub Copilot     → .github/copilot-instructions.md
  ✓ Gemini             → GEMINI.md
  ✓ Aider              → .aider.conf.yml

7 file(s) synced.

Define constraints once in SpecLock, sync everywhere. --format cursor for single format, --preview to dry-run, --list to see supported formats.

Incident Replay. Flight recorder for your AI coding sessions:

bash

speclock replay

Session: ses_a1b2c3 (claude-code, 47 min)
────────────────────────────────────────────
14:02  [ALLOW]   Create user profile component
14:08  [ALLOW]   Add form validation
14:15  [WARN]    Simplify authentication flow
                 → matched lock: "Never modify auth"
14:23  [BLOCK]   Clean up old user records
                 → euphemism detected: "clean up" = deletion
14:31  [ALLOW]   Update landing page hero section

Score: 5 events | 3 allowed | 1 warned | 1 BLOCKED

speclock replay --list lists sessions; --session <id> replays a specific one.

Safety Templates. Pre-built constraint packs:

bash

speclock template apply safe-defaults   # 5 locks — "Vibe Coding Seatbelt"
speclock template apply solo-founder    # 3 locks — auth, payments, data
speclock template apply hipaa           # 8 locks — HIPAA healthcare
speclock template apply api-stability   # 6 locks — API contract protection

Safe Defaults prevents the 5 most common AI disasters: database deletion, auth removal, secret exposure, error-handling removal, logging disablement.

v5.2 — AI Patch Firewall

Reviews actual diffs, not just descriptions. Catches things intent review misses:

code

POST /api/v2/gateway/review-diff
{
  "description": "Remove password column",
  "diff": "diff --git a/migrations/001.sql ..."
}

→ { verdict: "BLOCK",
    reviewMode: "unified",
    intentVerdict: "ALLOW",     ← description alone looks safe
    diffVerdict: "BLOCK",       ← diff reveals destructive schema change
    signals: {
      schemaChange: { score: 12, isDestructive: true },
      interfaceBreak: { score: 10 },
      protectedSymbolEdit: { score: 8 },
      dependencyDrift: { score: 5 },
      publicApiImpact: { score: 0 }
    },
    recommendation: { action: "require_approval" } }

Signal detection: interface breaks, protected symbol edits in locked zones, dependency drift, schema/migration destructive changes, public API route changes. Hard escalation: auto-BLOCK on destructive schema changes, removed API routes, protected symbol edits. Unified review: merges intent (35%) + diff (65%), takes the stronger verdict.

v5.1 — Patch Gateway

One API call gates every change. Takes a description + file list, returns ALLOW/WARN/BLOCK:

code

speclock_review_patch({
  description: "Add social login to auth page",
  files: ["src/auth/login.js"]
})

→ { verdict: "BLOCK", riskScore: 85,
    reasons: [{ type: "semantic_conflict", lock: "Never modify auth" }],
    blastRadius: { impactPercent: 28.3 },
    summary: "BLOCKED. 1 constraint conflict. 12 files affected." }

Combines semantic conflict detection + lock-to-file mapping + blast radius + typed constraint awareness into a single risk score (0-100).

v5.0 — Spec Compiler, Code Graph, Typed Constraints, Python SDK & ROS2

Spec Compiler. Paste a PRD, README, or architecture doc — SpecLock extracts all constraints automatically:

code

Input:  "We're building a fintech app. Use React and FastAPI.
         Never touch the auth module. Response time must stay
         under 200ms. Payments go through Stripe."

Output: 2 text locks:
          - "Never touch the auth module"
          - "Payments go through Stripe — don't change provider"
        1 typed lock:
          - response_time_ms <= 200 (numerical)
        2 decisions:
          - "Use React for frontend"
          - "Use FastAPI for backend"

Uses Gemini Flash by default ($0.01 per 1000 compilations).

Code Graph. Live dependency graph of your codebase. Parses JS/TS/Python imports.

code

$ speclock blast-radius src/core/memory.js

Direct Dependents:  8 files
Transitive Impact:  14 files (33% of codebase)
Max Depth:          4 hops

Lock-to-file mapping auto-maps locks to source files; module detection groups files into logical modules.

Typed Constraints. Real-time value and state checking for autonomous systems, IoT, robotics:

javascript

// Numerical: speed must be <= 2.0 m/s
{ constraintType: "numerical", metric: "speed_mps", operator: "<=", value: 2.0 }

// Range: temperature must stay between 20-25°C
{ constraintType: "range", metric: "temperature_c", min: 20, max: 25 }

// State: never go from armed → disarmed without approval
{ constraintType: "state", metric: "system_mode", forbidden: [{ from: "armed", to: "disarmed" }] }

// Temporal: heartbeat must occur every 30 seconds
{ constraintType: "temporal", metric: "heartbeat_s", operator: "<=", value: 30 }

Python SDK & ROS2.

bash

pip install speclock-sdk

python

from speclock import SpecLock

sl = SpecLock(project_root=".")
result = sl.check_text("Switch database to MongoDB")
result = sl.check_typed(metric="speed_mps", value=3.5)
result = sl.check(action="Increase speed", speed_mps=3.5)

Uses the same .speclock/brain.json as the Node.js MCP server. ROS2 Guardian Node subscribes to /joint_states, /cmd_vel, /speclock/state_transition; publishes violations to /speclock/violations; triggers emergency stop via /speclock/emergency_stop.

Show your support

If SpecLock saves your project from a 3am incident, add this badge to your README:

markdown

[![Protected by SpecLock](https://img.shields.io/badge/Protected_by-SpecLock-FF6B2C?style=flat&logo=lock)](https://github.com/sgroy10/speclock)

Or run speclock badge in your terminal to see all variants. Full gallery: sgroy10.github.io/speclock/badge.html · Full docs: BADGES.md.

Every adoption helps another developer discover SpecLock and stop their AI from wrecking their project. Thank you.

Spread the word

Want to help SpecLock reach more developers? Everything you need to post — tweets, LinkedIn drafts, Reddit templates, Show HN copy, Discord messages, one-liners, elevator pitches — is pre-written and fact-checked in VIRAL-KIT.md. Copy, paste, send. Zero effort.

Contributing

Issues and PRs welcome on GitHub.

License

MIT

Author

SpecLock is created and maintained by Sandeep Roy.

Sandeep Roy is the sole developer of SpecLock — the AI Constraint Engine that enforces project rules across AI coding sessions. All 51 MCP tools, the semantic conflict detection engine, enterprise security features (SOC 2, HIPAA, RBAC, encryption), and the pre-publish test gate were designed and built by Sandeep Roy.

GitHub: @sgroy10
npm: speclock

SpecLock v5.8.0 — Cross-platform action guardrails with native Claude Code enforcement, MCP integrations, 1,043 core tests, and 51 MCP tools. Developed by Sandeep Roy.

Install

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "speclock": {
      "command": "npx",
      "args": [
        "-y",
        "speclock@5.5.3"
      ]
    }
  }
}

Model Context Protocol (MCP) Server: io.github.sgroy10/speclock

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

Rules files tell AI what not to change.SpecLock enforces them.

See the difference

60-second setup

Install as a Claude Code plugin

Install on other coding agents

What you get

Proven in the open

Commands you will use most

New in v5.8.0

The Problem

How It Works

Quick Start by Platform

Bolt.new / Aider / Any npm Platform

Claude Code

Cursor / Windsurf / Cline

Lovable (No Install)

Why SpecLock Over Alternatives?

Semantic Engine

Hard Enforcement

Enterprise Security

API Key Auth + RBAC

AES-256-GCM Encryption

HMAC Audit Chain

Compliance Exports

Policy-as-Code

REST API v2

51 MCP Tools

CLI

Auto-Guard

Architecture

Configuration

Test Results

Simulated Developer Journeys

John scenario — Indie developer on Bolt.new

Sam scenario — Senior engineer building a HIPAA hospital ERP

Pricing

Changelog

v5.4 — Drift Score, Lock Coverage, Lock Strengthener

v5.3 — Universal Rules Sync, Incident Replay, Safety Templates

v5.2 — AI Patch Firewall

v5.1 — Patch Gateway

v5.0 — Spec Compiler, Code Graph, Typed Constraints, Python SDK & ROS2

Show your support

Spread the word

Contributing

License

Author

Install

Related servers

Rules files tell AI what not to change.
SpecLock enforces them.