How do I install the Routine Abstraction Improver skill?

Run npx skillmds@latest add bex-co/routine-abstraction-improver in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Routine Abstraction Improver safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Routine Abstraction Improver?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Routine Abstraction Improver free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Routine Abstraction Improver?

bex-co (@bex-co) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Routine Abstraction Improver by bex-co

Name: Routine Abstraction Improver
Author: bex-co

Routine Abstraction Improver

Autonomous maintenance routine that flattens over-engineered abstractions in a monorepo package — interfaces with one implementation and no stated reason, passthrough wrappers, one-product factories, delegate-only manager layers — by inlining the single thing behind them and shipping via /ship. Use only when the user explicitly invokes /routine-abstraction-improver or asks to flatten needless indirection. SKIP for convoluted logic inside one unit (routine-logic-simplifier), imports crossing stated boundaries (routine-abstraction-police), and duplicated implementations (routine-dup-unifier). The core trigger is "remove indirection that has exactly one thing behind it".

bex-co 1abc979 3.2 KB Updated Sep 17, 2026

File contents

Task: Flatten over-engineered abstractions

Usage: /routine-abstraction-improver [package-or-path]

Find a layer of indirection with exactly one thing behind it and no stated reason to exist, inline it, delete the layer, and ship via /ship.

Contract

Read .agents/skills/routine-shared/contract.md first — preconditions, scope resolution, verify gates, ship protocol, budget, universal STOPs. Floor even without it: never ship red; one finding per ship; anything in a DO_NOT_DO.md is a hard STOP.

Workflow

1. Scope

Resolve scope per the contract.

2. Discover

The shapes worth suspecting:

Interfaces/abstract classes with exactly one implementation
Wrapper functions/modules that only re-export or forward arguments
Factories that can only ever produce one product
Generics never instantiated with a second type
"Manager"/"provider"/"service" layers that purely delegate

3. Prove it

A layer is a finding only when all hold:

Grep confirms exactly one implementation and one usage pattern.
No stated reason for it exists. Check the scoped CLAUDE.md, docs/adrs/, and .pm boards. In particular: backend-v2 mandates an I<Name> interface beside every service/workflow class (backend-cluster/backend-v2/CLAUDE.md, Dependency and layer rules) — those interfaces are a stated convention, never a finding. Same for seams that exist so tests can double them, when the tests actually do.
No evidence of a planned second implementation.

4. Fix

Inline the single thing, delete the layer, call directly. If tests mocked the deleted layer, rewrite them against the concrete unit with real assertions — never leave them asserting a mock of something that no longer exists. Behavior identical.

5. Verify

Typecheck + full owning-package gate, and a grep confirming no dangling references to the deleted layer.

6. Ship

Compose /ship for this one flattening. Loop within budget.

What NOT to do

Never flatten an abstraction a CLAUDE.md, ADR, or working test double justifies — a stated convention beats this routine's taste, every time.
Don't rewrite convoluted logic inside a unit (routine-logic-simplifier) or move code across layers (routine-abstraction-police).
Don't flatten two layers in one ship; each deletion stands alone.
Don't replace the deleted abstraction with a cleverer one — the fix is less structure, not different structure.

Arguments

$ARGUMENTS

---name: routine-abstraction-improverdescription: Autonomous maintenance routine that flattens over-engineered abstractions in a monorepo package — interfaces with one implementation and no stated reason, passthrough wrappers, one-product factories, delegate-only manager layers — by inlining the single thing behind them and shipping via /ship. Use only when the user explicitly invokes /routine-abstraction-improver or asks to flatten needless indirection. SKIP for convoluted logic inside one unit (routine-logic-simplifier), imports crossing stated boundaries (routine-abstraction-police), and duplicated implementations (routine-dup-unifier). The core trigger is "remove indirection that has exactly one thing behind it".---# Task: Flatten over-engineered abstractionsUsage: `/routine-abstraction-improver [package-or-path]`Find a layer of indirection with exactly one thing behind it and no statedreason to exist, inline it, delete the layer, and ship via `/ship`.## ContractRead `.agents/skills/routine-shared/contract.md` first — preconditions,scope resolution, verify gates, ship protocol, budget, universal STOPs. Flooreven without it: never ship red; one finding per ship; anything in a`DO_NOT_DO.md` is a hard STOP.## Workflow### 1. ScopeResolve scope per the contract.### 2. DiscoverThe shapes worth suspecting:- Interfaces/abstract classes with exactly one implementation- Wrapper functions/modules that only re-export or forward arguments- Factories that can only ever produce one product- Generics never instantiated with a second type- "Manager"/"provider"/"service" layers that purely delegate### 3. Prove itA layer is a finding only when **all** hold:1. Grep confirms exactly one implementation and one usage pattern.2. **No stated reason for it exists.** Check the scoped `CLAUDE.md`, `docs/adrs/`, and `.pm` boards. In particular: **backend-v2 mandates an `I<Name>` interface beside every service/workflow class** (`backend-cluster/backend-v2/CLAUDE.md`, Dependency and layer rules) — those interfaces are a stated convention, never a finding. Same for seams that exist so tests can double them, when the tests actually do.3. No evidence of a planned second implementation.### 4. FixInline the single thing, delete the layer, call directly. If tests mocked thedeleted layer, rewrite them against the concrete unit with real assertions —never leave them asserting a mock of something that no longer exists. Behavioridentical.### 5. VerifyTypecheck + full owning-package gate, and a grep confirming no danglingreferences to the deleted layer.### 6. ShipCompose `/ship` for this one flattening. Loop within budget.## What NOT to do- Never flatten an abstraction a `CLAUDE.md`, ADR, or working test double justifies — a stated convention beats this routine's taste, every time.- Don't rewrite convoluted logic inside a unit (`routine-logic-simplifier`) or move code across layers (`routine-abstraction-police`).- Don't flatten two layers in one ship; each deletion stands alone.- Don't replace the deleted abstraction with a cleverer one — the fix is *less* structure, not different structure.## Arguments$ARGUMENTS

Frequently asked questions