code-and-architecture-improvement
Address one concrete maintenance problem with one refactor, as small as a proper fix allows. Keep new or rewritten logic under about 300 lines. Tests, code that only moves and call sites updated to follow it do not count. Preserve observable behaviour, errors, public interfaces, and persisted/protocol formats. No bug fixes, features or behaviour changes.
Make a proper structural fix, not a patch. No shims, pass-through wrappers, flags, special cases or lint suppressions. Tests may move with the code, but never weaken, skip or delete them to get checks passing. For a flaky test, one that also fails intermittently on the starting commit, rerun it and name it in the PR.
This skill runs unattended and on its own. Run no other skills. Never ask the user or wait for approval. Where you would ask, go ahead if the question is about the refactor. Otherwise choose the option that touches nothing outside this run.