silkyland
UserAgent skill: evidence-based feasibility + migration strategy for architecture transformations (language ports, standalone→SaaS, vanilla→framework) — dependency census, difficulty heatmap, GO/PARTIAL/NO-GO verdict, parity-gated roadmap
Categories
Indexed Skills (4)
transform-my-repo
Feasibility analysis and migration strategy for architecture transformations: language ports (PHP to Python, Rust to Go), framework migrations (Vue or React SPA to Next.js), major version upgrades, monolith to microservices and back, database migrations, cloud/container/ serverless re-hosting, sync to event-driven, REST to GraphQL/gRPC, UI platform shifts, standalone to SaaS, and vanilla to framework. Produces an evidence-based GO/PARTIAL/NO-GO verdict with a worth-it test against the do-nothing baseline (dependency census verified in the target ecosystem, semantic gap analysis, per-module difficulty heatmap), then a migration roadmap with behavioral parity gates and rollback points. Allowed to recommend NOT migrating. Use when the user asks to migrate, port, rewrite, re-platform, upgrade a major version, split or merge services, switch databases or API paradigms, asks whether a migration is worth it, or mentions transform-my-repo or /transform-my-repo.
deep-plan-ingest
Distills a completed deep-plan document (e.g. docs/PLAN.md) into durable project knowledge files: AGENTS.md (agent operating rules and verified ground truth), docs/ARCHITECTURE.md (component map, data flow, framework mechanisms with citations), and ROADMAP.md (phased roadmap with live status). Carries only VERIFIED evidence forward, re-checks stale claims, and merges into existing files instead of overwriting. Use after a deep-plan finishes, when the user mentions deep-plan-ingest or ingest the plan, or asks to generate/update AGENTS.md, ARCHITECTURE.md, or ROADMAP.md from a plan.
deep-plan
Research-first, evidence-first implementation planning in seven gated phases: frame the task, inventory the real codebase, verify ground truth from vendor source or official docs, adversarially audit existing code, analyze gaps, commit to design decisions, and write a phased plan document with timeline, risks, and verification. Enforces "no claim without evidence, no design before research". Use when the user asks to plan, design, architect, audit, or review before implementing a feature, refactor, migration, or system, or mentions deep-plan, /deep-plan, or Plan mode.
clean-slate
Re-initializes a project's agent knowledge from scratch when the existing knowledge files (CLAUDE.md, AGENTS.md, cursor rules, architecture docs, roadmaps, old plans) have rotted, contradict the code, or accumulated too much noise to patch. Salvages still-true facts by verifying them against the code, asks the user about backup before deleting anything, re-reads the actual codebase fresh, interviews the user on the intended direction, and rebuilds strong AGENTS.md, docs/ARCHITECTURE.md, and ROADMAP.md. Use when the user asks to reset, re-initialize, or rebuild project knowledge or architecture docs, says the docs are stale or wrong, or mentions clean-slate or /clean-slate.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.