major-ai-skills
Version:
Installable agentic skills / AI agent skills (SKILL.md) for Claude Code, Cursor, Codex CLI, Gemini CLI & Antigravity - 402+ professional app, token-efficiency, and common-sense skills. SEO/GEO ready.
88 lines (68 loc) • 4.74 kB
Markdown
name: compare-two-products-fairly
description: "Compare two products against the same requirements, pricing assumptions, limitations, and evidence."
category: common-sense
risk: safe
source: self
source_type: self
date_added: "2026-08-26"
tags: ["product-comparison", "head-to-head", "evaluation", "trade-offs", "decision-matrix", "prompt-engineering"]
tools: ["claude", "cursor", "gemini", "codex", "chatgpt"]
# Compare Two Products Fairly (Symmetrical Comparison Matrix) (AI Skill)
## Overview
Asking an AI *"Which is better: Product A or Product B?"* triggers shallow generalizations and often biases towards whichever product has more marketing presence.
The **Symmetrical Comparison Protocol** forces the AI into an objective, head-to-head evaluation framework that compares exact functional dimensions, total cost of ownership, and specific user profile matches.
## The Head-to-Head Comparison Framework
```
┌─────────────────────────────────────────────────────────────┐
│ Symmetrical Comparison Matrix │
│ │
│ [ PRODUCT A ] vs. [ PRODUCT B ] │
│ │ │ │
│ • Primary Superpower • Primary Superpower│
│ • Fatal Limitation • Fatal Limitation │
│ • True Pricing & Hidden Costs • True Pricing │
│ • Ideal User Match • Ideal User Match │
│ │
│ └──────────────────────┬──────────────────┘ │
│ ▼ │
│ [ Decision Fork: If X $\rightarrow$ A, If Y $\rightarrow$ B ] │
└─────────────────────────────────────────────────────────────┘
```
## Master Head-to-Head Prompt Templates
### Pattern 1: The Symmetrical Matrix Directive
Use for comparing developer tools, SaaS apps, or hardware:
```markdown
Compare [PRODUCT A] and [PRODUCT B] for [TARGET USE CASE / TEAM SIZE].
Output Rules:
1. Generate a single Markdown comparison table with the following headers:
| Evaluation Dimension | [PRODUCT A] | [PRODUCT B] | Advantage Winner |
2. Cover these dimensions:
- Primary Architectural Superpower
- Worst Limitation / Pain Point
- Pricing Model & Hidden Add-on Costs
- Learning Curve / Time to Implement
3. Follow the table with a "Decision Fork":
- "Choose [PRODUCT A] if you prioritize..."
- "Choose [PRODUCT B] if you prioritize..."
```
## Real-World Case Study
### Scenario: Comparing Next.js vs. Remix for Web Application
#### Symmetrical Output Example
| Evaluation Dimension | Next.js (App Router) | Remix (React Router v7) | Advantage Winner |
| :--- | :--- | :--- | :--- |
| **Architectural Model** | React Server Components (RSC) & Server Actions; edge/node hybrid. | Web Standards-first (Fetch/Request/Response); nested routing & loaders. | **Tie** (Philosophical difference) |
| **Deployment Flexibility** | Optimized for Vercel; self-hosting standalone server has edge caveats. | Deploys natively to Cloudflare Workers, Node, Express, Fly.io with zero lock-in. | **Remix** (Portability) |
| **Ecosystem & Community** | Massive ecosystem, extensive documentation, largest talent pool. | Smaller, passionate community; rapidly unifying with React Router. | **Next.js** (Ecosystem size) |
| **Developer Ergonomics** | RSC caching semantics can be complex and unintuitive to debug. | Standard HTML form submissions and standard Web Request APIs. | **Remix** (Simplicity) |
#### The Decision Fork
- **Choose Next.js** if your team is already invested in Vercel infrastructure, needs massive component library support, or heavily utilizes React Server Components.
- **Choose Remix** if you want standards-based web architecture, total cloud hosting portability, and cleaner form mutation ergonomics.
## Comparison Heuristics
- **Always ask for the "Fatal Limitation"**: Every product has a tradeoff; uncovering it prevents post-purchase regret.
- **Demand the "Decision Fork"**: Never accept *"both are great"*; force the AI to define the exact condition where each option wins.