Frontendsource GitHub
Dragonruby best practices
/dragonruby-best-practices-cursorrules-prompt-filecApplique des règles Cursor pour développer avec Dragonruby best practices de façon cohérente et maintenable.
// contenu du skill
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., usersignedin?, 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.
// source originale publique
PatrickJS/awesome-cursorrules/rules/dragonruby-best-practices-cursorrules-prompt-file.mdc
Licence : CC0-1.0. Consultez le dépôt avant toute réutilisation.
Projet indépendant, non affilié à Anthropic. Ce skill reste la propriété de son auteur original.