validation-policy

Numeric input validation enforces a standardized sequence: check finite values, verify integers, validate ranges, then apply domain-specific checks. This Skill provides unified error handling and JSDoc documentation so all public functions follow the same validation policy across your project.

Runtime validation applies four sequential checks: finite value check first, then integer check, then range validation, then domain-specific validation. This order catches errors early and ensures consistent error messages in Japanese throughout your codebase.

Error handling combines input validation with standardized messages and JSDoc @throws documentation. This Skill enforces a unified error-messaging policy across scoring, coordinates, and boundary inputs so callers receive predictable, localized error feedback.

Yes. This Skill applies validation policies to all public function inputs without requiring dependencies or components. It guides implementation, testing, and code reviews using consistent validation order and standardized error messages.

Validation covers scoring calculations, coordinate operations, and boundary inputs. Domain-specific checks follow the standard finite-integer-range sequence, with JSDoc constraints documenting @param limits and expected @throws errors for each function.