How do I install the Classic To Default Sync skill?

Run npx skillmds@latest add misonl/classic-to-default-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Classic To Default Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Classic To Default Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Classic To Default Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Classic To Default Sync?

misonl (@misonl) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Classic To Default Sync by misonl — Agent Skill

Name: Classic To Default Sync
Author: misonl

Classic To Default Sync

Inspect a given commit's web/classic changes and sync all features/fixes to web/default. Use when the user provides a commit ID and wants to audit whether web/default already has the same features as web/classic, port missing features, improve suboptimal implementations, fix bugs, and remove redundant code. Trigger phrases include: "/classic-to-default-sync <hash>", "classic-to-default-sync <hash>", "sync classic to default", "port from classic", "compare classic commit", "classic 和 default 对比", "把这次 classic 的修改同步到 default", "查看这次提交 classic 中的修改并同步", or any request supplying a commit hash together with classic/default comparison intent.

misonl 052854a 3.7 KB Updated Sep 17, 2026

File contents

Classic-to-Default Sync

Given a commit ID, audit all web/classic changes and ensure web/default reaches feature parity with the best possible implementation.

Input

The user must supply a <commit-id>.

Workflow

Step 1 — Extract classic diff

git show <commit-id> -- web/classic

Read every changed file in web/classic. Identify the logical changes (new features, UI/UX improvements, bug fixes, config tweaks, removed dead code, etc.) — not just line diffs.

Step 2 — Map to default counterparts

For each logical change found in Step 1, locate the equivalent file(s) in web/default/src/. Use Glob/Grep/SemanticSearch as needed. Consider that:

web/classic uses React 18 + Vite + Semi Design
web/default uses React 19 + Rsbuild + Radix UI + Tailwind CSS
Component names, file paths, and API shapes may differ; match by functionality, not filename.

Step 3 — Triage each change

Classify every logical change as one of:

Status	Meaning	Action
OK	Already present & optimal	No action needed
IMPROVE	Present but suboptimal	Improve: logic, layout, style, or code quality
MISSING	Missing	Implement from scratch in default's stack

Step 4 — Implement

For each IMPROVE or MISSING item:

Read the target file(s) in web/default before editing (required by project conventions).
Implement using web/default conventions:
- React 19 patterns (hooks, Suspense, etc.)
- Radix UI primitives where applicable
- Tailwind CSS for styling (no inline styles or Semi Design imports)
- useTranslation() + t('English key') for all user-visible strings
- TypeScript — explicit types, no any
- No dead code, no redundant comments
Follow Rule 6 (pointer types for optional relay DTOs) if touching relay-related TS types.
After editing, run ReadLints on changed files and fix any introduced lint errors.

Step 5 — i18n

If any new user-visible strings were added, run the i18n sync:

cd web/default && bun run i18n:sync

Then add missing translations for all supported locales (en, zh, fr, ja, ru, vi) following the i18n-translate skill.

Step 6 — Report

Summarise the work in a concise table:

#	Change (from classic commit)	Status	Action taken
1	...	OK / IMPROVE / MISSING	None / Improved / Implemented

If every item is OK with no action needed, simply reply: "已完成 - web/default 已具备此次提交的所有功能，且实现质量良好，无需修改。"

Quality bar

No unused imports, variables, or components
No commented-out code left behind
Consistent naming with surrounding web/default code
All interactive elements accessible (keyboard nav, ARIA labels where Radix doesn't provide them automatically)
No regressions: existing behaviour in web/default must not break

---name: classic-to-default-syncdescription: Inspect a given commit's web/classic changes and sync all features/fixes to web/default. Use when the user provides a commit ID and wants to audit whether web/default already has the same features as web/classic, port missing features, improve suboptimal implementations, fix bugs, and remove redundant code. Trigger phrases include: "/classic-to-default-sync <hash>", "classic-to-default-sync <hash>", "sync classic to default", "port from classic", "compare classic commit", "classic 和 default 对比", "把这次 classic 的修改同步到 default", "查看这次提交 classic 中的修改并同步", or any request supplying a commit hash together with classic/default comparison intent.---# Classic-to-Default SyncGiven a **commit ID**, audit all `web/classic` changes and ensure `web/default` reaches feature parity with the best possible implementation.## InputThe user must supply a `<commit-id>`.## Workflow### Step 1 — Extract classic diff```bashgit show <commit-id> -- web/classic```Read every changed file in `web/classic`. Identify the **logical changes** (new features, UI/UX improvements, bug fixes, config tweaks, removed dead code, etc.) — not just line diffs.### Step 2 — Map to default counterpartsFor each logical change found in Step 1, locate the equivalent file(s) in `web/default/src/`. Use Glob/Grep/SemanticSearch as needed. Consider that:- `web/classic` uses **React 18 + Vite + Semi Design**- `web/default` uses **React 19 + Rsbuild + Radix UI + Tailwind CSS**- Component names, file paths, and API shapes may differ; match by **functionality**, not filename.### Step 3 — Triage each changeClassify every logical change as one of:| Status | Meaning | Action ||--------|---------|--------|| OK | Already present & optimal | No action needed || IMPROVE | Present but suboptimal | Improve: logic, layout, style, or code quality || MISSING | Missing | Implement from scratch in default's stack |### Step 4 — ImplementFor each **IMPROVE** or **MISSING** item:1. **Read the target file(s) in `web/default`** before editing (required by project conventions).2. Implement using `web/default` conventions: - React 19 patterns (hooks, Suspense, etc.) - Radix UI primitives where applicable - Tailwind CSS for styling (no inline styles or Semi Design imports) - `useTranslation()` + `t('English key')` for all user-visible strings - TypeScript — explicit types, no `any` - No dead code, no redundant comments3. Follow **Rule 6** (pointer types for optional relay DTOs) if touching relay-related TS types.4. After editing, run `ReadLints` on changed files and fix any introduced lint errors.### Step 5 — i18nIf any new user-visible strings were added, run the i18n sync:```bashcd web/default && bun run i18n:sync```Then add missing translations for all supported locales (en, zh, fr, ja, ru, vi) following the **i18n-translate** skill.### Step 6 — ReportSummarise the work in a concise table:| # | Change (from classic commit) | Status | Action taken ||---|------------------------------|--------|--------------|| 1 | ... | OK / IMPROVE / MISSING | None / Improved / Implemented |If every item is OK with no action needed, simply reply: **"已完成 - web/default 已具备此次提交的所有功能，且实现质量良好，无需修改。"**## Quality bar- No unused imports, variables, or components- No commented-out code left behind- Consistent naming with surrounding `web/default` code- All interactive elements accessible (keyboard nav, ARIA labels where Radix doesn't provide them automatically)- No regressions: existing behaviour in `web/default` must not break

Frequently asked questions