skills.rest
EpicenterHQ
EpicenterHQOFFICIAL
Explore all skills by this author →
Website𝕏@EpicenterHQGitHub

asymmetric-wins

Identifies small feature promises whose refusal deletes disproportionate code complexity.

4.8k|376|Updated Mar 16, 2023
Search Tags:#technical debt#complexity reduction#decision framework#Refactoring#ARCHITECTURE#feature cutting#code deletion
One-click install
npx skills add https://github.com/EpicenterHQ/epicenter --skill asymmetric-wins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asymmetric-wins
Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/asymmetric-wins
Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill asymmetric-wins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software projects accumulate complexity from small convenience promises—fallback parsers, compatibility aliases, duplicate fast paths, pixel-perfect reproductions—that each force an entire second system to be maintained. This Skill provides a disciplined decision framework for finding the one small promise whose refusal collapses a disproportionately large code family while keeping the product's core value intact.

Core Features & Use Cases

  • Refusal Point Analysis: Systematically lists candidate refusal points (legacy aliases, rare modes, provider exceptions, exact reproduction) and maps each to the code family it owns.
  • Decision Templates: Provides structured templates for specs and design notes covering the product sentence, deletion prize, user loss, and final decision.
  • UI Refactor Guidance: Includes an artifact ladder (shared primitive, screenshot, sketch, partial tree, full HTML) so teams use the smallest artifact that preserves the design decision.
  • Use Case: When refactoring authentication, evaluate whether refusing a Google GIS fast path lets you delete per-provider helpers, blocked-browser UI, and duplicate test paths while keeping one OAuth 2.1 PKCE invariant.

Quick Start

Ask the AI to apply the asymmetric wins framework to evaluate whether a specific feature or compatibility promise in my codebase is worth the complexity it forces.

Frequently Asked Questions about asymmetric-wins

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which features to cut during a refactor?▼

List candidate refusal points such as legacy aliases, fallback parsers, and rare modes, then map each to the code family it owns. Refuse the candidate with the largest deletion prize whose loss is a small convenience rather than a load-bearing capability.

What is an asymmetric win in software design?▼

An asymmetric win is a refusal that gives back more complexity than it costs in product capability. You trade a small amount of fidelity, compatibility, or modes to collapse a much larger implementation graph while keeping the product sentence intact.

When is pixel-perfect fidelity worth keeping in a UI refactor?▼

Pixel, markup, and screenshot fidelity are load-bearing when the exact detail carries comprehension, accessibility, trust, brand, or a regression-sensitive state. Otherwise exact reproduction is a promise like any other and should earn the code family it forces.

How do I avoid removing features users actually depend on?▼

Name the product sentence first and ask who loses what if the behavior is refused. Keep the feature when the user loss is load-bearing or when the deletion would only move complexity somewhere harder to see.

What design artifact should replace a full HTML reproduction?▼

Use the smallest artifact that preserves the decision: a shared primitive first, then a screenshot, compact sketch or state table, then a partial tree. Reserve full HTML diagrams for cases where exact DOM shape is the product contract or the bug.

Related Skills

Explore More Software Engineering Skills→
nassimbfnassimbf
3

product-lens

Force explicit reasoning and surface hard truths before coding.

Community
Advanced
quaid-appquaid-app
3

breaking-schema-changes

Apply breaking SQLite schema migrations atomically in Rust projects.

Official
Advanced
ollieb89ollieb89

openclaw-review

Orchestrate L2 diff review workflows for L3 code changes on staging branches.

Community
Intermediate
logo-solutionslogo-solutions

deprecation-and-migration

Plan deprecation and migration of legacy systems, APIs, and libraries.

Official
Advanced