Aiogram fsm flows
Skill ballisarium/aiogram-bot-skills/skills/aiogram-fsm-flows
focused workflows for building and maintaining aiogram bots
npx -y skills add ballisarium/aiogram-bot-skills --skill aiogram-fsm-flowsAssembled 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 creating, changing, or debugging an aiogram FSM flow; состояние, StatesGroup, multi-step сценарий, transitions, validation, cancel, back.
SKILL.md
2.2 KB, as published. Nobody here has run it
aiogram fsm flows
use FSM only when the bot must remember progress across messages or callbacks. keep a single-step action stateless.
workflow
use aiogram-handler-implementation when state-filtered handlers or their routing change. use aiogram-bot-verify after code changes.
- confirm the aiogram major version, storage backend, state naming, existing navigation helpers, persistence needs, and test style.
- define the internal state map before editing: entry, expected input, validation, stored data, success, retry, back, cancel, stale state, and cleanup.
- follow project naming. prefer one
StatesGroupper domain flow and meaningful state names overstep1or handler names. - make each transition explicit: accepted input, data written, next state, response, and cleanup condition.
- validate at the input boundary. on invalid input, explain the problem, keep data consistent, and deliberately remain, reset, or exit; never advance silently.
- reuse global cancel, back, and retry behavior. otherwise implement the smallest local equivalent:
- cancel clears state and temporary data
- back restores the previous meaningful state and prompt
- retry repeats the current prompt without corrupting data
- clear state after success, cancellation, unrecoverable failure, permission loss, or missing backing data. provide a safe reset for callbacks to deleted entities, old deployments, changed permissions, and changed flow schemas.
- keep domain decisions in services or use cases; state handlers orchestrate the conversation.
- test entry, every valid transition, invalid input, back, cancel, retry, success cleanup, and relevant stale-data behavior. completion requires a complete state map, explicit transitions, recovery and cleanup paths, persistence appropriate to deployment, and transition coverage.
guardrails
never store large or sensitive payloads in FSM data, clear needed data before reading it, leave users in obsolete states, or rename persisted states casually.