Aiogram project orientation
Skill ballisarium/aiogram-bot-skills/skills/aiogram-project-orientation
focused workflows for building and maintaining aiogram bots
npx -y skills add ballisarium/aiogram-bot-skills --skill aiogram-project-orientationAssembled 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 before changing an unfamiliar aiogram or telegram bot repository; проект, бот, структура, version, entrypoint, routers, startup, config, database, tests.
SKILL.md
2.0 KB, as published. Nobody here has run it
aiogram project orientation
build a working map before substantial changes. report only findings that affect the task.
workflow
- prove the aiogram major version from dependency files, lockfiles, imports, and handler syntax. if it remains uncertain, say so and avoid version-specific rewrites.
- find the real entrypoint through Python modules, package scripts, containers, process files, or service configuration. identify polling, webhook, cli, or framework lifecycle startup.
- trace
BotandDispatchercreation, config loading, middleware setup, startup hooks, and import-time side effects. - trace handler registration end to end:
- aiogram 3:
Router,include_router,include_routers, and aggregation order - aiogram 2: decorators,
register_*_handler, and registration imports
- aiogram 3:
- map only task-relevant layers: handlers, filters, keyboards, callback data, states, services, repositories, models, texts, jobs, and integrations.
- identify state and storage behavior: backend, naming, cancel and cleanup paths, persistence, and transition tests.
- identify the data layer: driver or orm, repositories, migrations, transactions, and direct database access from handlers.
- find the project's own test, lint, format, typecheck, and import commands. note fixtures, async setup, fake events, and network isolation.
- locate text and localization conventions before changing user-facing copy.
completion requires a proven version or stated uncertainty, a traced startup and registration path, the relevant change surfaces, and safe verification commands.
output
keep the user-facing map short: version, entrypoint, routing convention, relevant layers, verification commands, and implementation risks. continue to implementation unless the user requested analysis only.