| style-guide.mdc | Define overall coding style, such as indentation, spacing, function length, etc. |
| typescript-rules.mdc | Specify TS interface definitions, type usage preferences, etc. |
| component-patterns.mdc | Frontend component structure, naming conventions, state management methods, etc. |
| naming-rules.mdc | Naming conventions: variables, files, functions, hooks, etc. |
| api-conventions.mdc | Define API interface naming, parameters, response structure standards, etc. |
| css-guidelines.mdc | Style writing habits, such as using Tailwind/CSS-in-JS rules |
| refactor-rules.mdc | Explain specific operations of the "refactor" instruction (such as function extraction, naming improvements) |
| extract-patterns.mdc | Tell AI how to extract common components, methods, or hooks |
| generate-docs.mdc | Automatically generate comments or JSDoc/TSDoc format documentation |
| test-generation.mdc | Control auto-generated unit test styles and test coverage |
| readme-template.mdc | Define README generation structure, content modules, etc. |
| changelog-guidelines.mdc | Automatically generate Changelog format specifications, such as grouping, naming, etc. |
| comment-style.mdc | Control comment language (e.g., Chinese/English), position, conciseness, etc. |
| security-rules.mdc | Restrict dangerous operations, such as prohibiting eval, enforcing parameter validation |
| performance-hints.mdc | Define performance tip rules, such as avoiding repeated rendering, memory leaks, etc. |
| accessibility-rules.mdc | Page accessibility standards, such as label usage, color contrast, etc. |
| linter-integration.mdc | Make AI follow existing ESLint/Prettier configurations |
| team-style.mdc | Unify code style for multi-member projects |
| task-template.mdc | Automatically generate issue/task description content templates |
| commit-style.mdc | Generate Git commits that comply with commit standards (such as Conventional Commits) |
| branch-policy.mdc | Specify branch naming strategies, such as feature/xxx, hotfix/yyy |