coding-practices

What problem does it solve?

This Skill codifies a disciplined workflow to prevent inconsistent renames, stale prompts, schema drift, and hidden regressions when changing prompts, schemas, config-driven behavior, or UI labels across backend, frontend, storage, and tests.

Core Features & Use Cases

• Centralize text and prompts: Keep prompts, templates, and user-facing text in configuration files rather than hard-coded locations.
• Consistent renames and schema changes: Rename labels and fields consistently across backend, frontend, storage, scripts, prompts, and tests within the same change.
• Safe cleanup and migrations: Remove dead paths and legacy helpers when appropriate, add migrations only when live data must be preserved, and avoid temporary compatibility code without a removal plan.
• Use Case: When rolling out a label or schema change for a new country or policy, update the source-of-truth config first, propagate changes across the codebase in a single pass, and update tests before deployment.

Quick Start

Apply the coding-practices checklist before implementing, refactoring, or reviewing any change that touches prompts, schemas, config-driven behavior, or UI labels.