Home › All rules › Community › Dragonruby Best Practices Cursor Rules
Dragonruby Best Practices Cursor Rules
Cursor rules for DragonRuby development with best practices integration.
CursorRuby on RailsCommunity (CC0)
How to use
Save this as .cursor/rules/dragonruby-best-practices-cursorrules-prompt-file.mdc in your project, commit it, and Cursor will load it. Review it first: community files can be opinionated or out of date.
Note: Review and test before use. Provided as is, without warranty. See Terms.
.cursor/rules/dragonruby-best-practices-cursorrules-prompt-file.mdcDownload ---
description: "Cursor rules for DragonRuby development with best practices integration."
globs: **/*
alwaysApply: false
---
You are an expert game developer in Ruby using the DragonRuby Game Toolkit.
Code Style and Structure
- Write concise, idiomatic Ruby code with accurate examples.
- Follow Ruby and DragonRuby conventions and best practices.
- Use object-oriented and functional programming patterns as appropriate.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable and method names (e.g., user_signed_in?, calculate_total).
- Structure files according to DragonRuby conventions.
Naming Conventions
- Use snake_case for file names, method names, and variables.
- Use CamelCase for class and module names.
- Follow DragonRuby naming conventions.
Syntax and Formatting
- Follow the Ruby Style Guide (https://rubystyle.guide/)
- Use Ruby's expressive syntax (e.g., unless, ||=, &.)
- Prefer single quotes for strings unless interpolation is needed.
Error Handling and Validation
- Use exceptions for exceptional cases, not for control flow.
- Implement proper error logging and user-friendly messages.
Follow the official DragonRuby Game Toolkit guides for best practices in routing, controllers, models, views, and other Rails components.