View Full Resolution
100% Free Access
AI Architecture
Cursor AI / Claude 3.5
Category
AI Agents
Best Use Case
Commercial & Cinematic
AI Agents
Verified Blueprint
Clean Code Agent Rule
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.
Ready-to-Run Prompt
100% Free Copy
# Clean Code Guidelines
## Constants Over Magic Numbers
- Replace hard-coded values with named constants
- Use descriptive constant names that explain the value's purpose
- Keep constants at the top of the file or in a dedicated constants file
## Meaningful Names
- Variables, functions, and classes should reveal their purpose
- Names should explain why something exists and how it's used
- Avoid abbreviations unless they're universally understood
## Smart Comments
- Don't comment on what the code does - make the code self-documenting
- Use comments to explain why something is done a certain way
- Document APIs, complex algorithms, and non-obvious side effects
## Single Responsibility
- Each function should do exactly one thing
- Functions should be small and focused
- If a function needs a comment to explain what it does, it should be split
## DRY (Don't Repeat Yourself)
- Extract repeated code into reusable functions
- Share common logic through proper abstraction
- Maintain single sources of truth
## Clean Structure
- Keep related code together
- Organize code in a logical hierarchy
- Use consistent file and folder naming conventions
## Encapsulation
- Hide implementation details
- Expose clear interfaces
- Move nested conditionals into well-named functions
## Code Quality Maintenance
- Refactor continuously
- Fix technical debt early
- Leave code cleaner than you found it
## Testing
- Write tests before fixing bugs
- Keep tests readable and maintainable
- Test edge cases and error conditions
## Version Control
- Write clear commit messages
- Make small, focused commits
- Use meaningful branch names
## Constants Over Magic Numbers
- Replace hard-coded values with named constants
- Use descriptive constant names that explain the value's purpose
- Keep constants at the top of the file or in a dedicated constants file
## Meaningful Names
- Variables, functions, and classes should reveal their purpose
- Names should explain why something exists and how it's used
- Avoid abbreviations unless they're universally understood
## Smart Comments
- Don't comment on what the code does - make the code self-documenting
- Use comments to explain why something is done a certain way
- Document APIs, complex algorithms, and non-obvious side effects
## Single Responsibility
- Each function should do exactly one thing
- Functions should be small and focused
- If a function needs a comment to explain what it does, it should be split
## DRY (Don't Repeat Yourself)
- Extract repeated code into reusable functions
- Share common logic through proper abstraction
- Maintain single sources of truth
## Clean Structure
- Keep related code together
- Organize code in a logical hierarchy
- Use consistent file and folder naming conventions
## Encapsulation
- Hide implementation details
- Expose clear interfaces
- Move nested conditionals into well-named functions
## Code Quality Maintenance
- Refactor continuously
- Fix technical debt early
- Leave code cleaner than you found it
## Testing
- Write tests before fixing bugs
- Keep tests readable and maintainable
- Test edge cases and error conditions
## Version Control
- Write clear commit messages
- Make small, focused commits
- Use meaningful branch names
Structured JSON Schema
Use with automated API pipelines, LangChain, or custom image generators
{
"system_prompt": "# Clean Code Guidelines\n\n## Constants Over Magic Numbers\n- Replace hard-coded values with named constants\n- Use descriptive constant names that explain the value's purpose\n- Keep constants at the top of the file or in a dedicated constants file\n\n## Meaningful Names\n- Variables, functions, and classes should reveal their purpose\n- Names should explain why something exists and how it's used\n- Avoid abbreviations unless they're universally understood\n\n## Smart Comments\n- Don't comment on what the code does - make the code self-documenting\n- Use comments to explain why something is done a certain way\n- Document APIs, complex algorithms, and non-obvious side effects\n\n## Single Responsibility\n- Each function should do exactly one thing\n- Functions should be small and focused\n- If a function needs a comment to explain what it does, it should be split\n\n## DRY (Don't Repeat Yourself)\n- Extract repeated code into reusable functions\n- Share common logic through proper abstraction\n- Maintain single sources of truth\n\n## Clean Structure\n- Keep related code together\n- Organize code in a logical hierarchy\n- Use consistent file and folder naming conventions\n\n## Encapsulation\n- Hide implementation details\n- Expose clear interfaces\n- Move nested conditionals into well-named functions\n\n## Code Quality Maintenance\n- Refactor continuously\n- Fix technical debt early\n- Leave code cleaner than you found it\n\n## Testing\n- Write tests before fixing bugs\n- Keep tests readable and maintainable\n- Test edge cases and error conditions\n\n## Version Control\n- Write clear commit messages\n- Make small, focused commits\n- Use meaningful branch names",
"prompt_type": "agent_rule",
"framework": "cursor",
"globs": "[\"**/*\"]",
"compatible_models": [
"Claude 3.5 Sonnet",
"GPT-4o",
"Cursor AI",
"Gemini 2.5 Flash"
],
"download_filename": "clean-code.cursorrules",
"tags": [
"cursor",
"cursorrules",
"agent",
"coding",
"clean"
]
}
Internal Discovery
View All →