agentsclimarketplace

Aiogram architecture refactor

Skill ballisarium/aiogram-bot-skills/skills/aiogram-architecture-refactor

focused workflows for building and maintaining aiogram bots

Install
npx -y skills add ballisarium/aiogram-bot-skills --skill aiogram-architecture-refactor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

use for a deliberate, bounded aiogram bot refactor; рефакторинг, move handler logic, split routers, services, keyboards, texts, i18n, repositories.

SKILL.md

1.9 KB, as published. Nobody here has run it

aiogram architecture refactor

improve structure without changing public telegram behavior. do not invoke for normal feature work unless structure blocks the requested change.

workflow

  1. use aiogram-project-orientation unless the repository is already mapped.
  2. define the boundary: behavior that must remain invariant, files and layers in scope, explicit exclusions, and tests that protect the behavior.
  3. add focused characterization tests before a non-trivial move when existing coverage is missing.
  4. move one responsibility at a time through existing architecture: handler logic to a service, data access to a repository, markup to a keyboard builder, text to localization, callback assembly to a factory, or a large router to domain routers.
  5. preserve commands, callback payload compatibility, persisted FSM state names, user-facing text, keyboard layout, permissions, and polling or webhook behavior unless the request explicitly changes them.
  6. preserve the installed aiogram major-version style and existing dependency wiring. do not introduce a parallel architecture for a single function.
  7. keep imports safe: no startup on import, global Bot instance in feature modules, circular imports, handler config loading, or live network access in tests.
  8. use aiogram-bot-verify after each meaningful slice and resolve failures before the next move.

completion requires a bounded responsibility move, protected invariant behavior, preserved compatibility, and verification for every slice. report what moved, what stayed stable, checks run, and remaining gaps.

guardrails

do not mix feature changes, aiogram migration, deployment changes, or unrelated cleanup into the refactor. never rename persisted callbacks or FSM states casually.

Gives 0 of the 12 instructions most refactoring skills give

Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06

  • run tests after each changein 59 of 521, across 56 files
  • write tests before refactoringin 27 of 521, across 24 files
  • preserve external behaviorin 26 of 521, across 22 files
  • remove dead codein 25 of 521, across 24 files
  • make small incremental changesin 20 of 521, across 17 files
  • break the implementation into tiny commitsin 18 of 521, across 5 files
  • ask the user about alternative optionsin 17 of 521, across 4 files
  • create a GitHub issue with the planin 17 of 521, across 4 files
  • explore the repository to verify assertionsin 17 of 521, across 4 files
  • interview the user about the refactorin 16 of 521, across 3 files
  • check the codebase for test coveragein 16 of 521, across 3 files
  • refactor one thing at a timein 16 of 521, across 12 files

Said here and by no other author read

  • map the repository first unless already mapped
  • preserve commands and payload compatibility
  • preserve persisted FSM state names and user-facing text
  • preserve installed aiogram major-version style
  • avoid startup imports and global bot instances
  • avoid circular imports and live network access in tests

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.