skills.rest
The-INTJ
The-INTJCOMMUNITY
Explore all skills by this author →
GitHub

migrate-to-config-api

Automate migration from hard-coded contestTemplates to a centralized /api/contest/configs API.

1|Updated Jan 7, 2025
Search Tags:#frontend#backend#migration#seed#breaking-change#config-api#contest-config
One-click install
npx skills add https://github.com/The-INTJ/item-dc-calculator --skill migrate-to-config-api
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-to-config-api
Source: https://github.com/The-INTJ/item-dc-calculator/tree/main/.claude/skills/migrate-to-config-api
Command: npx skills add https://github.com/The-INTJ/item-dc-calculator --skill migrate-to-config-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guided workflow replaces hard-coded contestTemplates with a centralized /api/contest/configs API, enabling automated seeding, API-driven contest configuration, and simplified config management across the project.

Core Features & Use Cases

  • 7-phase implementation guide covering backend seeding, adapter updates, frontend config selection, and safe deprecation of old defaults.
  • End-to-end migration blueprint including backend initialization, API integration, frontend wiring, and validation to ensure contests always embed valid configs.
  • Incremental rollout plan with clear milestones, tests, and rollback steps for production environments.

Quick Start

Run the migration workflow with a phase number to begin the guided migration (e.g., /migrate-to-config-api 1).

Frequently Asked Questions about migrate-to-config-api

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

FAQPage Schema
How do I migrate hard-coded contest templates to a centralized config API?▼

You can migrate hard-coded contest templates to a centralized config API by running a guided seven-phase workflow that automates backend seeding, adapter updates, frontend config selection, validation, and testing.

What is a centralized contest config API and when do I need it?▼

A centralized contest config API is an endpoint like /api/contest/configs that replaces hard-coded contestTemplates. You need it when you want to enable automated seeding, API-driven contest configuration, and simplified config management across both backend and frontend systems.

How do I start the contest config migration workflow phase by phase?▼

To start the contest config migration, run the workflow command with a specific phase number. This initiates the guided migration process, beginning with backend initialization and seeding before moving to API integration and frontend updates.

Does the config API migration support backward-compatibility and rollback?▼

Yes, the config API migration supports backward-compatibility and rollback through an incremental rollout plan. It includes clear milestones, tests, safe deprecation of old defaults like DEFAULT_CONFIG, and robust error handling to ensure safe startup.

Can I use this migration workflow for both backend and frontend contest configuration?▼

Yes, you can use this migration workflow for both backend and frontend contest configuration. The end-to-end blueprint covers backend initialization and seeding, adapter updates, and frontend config selection to ensure all layers integrate with the centralized API.

Related Skills

Explore More Software Engineering Skills→
vlad-ryzhkovvlad-ryzhkov
25

repo-scout

Audit Go backend repositories for API endpoints, infrastructure, and test coverage.

Community
Intermediate
thrawn01thrawn01
11

babysit-pr

Monitor and fix CI failures and automated review comments on a pull request.

Community
Advanced
zinohomezinohome
1

integration-test-builder

Generate integration tests for API endpoints with database seeding and CI strategies.

Community
Advanced
JoniSirvioJoniSirvio

onboard

Design onboarding systems with empty states, tooltips, and guided tours.

Community
Intermediate