Agent Skills
nklswbr/skills

Skills / subtract

Signatures of Addition

Things that pile up because adding was easier than deciding. Walk the surface against the sections that apply. Each row is a signature, why it tends to exist, and the usual rung on the ladder. "Usual" is a starting point; the evidence decides.

Product and flows

SignatureWhy it existsUsual rung
A setting almost nobody changesThe team couldn't agree, so they shipped bothDefault
A setting that exists for one customerA sales ask that became permanentHide (flag or per-account config), or Delete if the customer churned
Two ways to reach the same place (sidebar + tab + command palette + button)Each was added by a different team or releaseMerge; keep the one people use, plus the shortcut
An onboarding tour or welcome carouselThe product didn't explain itself, so a layer was added on topDelete; fix the empty state and labels instead
A wizard for a form with five fieldsSomeone felt the form was longDelete the wizard; one page, fewer fields
A field that's optional and almost always empty"Might be useful later"Delete, or move to the detail view
A field you could infer (country from address, name from email, timezone from browser)It was easier to ask than to inferDefault, editable
"Are you sure?" on a reversible actionFear of mistakesDelete; offer Undo instead
A confirmation toast for a change the user can already seeFeedback by habitDelete
A feature with a flag that's been at 100% (or 0%) for monthsThe cleanup ticket never got scheduledDelete the flag (and the dead branch)
A feature that duplicates a better one shipped laterNobody owned removing the old oneMerge, migrate, Delete
Plans or tiers that differ by one featurePricing designed by additionMerge tiers
A notification type nobody turns on, or everyone turns offDefault-on to drive engagementDelete, or default off
Multiple empty, loading, and error designs for the same thingBuilt per screenMerge into one pattern

Interface

SignatureWhy it existsUsual rung
Icon + label + tooltip saying the same thingBelt, suspenders, second beltShorten to label (or icon + tooltip for dense toolbars)
Border + shadow + background on the same cardEach was added to make it "pop"Shorten to one
Several primary-looking buttons in one viewEvery stakeholder wanted theirs prominentKeep one primary, demote the rest
A heading with a subtitle that restates itTemplate had a subtitle slotDelete the subtitle
A tooltip explaining a labelThe label is wrongShorten: fix the label, delete the tooltip
Section dividers between sections that already have headingsVisual noise by defaultDelete; spacing does the job
A badge, dot, or counter that's always onEngagement pressureDelete, or show only when it changes something
Decorative icons in front of every list itemFilling spaceDelete
A filter bar with eight filters where two get usedBuilt for completenessKeep the two, hide the rest under "More"
Breadcrumbs on a two-level hierarchyPattern-library defaultDelete; a back link is enough
A modal that could be inlineModals feel "safe"Delete the modal; edit in place
Pagination controls plus "load more" plus infinite scrollDebates settled by doing all threeMerge to one
Animations on frequent actionsPolish added uniformlyDelete (high-frequency actions shouldn't animate)
Custom component where a native one works (select, date input, checkbox)Design consistencyDelete the custom one when native is good enough

Copy

SignatureWhy it existsUsual rung
"Please", "simply", "just", "easily", "in order to"Politeness fillerShorten
Helper text that repeats the label ("Email — Enter your email")Every field got helper textDelete
An empty state with a paragraphExplaining instead of offering the next actionShorten to one line + the action
Errors that explain what happened but not what to doWritten from the system's viewShorten to the fix
Button labels like "Submit", "OK", "Continue"DefaultsShorten to the verb that happens ("Send invite")
Marketing voice inside the productCopy reused from the landing pageShorten
The same idea said in title, subtitle, and bodyEach layer written separatelyKeep one
Legal or disclaimer text on every pageApplied once, copied everywhereKeep it where it applies, Delete elsewhere

Code

SignatureWhy it existsUsual rung
An abstraction with one implementation"We might need another"Delete; inline it
A wrapper that forwards to one library callFuture-proofingDelete
V2 next to the original, both in useMigration never finishedMerge, then Delete the old one
A config option with one value in every environmentBuilt configurable on day oneDelete; make it a constant
A feature flag fully rolled outCleanup never scheduledDelete flag and dead branch
Props or parameters that every caller passes the same wayOptionality nobody usesDefault, then Delete
Defensive checks for states the types already rule outCopy-paste cautionDelete
Dependencies used for one functionFaster to install than writeShorten (native API or a few lines)
Utils folder with near-duplicate helpersNobody searched before writingMerge
Comments restating the codeHabitDelete
Tests that assert implementation details of deleted behaviorNever removed with the featureDelete
Indirection layers (service → manager → handler → helper) for a simple callArchitecture by templateMerge layers
Generated or vendored code checked in alongside its sourceConvenience onceDelete, generate at build
Commented-out code"Just in case"Delete; git remembers

Questions that find more

When the table runs dry, ask these about the surface:

  • If we launched this today, which parts would make it into v1?
  • What would we remove if we had to cut it in half by Friday?
  • What does a new user ignore, and what does a power user ignore? Things both ignore go first.
  • Which parts exist to compensate for another part being bad? Fix the bad part, delete the compensation.
  • Which settings exist because we didn't make a decision?
  • What do we maintain that nobody would miss if it silently broke for a week?
  • What would the simplest competitor leave out?