code-reuse-enforcement

Magic strings and duplication occur when developers hardcode values instead of using existing constants, enums, or utilities. This Skill enforces discovery-first workflow: check your codebase's constants catalog before writing literals, then substitute shared resources. This centralizes changes, prevents drift, and ensures consistency across modules.

Enforce reuse by requiring developers to discover existing constants, enums, and utilities before coding. This Skill integrates discovery guidance into your workflow, blocks commits with hardcoded values, and guides feature work and refactors to use shared resources instead of duplicating literals.

A discovery-first workflow checks available constants, enums, and utilities before writing new code. This Skill applies this pattern across all development tasks—feature work, refactors, new modules—guiding developers to substitute literals with existing shared resources and preventing duplicate definitions.

Yes. This Skill detects hardcoded values and violations of constant/enum usage, then blocks commits when violations are found. It satisfies functional requirements to identify magic strings and enforce substitution with constants or utilities before code is committed.

Centralized constants and utilities reduce maintenance burden and prevent drift. When a value changes, you update one source instead of hunting through the codebase. This Skill prevents duplication by enforcing discovery before writing, ensuring all developers reference the same shared resources.

Yes. This Skill applies discovery-first guidance and hardcoded-value detection across all development tasks in the repository, ensuring consistent enforcement of constant and enum reuse regardless of module or file type.