AI SummaryCopilot guidelines for contributing Java code to Redops, an attack-simulation tool, covering naming conventions, code quality, testing, security, and ethical usage standards.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "redops — Copilot Instructions" prompt rules to my project. Repository: https://github.com/Flotss/redops Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Automated attack simulation tool for web apps and servers (brute force, OWASP Top 10, DoS) with report generation and GUI.
Purpose
Provide clear, concise rules for using Copilot and contributing Java code to the Redops project (an attack-simulation tool). These guidelines help keep code readable, testable, and secure.
Structure and conventions
• Follow standard Java naming conventions (lowercase package names, PascalCase for classes). • Organize code by responsibility: com.redops.library → config, pipeline, modules, tools, etc. • Keep classes small and focused (Single Responsibility Principle).
Code quality
• Use clear, descriptive names for variables and methods. • Add comments only to explain non-obvious decisions (avoid redundant comments). • Follow the project's style rules (indentation, reasonable line length).
Testing
• Add JUnit unit tests for any new feature or bug fix. • Cover edge cases (null values, empty collections, I/O errors, invalid parameters). • For asynchronous or multi-threaded code, include at least one concurrent-behavior test when appropriate.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts