eg-migration

Solid

Migrate an EXISTING project onto the EstreGenesis AI-native standard — audit whatever rule files it already has (CLAUDE.md, .cursor/rules/, copilot-instructions, ad-hoc AGENTS.md), then run the seed's Migration A (scattered rules, no SSoT) or Migration C (custom + seed hybrid). Invoke when the user wants to adopt EG on a project that already has agent instructions, or via /egmig. A project with no rule files at all goes to eg-bootstrap; a project already seeded goes to eg-upgrade.

AI & Automation 7 stars 0 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 78/100

Stars 20%
30
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /eg-migration (`/egmig`) — bring an existing project onto the EG standard Migration modes **M1** (Migration A) and **M3** (Migration C) of the seed. Additive by construction: the project's existing rules are *extracted and promoted*, never bulldozed. ## 0. Audit first, classify second Inventory what the project actually has — do not guess: ``` AGENTS.md · CLAUDE.md · GEMINI.md · .cursor/rules/ · .github/copilot-instructions.md .windsurfrules · .clinerules · .agent/ · .claude/ (settings, skills, hooks) ``` Then classify: | Finding | Mode | Route | |---|---|---| | `.agent/seed_prompt.md` present (any version) | **M2** | Stop — this is an upgrade, not a migration → **`/eg-upgrade`** | | Rule files exist, but no `AGENTS.md` acting as SSoT | **M1** | Seed's **Migration A** — continue | | An `AGENTS.md` exists but co-exists with divergent per-tool rules, or the project has heavy custom conventions worth keeping | **M3** | Seed's **Migration C** (hybrid) — continue | | No rule files at all | — | → **`/eg-bootstrap`** | State the mode and the evidence for it in one line before touching anything. ## 1. Fetch the seed Same tier table as `/eg-bootstrap` — default **Lite**, user's prevailing language. One tier per repo. Base: `https://raw.githubusercontent.com/SoliEstre/EstreGenesis/main/` | Tier | English | 한국어 | |---|---|---| | Master | `AI_Native_Project_Master_Seed_Prompt.md` | `AI_Native_프로젝트_마스터_시드_프롬프트.md` | | Lite | `AI_Native_Project_Seed_Prompt_Lite.md` | `AI_Nativ...

Details

Author
SoliEstre
Repository
SoliEstre/EstreGenesis
Created
2 months ago
Last Updated
today
Language
JavaScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

eg-upgrade

Upgrade a project that already runs on EstreGenesis — bring its seed up to the current release (Migration B numbered delta, additive only), refresh the installed EG plugins from the marketplace, and report what actually moved. Invoke when a new EG release lands, when the project's seed marker is behind, or via /egup. Requires .agent/seed_prompt.md with its version marker intact; a project without one goes to eg-bootstrap or eg-migration.

7 Updated today
SoliEstre
AI & Automation Listed

egmig

Short alias for eg-migration — migrate an EXISTING project (one that already has CLAUDE.md / .cursor/rules / copilot-instructions) onto the EstreGenesis standard via the seed's Migration A or C. Same behavior as /eg-migration; use whichever name you remember.

7 Updated today
SoliEstre
AI & Automation Solid

eg-bootstrap

Bootstrap a NEW project onto the EstreGenesis AI-native standard — fetch the right seed tier, install it as the project's operating charter, and run the seed's Bootstrap mode (AGENTS.md SSoT + bridges + .agent/ scaffold). Invoke on a fresh or near-empty project when the user says bootstrap / start / set up an AI-native project / EG seed, or via /egboot. Removes the copy-the-URL step: the canonical seed locations are baked in here. For an EXISTING project with its own rule files use eg-migration; for a project already on the seed use eg-upgrade.

7 Updated today
SoliEstre