skill-name-kebab-case

name	{"[object Object]":null}
description	{{WHAT this skill does in one sentence.}} WHEN: {{trigger phrase 1}}, {{trigger phrase 2}}, {{trigger phrase 3}}, {{e.g. "upgrade .NET Framework to .NET 9", "migrate Struts to Spring MVC", "fix CVE vulnerabilities", "containerize legacy app"}}. NOT for: {{explicit exclusions — prevents false triggering, e.g. "greenfield development, infrastructure-only changes"}}.

{{Skill Title — e.g. ".NET Framework → .NET 9 Migration Rules"}}

Purpose

{{1–2 sentences: what knowledge this skill packages and what outcome it enables.}}

Prerequisites

• {{e.g. "Assessment report (ASSESSMENT.md) exists"}}
• {{e.g. ".NET 9 SDK installed — verify with dotnet --list-sdks"}}

Procedure

Step 1 — {{e.g. "Detect the migration surface"}}

{{Concrete instructions. Prefer commands and decision tables over prose.}}

{{command or code example}}

Step 2 — {{e.g. "Apply transformation rules"}}

Source pattern	Target pattern	Notes
{{e.g. WebForms .aspx}}	{{e.g. Razor Pages}}	{{caveat}}
{{e.g. javax.servlet.*}}	{{e.g. jakarta.servlet.*}}	{{caveat}}

Step 3 — {{e.g. "Verify"}}

• {{verification item — e.g. "solution builds with zero warnings-as-errors"}}
• {{verification item — e.g. "all tests in CI suite pass"}}

Common Pitfalls

• ⚠️ {{pitfall + how to avoid — e.g. "binding redirects are not honored in .NET 9; delete them and use the SDK-style project resolution"}}
• ⚠️ {{pitfall + how to avoid}}

References

• {{Link to official migration guide / rulebook file in this folder}}
• {{e.g. ./rules/breaking-changes.md (supporting file)}}