What problem does it solve? Security gaps in new code — unguarded routes, missing tenant scoping, privilege grants on login paths — are usually discovered months later as audit findings. This Skill forces two design questions (who can reach this, what do they get) to be answered before the code exists, so the guard ships in the same commit as the feature. ## Core Features & Use Cases - Two-question gate: Names the least-privileged caller and what they obtain, ending the check immediately if the answer is nothing. - Decision table by surface: Maps routes, tenant queries, webhooks, model-callable tools, URL fetches, uploads, and input-built queries to the one decision each requires and where it lives in code. - Durability rules: Enforces default-closed parameters, deletion of dev-only routes instead of guarding them, and recording decisions as checks or comments in code rather than PR descriptions. - Use Case: Before adding a new API endpoint that returns tenant data, run the check to decide which middleware guards it and confirm the tenant ID comes from the session in the SQL WHERE clause. ## Quick Start Ask the assistant to run the authority check on the new endpoint or webhook handler you are about to write.
