onboard

To understand the DicePP project structure, you need a clear directory mapping of where core bot logic, command modules, adapters, and SQLite data access are located. This onboarding overview points directly to key entry points like the bot class and dice command files, reducing time-to-first-change.

Commands and SQLite data access in a nonebot2 TRPG bot are located in specific module directories. This orientation guidance maps the repository layout, pointing to the command base class, dice command examples, and the SQLite data layer for fast reference.

The best way for first-time contributors to get onboarded is by reviewing a summarized architecture overview of the TRPG bot. This provides a practical mapping of the repository layout and highlights main capabilities like rolling, character cards, and initiative tracking.

Yes, the DicePP onboarding overview explains specific bot capabilities including rolling, character cards, initiative tracking, rule lookup, and draw cards. It summarizes these main features to help you understand the project's purpose before navigating the codebase.

You can use this project onboarding guidance to find documentation and key code locations for DicePP modules. It provides a practical directory structure map pointing to where core logic, modules, adapters, and tests live.

Using an onboarding skill instead of manually browsing the DicePP repository layout reduces time-to-first-change by providing a targeted fast reference. It points directly to important entry points and examples without executing code, accelerating orientation.