skills.rest
pebblepaw
pebblepawCOMMUNITY
Explore all skills by this author →
GitHub

coding-practices

Coordinate cross-cutting updates to prompts, schemas, configuration, and UI labels across codebases.

Updated Mar 5, 2026
Search Tags:#refactoring#migration#config#prompts#code-review#tests#developer-guidelines
One-click install
npx skills add https://github.com/pebblepaw/MiroWorld --skill coding-practices
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-practices
Source: https://github.com/pebblepaw/MiroWorld/tree/main/.codex/skills/coding-practices
Command: npx skills add https://github.com/pebblepaw/MiroWorld --skill coding-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about coding-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure consistent schema and config updates across backend and frontend?▼

To ensure consistent schema and config updates, modify the source-of-truth configuration first, then perform a repository-wide search to coordinate all call sites across backend, frontend, storage, and tests in a single pass.

What is the best way to manage cross-cutting prompt and UI label refactoring?▼

Managing cross-cutting prompt and UI label refactoring requires centralizing text in configuration files rather than hard-coded locations, ensuring consistent renames across scripts, prompts, and tests without stale references.

When do I need a database migration during a schema change?▼

You need a database migration during a schema change only when preserving live data. Avoid adding temporary compatibility code without a removal plan, and remove dead paths and legacy helpers when appropriate.

How do I prevent hidden regressions when changing configuration-driven behavior?▼

Preventing hidden regressions during configuration-driven behavior changes requires updating tests to reflect new contracts, verifying repository-wide search for stale references, and applying changes during code reviews.

Does this approach work for rolling out policy changes across multiple application layers?▼

Yes, this approach works for rolling out policy changes by updating the source-of-truth config first, propagating schema and label changes across the codebase in a single pass, and updating tests before deployment.

Why does stale configuration text cause schema drift in repository updates?▼

Stale configuration text causes schema drift when hard-coded prompts and labels are not centralized, leading to inconsistent renames and hidden regressions across backend, frontend, and storage layers during updates.

Related Skills

Explore More Software Engineering Skills→
nholder88nholder88
2

draft-repo-readme

Draft a README from a repository's source files and commit history.

Community
Intermediate
ulpi-ioulpi-io
2

run-parallel-agents-feature-debug

Orchestrate parallel debugging agents across Laravel, Next.js, and NestJS subsystems.

Official
Advanced
matchojeckimatchojecki
1

implement-spec

Coordinate subagents to implement phases of a target specification with code-review gating.

Community
Advanced
TheFJKTheFJK
2

ubersimplify-pipeline

Automate codebase simplification with multiple lenses and refactoring into a single pull request.

Community
Advanced