update rules
This commit is contained in:
parent
71b407c211
commit
154d15188d
1 changed files with 16 additions and 6 deletions
|
@ -1,9 +1,19 @@
|
||||||
---
|
---
|
||||||
description:
|
description: A very basic ruleset
|
||||||
globs:
|
globs:
|
||||||
|
alwaysApply: true
|
||||||
---
|
---
|
||||||
|
# Basic rules
|
||||||
|
|
||||||
# Your rule content
|
- Always use functional code
|
||||||
|
- Always prefer simple, easy-to-understand code
|
||||||
- You can @ files here
|
- Always create a .gitignore file with the build directory in it.
|
||||||
- You can use markdown but dont have to
|
- Always code what the user specifies and that of which it is obvious that its within the user's specifications
|
||||||
|
- If not sure about something, ask the user
|
||||||
|
- Keep .gitignore up to date
|
||||||
|
- Comment code well
|
||||||
|
- NEVER EVER EDIT .env files
|
||||||
|
- Don't change config files unless needed
|
||||||
|
- If function line count is above 55, split into multiple smaller functions or refactor
|
||||||
|
- If file line count above 400 split into more files or refactor
|
||||||
|
- Feel free to auto-apply any changes that follow these or any other rules.
|
Loading…
Add table
Reference in a new issue