skills.rest
martiendejong
martiendejongCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

terminology-migration

Audit and migrate terminology across backend and frontend codebases.

1|Updated Jan 11, 2026
Search Tags:#frontend#codebase#backend#migration#deprecation#refactor#terminology
One-click install
npx skills add https://github.com/martiendejong/autonomous-dev-system --skill terminology-migration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: terminology-migration
Source: https://github.com/martiendejong/autonomous-dev-system/tree/main/.claude/skills/terminology-migration
Command: npx skills add https://github.com/martiendejong/autonomous-dev-system --skill terminology-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive codebase-wide terminology refactoring when field names, method names, or concepts need to be migrated. Use when discovering misleading names, migrating from old to new terminology, or ensuring consistency across backend and frontend.

Core Features & Use Cases

  • Audit across backend and frontend to locate mismatched or outdated terms.
  • Plan, rename, and propagate terminology changes through models, services, controllers, APIs, and UI.
  • Use Case: A large project with naming drift between API, database, and UI can be unified by a single migration process.

Quick Start

Run the terminology-migration workflow to audit occurrences, plan changes, and apply a codebase-wide refactor across backend and frontend.

Frequently Asked Questions about terminology-migration

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

FAQPage Schema
How do I refactor outdated terminology across both backend and frontend codebases?▼

To refactor terminology across backend and frontend codebases, you can run an end-to-end migration workflow that audits occurrences, plans changes, and propagates renames through models, services, controllers, APIs, and UI.

What is the best way to fix naming drift between my API, database, and UI?▼

Fixing naming drift between API, database, and UI requires a codebase-wide terminology migration that audits mismatched terms and unifies them through a structured plan, rename, and validate process.

Can I use a single process to migrate terminology through models, services, and docs?▼

Yes, a single terminology migration process can propagate changes through models, services, controllers, and documentation, ensuring consistency while enforcing audit, plan, migrate, and validate phases.

Does terminology refactoring include build verification and deprecation handling?▼

Terminology refactoring includes build verification and deprecation handling to safely migrate outdated concepts, verifying that changes do not break existing frontend or backend functionality.

When should I run an end-to-end terminology audit instead of manual renaming?▼

Run an end-to-end terminology audit instead of manual renaming when a large project has widespread naming drift, ensuring all mismatched field names and concepts are systematically located and updated.

Related Skills

Explore More Software Engineering Skills→
andregusman-raizandregusman-raiz
19

ag-mapear-integracao

Map external-system integration touchpoints with the rAIz Platform across seven dimensions.

Community
Intermediate
jordanhubbardjordanhubbard
105

documentation-manager

Update project documentation to reflect code changes and evolving architecture.

Community
Intermediate
AshenDulsankaAshenDulsanka
4

grill-with-docs

Validate project plans against domain models and update documentation inline.

Community
Intermediate
jangtrinhjangtrinh

ck:project-organization

Standardize project file and directory organization with naming patterns and markdown templates.

Community
Intermediate