Cursor Angular 编码规范：来自 PatrickJS/awesome-cursorrules (40k stars) 的 ang，适用于各类文档与内容的智能化处理。
Cursor Angular 编码规范：来自 PatrickJS/awesome-cursorrules (40k stars) 的 ang，适用于各类文档与内容的智能化处理。
**文件来源:** PatrickJS/awesome-cursorrules → `rules/angular-novo-elements-cursorrules-prompt-file.mdc`
**原仓库:** https://github.com/PatrickJS/awesome-cursorrules
**评分:** ⭐ 仓库 40k stars (社区最权威 Cursor rules 合集)
把 `angular-novo-elements-cursorrules-prompt-file.mdc` 这条 Cursor 编码规则打包成可调用的 AI skill,帮你把代码生成统一到一致的标准上。
> Cursor rules for Angular development with Novo Elements UI library.
globs: **/*
alwaysApply: false
---
# .cursor
rules
# General rules
- Do not apologize
- Do not thank me
- Talk to me like a human
- Verify information before making changes
- Preserve existing code structures
- Provide concise and relevant responses
- Verify all information before making changes
You will be penalized if you:
- Skip steps in your thought process
- Add placeholders or TODOs for other developers
- Deliver code that is not production-ready
I'm tipping $9000 for an optimal, elegant, minimal world-class solution that meets all specifications. Your code changes should be specific and complete. Think through the problem step-by-step.
YOU MUST:
- Follow the User's intent PRECISELY
- NEVER break existing functionality by removing/modifying code or CSS without knowing exactly how to restore the same function
- Always strive to make your diff as tiny as possible
# File-by-file changes
- Make changes in small, incremental steps
- Test changes thoroughly before committing
- Document changes clearly in commit messages
# Code style and formatting
- Follow the project's coding standards
- Use consistent naming conventions
- Avoid using deprecated functions or libraries
# Debugging and testing
- Include debug information in log files
- Write unit tests for new code
- Ensure all tests pass before merging
# Project structure
- Maintain a clear and organized project structure
- Use meaningful names for files and directories
- Avoid clutter by removing unnecessary files
# Clean Code
Don't Repeat Yourself (DRY)
Duplication of code can make code very difficult to maintain. Any change in logic can make the code prone to bugs or can make the code change difficult. This can be fixed by doing code reuse (DRY Principle).
The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system".
The way to achieve DRY is by creating functions and classes to make sure that any logic should be written in only one place.
Curly's Law - Do One Thing
Curly's Law is about choosing a single, clearly defined goal for any particular bit of code: Do One Thing.
Curly's Law: A entity (class, function, variable) should mean one thing, and one thing only. It should not mean one thing in one circumstance and carry a different value from a different domain some other time. It should not mean two things at once. It should mean One Thing and should mean it all of the time.
Keep It Simple Stupid (KISS)
The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided.
Simple code has the following benefits:
less time to write
less chances of bugs
easier to understand, debug and modify
Do the simplest thing that could possibly work.
Don't make me think
Code should be easy to read and understand without much thinking. If it isn't then there is a prospect
...(完整内容在原仓库)...有问题或建议,在本 skill 下留言。
把 `angular-novo-elements-cursorrules-prompt-file.mdc` 这条 Cursor 编码规则打包成可调用的 AI skill,帮你把代码生成统一到一致的标准上。
> Cursor rules for Angular development with Novo Elements UI library.