Improve code readability and maintainability by giving meaningful names to numeric literals.

Advise developers to replace unexplained numbers with descriptive constants.

When a numeric literal appears in code whose purpose is not immediately clear, or when the same number appears in multiple places.

Any source code where numeric literals are used, especially in configuration, calculations, or magic numbers.

Replace magic number with named constant

Replace numeric literal with a named constant declaration

[MAGIC_NUMBER] -> [CONSTANT_NAME]

• number
• constant
• constant name
• magic number
• literal

• Replace 3.14 with PI
• 31536000 with SECONDS_PER_YEAR

Choosing non-descriptive constant names, exposing constants unnecessarily, using macros without type safety.

Contrast with 'Keep magic numbers' (rare) or 'Use enum for related constants'.

Avoid over-abstracting trivial numbers; avoid misleading constant names.

• Refactoring
• Code Quality
• Magic Number Elimination

The constant should be scoped appropriately (private, public) and have a clear, domain-specific name.

Improves readability, reduces errors when values need to change, and aids documentation.

Think of a magic number as a secret code; give it a name.

Place symbolic constants in a dedicated module or class to keep the global namespace clean and to group related constants together.

Replace Magic Number with Enum or Constant Class for related constants