kalahari-coding

Kalahari coding standards provide mandatory patterns for UI, logging, icons, and configuration access to ensure consistency across contributors and automation. Apply these conventions to all code modules referencing core Kalahari classes for icons, themes, translations, and build processes.

Fetch icons and theme colors through standardized APIs rather than hardcoding paths. Kalahari standards enforce consistent color management across UI components by centralizing theme access and forbidding direct color hardcoding.

Use SettingsManager and tr() functions as mandated by Kalahari standards. This ensures all UI strings route through translation infrastructure and configuration is accessed consistently across the project.

Kalahari coding standards define mandatory naming rules and singleton usage patterns to prevent anti-patterns. These conventions apply to all contributors and ensure predictable, maintainable code structure across modules.

Yes. Kalahari standards cover build process guidance and MCP tooling configuration alongside code conventions. They apply to all code-related contributors and automation agents handling project builds and integrations.

Kalahari forbids hardcoded icon paths, direct color values, non-standard configuration access, untranslated UI strings, and improper singleton usage. The standards impose mandatory alternatives covering icons, themes, configuration, translations, layouts, naming, and build processes.