review-constants-to-configs

This Skill evaluates hardcoded constants by analyzing their behavioral, timing, and appearance controls to assess suitability for user modification. It identifies magic numbers, timeouts, sizes, and intervals that would benefit from being promoted to a user-configurable registry.

The best way to refactor constants to configurable settings is to generate a detailed integration plan specifying the config section, key name, type, and default value. This allows end-users to adjust tuning parameters like timeout durations without requiring code changes.

You need to promote hardcoded values to configurable settings when tuning parameters like timeout durations or UI element sizes require frequent adjustment by end-users. Moving them to a configuration registry eliminates code changes and improves overall maintainability.

To plan a config registry integration, analyze hardcoded constants and outline requirements including the config section, key name, data type, and default values. This systematic approach ensures all necessary metadata is prepared for registry implementation.

Yes, you can evaluate which constants need configurability by assessing their impact on behavior, timing, and appearance. The Skill reviews source code constants to determine which ones genuinely benefit from user-level modification based on actual user need.