What problem does it solve? Mechanical engineering rules (lockfiles committed, no secrets in git, documented env vars, parameterized SQL) are easy to forget, and a rule that isn't runnable gets skipped. This gate turns the checkable slice of system-design and security law into a script that blocks a push on violations. ## Core Features & Use Cases - Blocking checks: Fails with exit code 1 on missing lockfiles, tracked .env files, undocumented process.env variables, TODO(keys) without SETUP-KEYS.md, missing PROJECT-LOG.md, string-interpolated SQL, and auth tokens stored in localStorage. - Non-blocking warnings: Flags server/API code with no rate-limit reference and server-side fetch calls without a timeout or AbortSignal. - E-commerce enforcement: Detects payment dependencies or cart/checkout routes and requires evidence the e-commerce guideline was applied. - Use Case: Before pushing a Next.js project, run the gate to catch a committed .env file and a SQL query built with template literals, fixing them before they reach the remote. ## Quick Start Run the system-design gate on my project directory and fix any blocking findings before I push.
