a43c47a5db
Add a QWEN.md file to establish project context, preferences, and behavior guidelines for Qwen Code interactions with the aperonight Ruby on Rails project. This helps ensure consistent and appropriate responses tailored to this specific project setup. This change follows the convention of using a QWEN.md file to customize AI assistant behavior in development environments.
25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
# Qwen Code Customization
|
|
|
|
## Project Context
|
|
- Working on a Ruby on Rails project named "aperonight"
|
|
- Using Docker for containerization
|
|
- Following Ruby version 3.1.0 (as indicated by .ruby-version)
|
|
- Using Bundler for gem management (Gemfile)
|
|
- Using Node.js for frontend assets (package.json likely present)
|
|
|
|
## Preferences
|
|
- Prefer to use Ruby and Rails conventions
|
|
- Follow Docker best practices for development environments
|
|
- Use standard Ruby/Rails project structure
|
|
- When creating new files, follow Rails conventions
|
|
- When modifying existing files, maintain consistency with current code style
|
|
- Use git for version control (as seen in .gitignore)
|
|
- Prefer to work with the project's existing toolchain (Bundler, etc.)
|
|
|
|
## Behavior
|
|
- When asked to make changes, first understand the context by examining relevant files
|
|
- When creating new files, ensure they follow project conventions
|
|
- When modifying files, preserve existing code style and patterns
|
|
- When implementing new features, suggest appropriate file locations and naming conventions
|
|
- When debugging, suggest using the project's existing test suite and development tools
|
|
- When suggesting changes, provide clear explanations of why the change is beneficial |