An AI engineering second opinion for your git diff. It doesn't tell you whether your code is right. It tells you what your code means.

Secure HTTP framework for Node.js. Express-compatible with built-in security, no performance tradeoff.

- Work around the umzug architectural limitations that make it hard/impossible to transactionally execute + log (or unlog) a migration, even when the logs and the migrations are applied to the same db. - Accept tradeoff that this will force each user mi

argon2-rust binding for Node.js

MCP server for AI-powered contract negotiation — clause redlining, counter-proposal generation, risk tradeoff analysis, and negotiation strategy recommendations

Standalone RICE prioritization scoring calculator — reach, impact, confidence, effort — extracted from Roadmap Tradeoff Visualizer as a reusable npm package.

Architecture Decision Records with teeth — lifecycle management, 15 architecture paradigms, DDD context scoping, DCAR forces evaluation, reflexion models, Wardley mapping, C4 diagrams, ATAM tradeoff analysis, and 19 specialized agents for Claude Code.

System Design Assistant (#6) engine — generate architecture diagrams (Mermaid), ADRs, weighted tradeoff analysis, persisted design memory, and interview-prep grading. Node native TypeScript; zero-network.

Inline critical CSS and lazy-load the rest.

Generate trusted local SSL/TLS certificates for local SSL development

NPAW's Plugin

NPAW's Plugin Adapters

The all-batteries-included GitHub SDK for Browsers, Node.js, and Deno

So, running a local HTTPS server usually sucks. There's a range of approaches, each with their own tradeoff. The common one, using self-signed certificates, means having to ignore scary browser warnings for each project.

My JavaScript parser

VMZ MathJax adapter - <Mathjax> + math engine

NPAW's Plugin

NPAW's Plugin

JSONL durable session persistence backend for the DeepSeek Harness

Generate trusted local SSL/TLS certificates for local SSL development