SpecLock – 귀하의 Claude.md가 제안입니다. 이걸로 법이 만들어지네

Website · npm · Smithery · GitHub Developed by Sandeep Roy · Free & Open Source (MIT License) New in v5.4: speclock drift — the only tool that measures how much your AI has drifted from your architecture.speclock coverage — find what's unprotected.speclock strengthen — grade your locks. Three numbers that tell your project's whole story. You: "Never touch the auth system" AI: 🔒 Locked. ... 5 sessions later ... You: "Add social login to the login page" AI: ⚠️ BLOCKED — violates lock "Never touch the auth system" Matched: auth → authentication (synonym), login → auth (concept) Confidence: 100% Should I find another approach? 100/100 on Claude's independent test suite. 991 tests across 19 suites. 0 false positives. 15.7ms per check. Zero-config Guardian Mode, Universal Rules Sync, AI Patch Firewall, Drift Score, Spec Compiler, Code Graph. npx speclock setup --goal "Build my app" That's it. One command. Works everywhere — Bolt.new, Claude Code, Cursor, Lovable, Windsurf, Cline, Aider. npx speclock protect Zero flags. Reads your existing rule files, extracts enforceable constraints, installs a pre-commit hook, and syncs rules to every AI tool. Your rules are now enforced, not just suggested. 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. You set constraints. SpecLock enforces them — across sessions, across tools, across teams. 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) 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. Add to .mcp.json : { "mcpServers": { "speclock": { "command": "npx", "args": ["-y", "speclock", "serve", "--project", "."] } } } Same config — add to .cursor/mcp.json or equivalent. - Go to Settings → Connectors → New MCP server - Enter URL: https://speclock-mcp-production.up.railway.app/mcp - Paste project instructions into Knowledge | 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 | 100/100 score, 0% FP | | 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. One command syncs your SpecLock constraints to every AI coding tool: speclock sync --all 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. Your AI tools will now see SpecLock constraints. Stop maintaining 3 separate rules files. Define constraints once in SpecLock, sync everywhere. speclock sync --format cursor # Sync to Cursor only speclock sync --preview claude # Preview without writing speclock sync --list # Show all supported formats Flight recorder for your AI coding sessions. See exactly what happened: 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