Structure software around the Dependency Rule — dependencies point inward from frameworks to use cases to entities. Use when deciding where code belongs in a RonyKit feature module (handler vs app vs repo), reviewing layer boundaries, or keeping business rules independent of Postgres/Rony/HTTP. For refactoring with tests, see refactoring-patterns. For untested code, see working-with-legacy-code.
$npx -y skills add clubpay/ronykit --skill clean-architectureInstalls into the current project.
Run `npx skills use "https://github.com/clubpay/ronykit" --skill "clubpay/ronykit/clean-architecture"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/clubpay/ronykit" that are relevant to the current task. Run `npx skills add "https://github.com/clubpay/ronykit"` and select the relevant skills, then follow their instructions.