Commands

Classnames

Always use specific class names for containers. Avoid general selectors like & h1 {} to prevent unintended global styling.

Good coding

• KISS (Keep It Simple, Stupid) Simplicity wins. Avoid unnecessary complexity.
• DRY (Don't Repeat Yourself) Eliminate duplicate code. Reuse logic smartly to reduce bugs.
• SRP (Single Responsibility Principle) Each module/class should do one thing and do it well.
• Modularity Break systems into small, independent parts for easier testing and updates.
• Readability Over Cleverness Clear, human-friendly code is better than overly clever tricks.
• Test Early, Test Often Catch bugs early when they’re cheaper to fix. Write tests as you build.
• Refactor Regularly Continuously improve code structure without changing behavior.
• Use the Right Tool for the Job Choose the best language, library, or pattern for the task.
• Separation of Concerns Keep UI, business logic, and data in separate layers.
• Think in Systems Zoom out to understand how components interact and fail together.
• Build clean, maintainable, and robust software by sticking to these principles.