Pyrofork Documentation Skill

This skill is a reusable, documentation-first operating guide for Pyrofork. Use it to implement features, answer questions, debug issues, and generate correct examples without needing the full docs site.

Core operating rules

1. Prefer asynchronous usage (async def, await, async with Client(...)) unless a clear sync requirement exists.
2. Treat Client lifecycle explicitly:
   • one-shot scripts: async with Client(...)
   • long-running bots: decorators/handlers + app.run()
3. Handle API failures explicitly; never swallow broad RPCError without logging/feedback.
4. For update routing, design filters + groups intentionally (group, propagation control).
5. Keep session handling safe: never run multiple processes against the same .session file.

Fast task routing

Pick reference files based on task type: