Aiogram handler implementation
Skill ballisarium/aiogram-bot-skills/skills/aiogram-handler-implementation
focused workflows for building and maintaining aiogram bots
npx -y skills add ballisarium/aiogram-bot-skills --skill aiogram-handler-implementationAssembled 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 when adding or changing aiogram handlers, routers, filters, commands, callback routing, bot commands, or handler dependencies; хэндлер, команда, роутер.
SKILL.md
2.2 KB, as published. Nobody here has run it
aiogram handler implementation
make the narrowest routing change that accepts only the intended telegram events.
prerequisites
use aiogram-project-orientation when the major version, registration path, or local conventions are unknown. use aiogram-bot-verify after code changes.
workflow
- inspect adjacent handlers for router naming, decorators, filters, dependency injection, error handling, texts, keyboards, and tests.
- place the change in the existing domain router unless a new domain boundary is required.
- define precise filters for command or content type, callback data, state, permissions, chat type, locale, and feature flags. check ordering against catch-all and overlapping handlers.
- keep the handler transport-focused: parse and validate event input, call a service or use case, render through existing helpers, and handle telegram-specific exceptions. move business rules, database access, and integrations out.
- wire dependencies through the project's existing middleware, parameters, container, factories, or startup construction. do not introduce a second injection style.
- register the handler through the existing path:
- aiogram 3: attach it to a
Routerand preserveinclude_routerorder - aiogram 2: preserve dispatcher decorators or registration imports
- aiogram 3: attach it to a
- update user-facing bot command registration when the command list changes.
- add tests proving intended input matches, unrelated input does not, payloads parse correctly, dependencies receive expected data, imports do not start the bot, and the router is included.
completion requires a reachable handler, bounded routing, project-consistent dependencies, import safety, and focused tests.
guardrails
do not create global Bot or Dispatcher objects in feature modules, start the bot during import, place catch-all handlers before specific ones, build large markups inline when keyboard helpers exist, or reorganize unrelated routers.