Maintain consistent naming patterns throughout your codebase, following established conventions and ensuring uniformity within the same context. This includes using correct syntax for configuration values, matching case conventions for related identifiers, organizing entries systematically (like alphabetically), and choosing descriptive names that clearly indicate purpose.
Examples of good practices:
underlined instead of underline in modifier arrays to match the established APIselectionfg consistently instead of mixing selectionFG and selectionfghx_launcher.sh instead of generic names like hx[language-server.<name>] for clarityInconsistent naming creates confusion, makes code harder to maintain, and can lead to subtle bugs when identifiers don’t match their expected format.
Enter the URL of a public GitHub repository