code-option-comparisonlisted

# Code Option Comparison ## Why this skill exists When a user is choosing between distinct ways to do something — "Redis or Postgres LISTEN/NOTIFY for pubsub?", "give me 4 onboarding flow designs", "compare polling vs streaming vs websocket" — the right artifact is not a long narrative. It's a grid: N columns, the same sub-sections in each, scannable tradeoffs, ending in a comparison matrix and a recommendation. This skill produces that grid as a single self-contained HTML file. ## When to use Trigger phrases: "compare N approaches", "side-by-side comparison", "give me 4 different ways to X", "lay them out so I can compare", "show me the tradeoffs between X and Y and Z." Inputs: a choice point the user faces (a design decision, implementation strategy, schema shape, algorithm) — with the options either enumerated by the user or generated by you on request. Output: **one self-contained HTML file**, typically `docs/comparisons/<topic>.html`. ## When NOT to use - **One topic with a narrative arc** → `software-visual-explainer`. - **PR review** → `software-visual-explainer` in PR mode. - **Throwaway interactive editors** → prompt from scratch. - **More than ~6 options** → grids get unscannable. Pick a top 6 and note the also-rans, or write a narrative. ## Process 1. **Enumerate the options.** Work from the user's list, or generate N distinct options yourself — explicitly vary the tradeoff each makes (cost vs latency, simplicity vs flexibility, …). Each must be dis