Menu
Research and compare how competing products implement a similar feature at the UX and interaction level. Provides structured comparison tables and strategic differentiation recommendations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate architecture and design documents for implemented code changes with risk-based depth selection. Automatically evaluates risk signals, layer spread, and change magnitude to choose documentation level (A/B/C). Use after completing a feature, before merging a PR that touches multiple layers or sensitive areas (auth, infra, migrations, payments), or when an implemented change needs a design record or ADR.
Verify that the current Git branch, upstream state, and dirty working tree match the user's intended task before staging, committing, pushing, or continuing work from another session. Use this to detect stale branch reuse, leftover dirty files from previous sessions, unrelated commits on the current branch, cases where work should be split into a new branch or worktree, and post-publish cleanup decisions after push, PR creation, or PR merge.
Re-audit code changes to identify side effects, regression risks, and unhandled edge cases before merging or deploying. Use after a change is complete and before merging to a shared branch, before deploying a hotfix, after complex multi-module refactoring, or when a previous review may have missed side effects in async, state-mutating, or security-sensitive code paths.
Diagnose and fix CJK (Korean, Japanese, Chinese) text-wrapping issues in web UIs. Systematically traces mid-syllable breaks, orphaned glyphs, and awkward line splits through a layered fix strategy covering global CSS cascade, component-library overrides, headline balancing, and translation-level phrase binding. Produces an evidence-based diagnosis and verification report before any code change is applied.
Finalize documentation changes for production readiness by discovering existing conventions, verifying code-doc alignment, reviewing format/terminology/tone consistency, verifying branch/worktree intent, and structuring clean commits with a post-publish branch/worktree cleanup decision. Counterpart of finalize-and-commit for documentation projects.
Finalize code changes for production readiness by removing duplicate logic, auditing hardcoded values, verifying branch/worktree intent, verifying build integrity, structuring clean commits with Conventional Commits format, and forcing a post-publish branch/worktree cleanup decision.
| name | competitive-feature-benchmark |
| description | Research and compare how competing products implement a similar feature at the UX and interaction level. Provides structured comparison tables and strategic differentiation recommendations. |
| license | MIT |
| metadata | {"compatibility":"Claude Code, Cursor","type":"execution","category":"research","maturity":"draft","estimated_time":"15 min"} |
Type: Execution
Research and analyze how competing products implement a similar feature. Provide structured comparison and strategic recommendations.
The goal is not imitation. The goal is to:
Do not run this skill without:
Optional but recommended:
Select 3–5 competitors based on:
For each competitor:
EFFICIENCY RULE: When analyzing multiple competitors, batch independent web searches in parallel where possible. Collect all competitor data before proceeding to Step 3, rather than completing full analysis of one competitor before starting the next.
For each competitor, analyze:
CONTEXT MANAGEMENT: After completing Step 2, compile findings into the comparison table immediately (Step 3). Use only the structured table — not the raw research notes — as input for Steps 4 and 5. This prevents context accumulation from verbose research outputs.
Create a structured comparison table including:
Identify:
Answer:
Provide a clear recommendation with justification.
Common bad outputs:
Input:
Feature: search filter in a SaaS project management tool. Our proposal: single dropdown with predefined filter options.
Output:
Input:
Feature: dashboard navigation for an analytics platform. Our proposal: tab-based top navigation with 8 sections. Target users: data analysts at mid-size companies. Competitors: Mixpanel, Amplitude, PostHog, Metabase.
Output:
FAST MODE (only if explicitly requested):
If competitors are not specified in the input, identify 3–5 relevant products in the same domain before proceeding.
