Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Code Quality Guidelines
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | 407% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -13% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -56% | 0% |
| case-15 | ✗→✓ | ▲ Improved | -1% | 0% |
| case-18 | ✗→✓ | ▲ Improved | 0% | 0% |
Code Quality Guidelines
Synced from https://github.com/PatrickJS/awesome-cursorrules/tree/main/rules/codequality.mdc.
Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
Make changes file by file and give me a chance to spot mistakes.
Never use apologies.
Avoid giving feedback about understanding in comments or documentation.
Don't suggest whitespace changes.
Don't summarize changes made.
Don't invent changes other than what's explicitly requested.
Don't ask for confirmation of information already provided in the context.
Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.
Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.
Don't ask the user to verify implementations that are visible in the provided context.
Don't suggest updates or changes to files when there are no actual modifications needed.
Always provide links to the real files, not x.md.
Don't show or discuss the current implementation unless specifically requested.
Other measured skills in the registry, with their headline benchmark lift.