Opinionated conventions for building secure login, sessions, MFA and OAuth flows in web apps.
Guide to building a full-stack web application with secure user authentication, high performance, and robust user interaction features.
Compares an OpenAPI YAML/JSON spec to a list of implemented routes and flags drift: missing operations, extra routes, method mismatches, and path-parameter shape differences. Use when reviewing API PRs, before a release, or asking "does our code still match the OpenAPI?". Includes a stdlib Python checker with --self-test.
Writes detailed build plans and holds a hard gate: no production writes until the user approves.
Reviews teammate PRs for correctness, security, and missing tests; sends actionable comments, not style nits.
Sorts incoming security reports for your project: spots duplicates and out-of-scope noise, checks each report against your policy, suggests a severity, and drafts polite replies to researchers.
Keeps your personal accounts safe: checks which ones still lack two-factor login, watches for breach and new sign-in alerts, explains what each alert means, and walks you through fixes step by step.
