Refactoring 032 - Apply Consistent Style Rules
Make your code look the same everywhere for everybody

I’m a senior software engineer loving clean code, and declarative designs. S.O.L.I.D. and agile methodologies fan.
Search for a command to run...
Make your code look the same everywhere for everybody

I’m a senior software engineer loving clean code, and declarative designs. S.O.L.I.D. and agile methodologies fan.
No comments yet. Be the first to comment.
The perfect prompt doesn't instruct the model on what it already knows how to do.

Approve the logic once, then let it run the same way forever.

Different stages need different brains.

One Second Brain doesn't scale past one skull.

Style errors double when nobody enforces them.

TL;DR: When machines generate large amounts of code, you need to apply one consistent style to all files.
class User{
private name;
public email;
constructor(name,email) {
this.name=name;
this.email = email;
}
private validateEmail() {
return this.email.includes('@');
}
public getName(){
return this.name;
}
public setName(newName)
{
this.name=newName;
}
}
class User {
public email;
private name;
// Step 1: Choose consistent indentation (2 spaces)
// Step 4: Public methods before private ones
constructor(name, email) {
this.name = name;
this.email = email;
}
public getName() {
return this.name;
}
// Step 3: Standardize spacing around operators
public setName(newName) {
this.name = newName;
}
// Step 2: Apply uniform brace placement
private validateEmail() {
return this.email.includes('@');
}
}
[X] Automatic
This refactoring is safe, as it only changes visual formatting without altering the code's behavior.
Modern IDEs and formatters can apply these changes automatically without risk of introducing bugs.
You improve readability and make your code easier to navigate.
You remove the mental overhead of switching styles across files.
Your code reviews will focus on meaningful semantic changes.
Consistent formatting reduces cognitive load when reading code, makes code reviews more focused on logic rather than style, and enables better collaboration between team members.
You also establish a foundation for maintainable code that new developers can understand quickly.
You create clearer visual representations that mirror the logical structure of your real-world domain.
When formatting reflects the hierarchical relationships and importance levels in your business logic, you maintain better alignment between the problem space and solution space.
You need team-wide agreement on formatting standards to be effective.
Different team members might have strong preferences for specific styles.
Large codebases require significant time investment and coordination to apply uniform styling across all files.
Suggested Prompt: 1. Choose a consistent indentation standard 2. Apply uniform brace placement rules throughout files 3. Standardize spacing around operators and keywords 4. Organize methods with public declarations before private ones 5. Configure automated formatting tools to maintain standards 6. Create tests to enforce your rules
| Without Proper Instructions | With Specific Instructions |
| ChatGPT | ChatGPT |
| Claude | Claude |
| Perplexity | Perplexity |
| Copilot | Copilot |
| You | You |
| Gemini | Gemini |
| DeepSeek | DeepSeek |
| Meta AI | Meta AI |
| Grok | Grok |
| Qwen | Qwen |
[X] Beginner
Image by Michal Jarmoluk on Pixabay
This article is part of the Refactoring Series.