Some feedback:

1. Return values:

   • Suggestion: Use floating-point numbers instead of strings for return values.
   • Benefit: This eliminates rounding issues and simplifies validation.
   • Improvement: Implement approximate equality checks for more reliable comparisons.

2. Description structure and formatting:

   • Suggestion: Restructure the description for better clarity and readability.
   • Improvement: Use concise language and clear formatting (e.g., bullet points, numbered lists).
   • Goal: Enhance understanding and reduce ambiguity for participants.

3. Specification Style Improvement:

   • Replace code-like specifications with clear, human-readable requirements.
   • Use concise language to describe expected inputs, outputs, and behaviors.
   • Avoid verbose or repetitive descriptions.
   • Avoid using your own code as specification for the formulas.

4. Hue value representation:

   • Issue: Adding 360 to hue and then treating it as 0 is redundant.
   • Suggestion: Simplify by using 0 directly where applicable.
   • Benefit: Reduces confusion and eliminates unnecessary steps.

Yes! You really should.

That's the only challenge with this kata, figuring out the formulas. Other than that, it's just switch statements, if/else, variables, math, and rounding.

Duplicate issue

Pro tip: you can write code that writes code ;)