code-quality

Enforce code quality by applying schema validation to inputs, throwing errors on violations instead of logging, avoiding union types, and eliminating defensive try/catch blocks. This ensures consistent, maintainable code across all changes and CI pipelines.

Use full, descriptive names instead of abbreviations—for example, write `number` rather than `num`. Clear naming conventions reduce confusion, enhance maintainability, and make code easier to collaborate on across teams.

Replace defensive try/catch blocks and forgiving logic with strict input validation using schema libraries and immediate error throwing when expectations are violated. This prevents bugs and makes failure modes explicit.

Prioritize editing existing files over creating new ones, and require user confirmation before generating new markdown files. This prevents file sprawl and keeps the codebase organized and maintainable.

Yes, emojis and unicode characters are encouraged in comments, commit messages, and documentation headers to enhance clarity and engagement while maintaining code professionalism.

Apply code quality enforcement before making changes or during pull request review to automatically check adherence to strict guidelines, preventing bugs and improving overall code health early.