agentleFS
Sign inStart free
colasamacolasama/MahoShojo-Generator/.agents/skills/platform-migration/SKILL.md

platform-migration

Skill167 starsChanged 27 days agoApache-2.0View on GitHub

Use for platform-rearchitecture, runtime migration, hosted/local routing changes, storage/session/DR migrations, or staged movement between old and new application boundaries in MahoShojo-Generator. Do not use for isolated feature work inside one already-stable runtime.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read docs/AGENTS.md, docs/README.md, the relevant topic page, accepted architecture/ADR/spec, migration plan and current code/CI facts.

    line 12
  2. Distinctive:

    Write down current state, target state and the exact migration gap.

    line 13
  3. Distinctive:

    Keep feature flags/configuration from becoming a way to bypass accepted MUST/MUST NOT semantics.

    line 16
  4. Very specific:

    Update migration/topic/status documentation when actual state changes.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Platform Migration

Web/Desktop 产品共源迁移同时使用双端共源切片模板与验收指南：先对照实际页面、状态、CSS/资源与副作用，再分共享层和宿主适配；按风险裁剪模板，不增加全站清单/hash/报告 marker 门禁。阶段与进度仍只维护唯一 Desktop 计划。

Workflow

  1. Read docs/AGENTS.md, docs/README.md, the relevant topic page, accepted architecture/ADR/spec, migration plan and current code/CI facts.
  2. Write down current state, target state and the exact migration gap. Do not describe target architecture as already deployed.
  3. Preserve trust boundaries and compatibility while moving one coherent seam at a time. Prefer adapters/versioned contracts over hidden app→app coupling.
  4. For stateful components, reason explicitly about ownership, idempotency, retries, fencing, failover, rollback and old/new coexistence.
  5. Keep feature flags/configuration from becoming a way to bypass accepted MUST/MUST NOT semantics.
  6. Validate the migrated seam with targeted tests and realistic recovery/failure cases. Expand to cross-runtime/full verification at cutover-level boundaries.
  7. Update migration/topic/status documentation when actual state changes; do not rewrite historical reports to manufacture consistency.

High-risk boundary

Production deploy/cutover, remote migration, secret changes and irreversible data operations require explicit user authorization even if the implementation is ready.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free