v0.8.0 "Polish" - add migration guide skill, common pitfalls across all 30 skills

New skill:
- steam-migration-guide: platform migration (Epic/GOG/itch.io to Steam), engine SDK integration (Unity/Unreal/Godot), feature parity mapping, migration checklist

Quality improvements:
- Added Common Pitfalls section to all 30 skills (3-6 actionable pitfalls each)

Plugin now at 30 skills, 9 rules, 16 MCP tools. Tests: 739 passed.

Made-with: Cursor

Author: TMHSDigital

.cursor-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "name": "steam-cursor-plugin",
   "displayName": "Steam Developer Tools",
-  "version": "0.7.0",
-  "description": "Integrates Steam and Steamworks APIs for game developers and power users. 29 skills covering store data, multiplayer, cloud saves, leaderboards, input, inventory, social, profiles, comparisons, reviews, pricing, market research, wishlists, CI/CD, release checklists, steamcmd, community, store pages, pricing strategy, DLC, playtesting, bug reporting, anti-cheat, and testing sandbox - plus 9 rules. Companion Steam MCP server provides 16 API tools.",
+  "version": "0.8.0",
+  "description": "Integrates Steam and Steamworks APIs for game developers and power users. 30 skills covering store data, multiplayer, cloud saves, leaderboards, input, inventory, social, profiles, comparisons, reviews, pricing, market research, wishlists, CI/CD, release checklists, steamcmd, community, store pages, pricing strategy, DLC, playtesting, bug reporting, anti-cheat, testing sandbox, and platform migration - plus 9 rules. Companion Steam MCP server provides 16 API tools.",
   "author": {
     "name": "TMHSDigital",
     "url": "https://github.com/TMHSDigital"

CHANGELOG.md

@@ -5,6 +5,19 @@ All notable changes to Steam Developer Tools will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.8.0] - 2026-03-28
+
+### Added
+
+- **steam-migration-guide** skill: migrating games to Steam from Epic, GOG, itch.io — engine-specific SDK integration (Unity, Unreal, Godot), feature parity mapping, store page strategy, and technical migration checklist
+- **Common Pitfalls sections** added to all 30 skills — each skill now includes 3-6 concise, actionable pitfalls specific to its domain
+
+### Changed
+
+- Plugin version bumped to 0.8.0
+- Plugin description updated to reflect 30 skills
+- All documentation updated: README, CLAUDE.md, CONTRIBUTING.md, ROADMAP.md
+
 ## [0.7.0] - 2026-03-28
 
 ### Added
@@ -136,6 +149,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **steam-deck-compat** rule: flags common Steam Deck compatibility issues (hardcoded resolutions, mouse-only input, anti-cheat, Windows-only paths, missing controller support)
 - Plugin manifest, README, CONTRIBUTING guide, and license
 
+[0.8.0]: https://github.com/TMHSDigital/Steam-Cursor-Plugin/releases/tag/v0.8.0
 [0.7.0]: https://github.com/TMHSDigital/Steam-Cursor-Plugin/releases/tag/v0.7.0
 [0.6.0]: https://github.com/TMHSDigital/Steam-Cursor-Plugin/releases/tag/v0.6.0
 [0.5.0]: https://github.com/TMHSDigital/Steam-Cursor-Plugin/releases/tag/v0.5.0

CLAUDE.md

@@ -4,11 +4,11 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-**Steam Developer Tools** is a Cursor IDE plugin (v0.7.0) that integrates Steam and Steamworks APIs for game developers and power users. It provides AI-assisted workflows for querying Steam store data, managing Steamworks configurations, building multiplayer networking, implementing cloud saves, leaderboards, input, inventory/economy, social features, looking up API docs, fetching player statistics, integrating Workshop UGC, designing achievements, looking up player profiles, comparing games, analyzing reviews, researching pricing, evaluating market fit, estimating wishlists, automating builds, validating release readiness, scripting steamcmd, managing communities, optimizing store pages, planning pricing strategy, configuring DLC, setting up playtests, creating bug report workflows, integrating anti-cheat, and providing a testing sandbox.
+**Steam Developer Tools** is a Cursor IDE plugin (v0.8.0) that integrates Steam and Steamworks APIs for game developers and power users. It provides AI-assisted workflows for querying Steam store data, managing Steamworks configurations, building multiplayer networking, implementing cloud saves, leaderboards, input, inventory/economy, social features, looking up API docs, fetching player statistics, integrating Workshop UGC, designing achievements, looking up player profiles, comparing games, analyzing reviews, researching pricing, evaluating market fit, estimating wishlists, automating builds, validating release readiness, scripting steamcmd, managing communities, optimizing store pages, planning pricing strategy, configuring DLC, setting up playtests, creating bug report workflows, integrating anti-cheat, providing a testing sandbox, and guiding platform migration.
 
 This plugin uses Markdown skill files and MDC rule files for AI guidance, paired with the companion [Steam MCP Server](https://github.com/TMHSDigital/steam-mcp) (separate repo) which provides 16 API tools (10 read-only + 6 write/guidance) for live data access. No build system, no npm, no compiled code in this repo.
 
-The project is on a themed release roadmap toward v1.0.0 (see `ROADMAP.md`). The next major milestone (v0.8.0 "Polish") adds refinement and gap-filling. Target at v1.0.0: 30 skills, 9 rules, 20 MCP tools.
+The project is on a themed release roadmap toward v1.0.0 (see `ROADMAP.md`). The next milestone is v1.0.0 "Stable" — the production release. Target at v1.0.0: 30 skills, 9 rules, 20 MCP tools.
 
 ## Plugin Architecture
 
@@ -18,7 +18,7 @@ skills/<skill-name>/SKILL.md - AI workflow definitions (one per skill)
 rules/<rule-name>.mdc        - Code quality and security rules (applied by Cursor AI)
 ```
 
-### Skills (29 total)
+### Skills (30 total)
 
 Each `SKILL.md` uses YAML frontmatter followed by markdown sections: **Trigger**, **Required Inputs**, **Workflow**, and **Example**.
 
@@ -53,6 +53,7 @@ Each `SKILL.md` uses YAML frontmatter followed by markdown sections: **Trigger**
 | `steam-bug-report-template` | Bug report templates, crash dumps, system info, known issues |
 | `steam-anticheat-integration` | EAC, BattlEye, VAC setup, Proton/Deck compatibility |
 | `steam-testing-sandbox` | App ID 480 sandbox, test accounts, console commands, dev workflow |
+| `steam-migration-guide` | Platform migration (Epic/GOG/itch.io to Steam), engine SDK integration |
 
 ### Rules (9 total)
 

CONTRIBUTING.md

@@ -36,12 +36,12 @@ Cursor will pick up changes to skills and rules without restarting.
 
 ## Plugin Structure
 
-The plugin currently has **29 skills** and **9 rules**.
+The plugin currently has **30 skills** and **9 rules**.
 
 ```
 .cursor-plugin/
   plugin.json          # Plugin manifest (name, version, metadata)
-skills/                # 29 skill directories
+skills/                # 30 skill directories
   <skill-name>/
     SKILL.md           # Skill definition with frontmatter + instructions
 rules/                 # 9 rule files

README.md

@@ -11,7 +11,7 @@
 <p align="center">
   <a href="https://github.com/TMHSDigital/Steam-Cursor-Plugin/actions/workflows/validate.yml"><img src="https://img.shields.io/github/actions/workflow/status/TMHSDigital/Steam-Cursor-Plugin/validate.yml?label=CI" alt="CI"></a>
   <a href="LICENSE"><img src="https://img.shields.io/badge/license-CC--BY--NC--ND--4.0-blue.svg" alt="License: CC BY-NC-ND 4.0"></a>
-  <a href="CHANGELOG.md"><img src="https://img.shields.io/badge/version-0.7.0-green.svg" alt="Version"></a>
+  <a href="CHANGELOG.md"><img src="https://img.shields.io/badge/version-0.8.0-green.svg" alt="Version"></a>
   <a href="https://github.com/TMHSDigital/Steam-Cursor-Plugin/stargazers"><img src="https://img.shields.io/github/stars/TMHSDigital/Steam-Cursor-Plugin?style=flat" alt="GitHub Stars"></a>
   <a href="https://github.com/TMHSDigital/Steam-Cursor-Plugin/commits/main"><img src="https://img.shields.io/github/last-commit/TMHSDigital/Steam-Cursor-Plugin" alt="Last Commit"></a>
   <a href="https://github.com/TMHSDigital/Steam-Cursor-Plugin"><img src="https://img.shields.io/badge/Cursor-Plugin-8B5CF6.svg" alt="Cursor Plugin"></a>
@@ -22,7 +22,7 @@
 ---
 
 <p align="center">
-  <strong>29 skills</strong> &nbsp;&bull;&nbsp; <strong>9 rules</strong> &nbsp;&bull;&nbsp; <strong>16 MCP tools</strong>
+  <strong>30 skills</strong> &nbsp;&bull;&nbsp; <strong>9 rules</strong> &nbsp;&bull;&nbsp; <strong>16 MCP tools</strong>
 </p>
 
 Query Steam store data, manage Steamworks app configurations, build multiplayer networking, implement cloud saves, design achievements, compare games, and look up player profiles - all from within Cursor's AI chat. Covers the full Steam &amp; Steamworks ecosystem with live data via the companion [Steam MCP Server](https://github.com/TMHSDigital/steam-mcp).
@@ -79,6 +79,7 @@ flowchart LR
 | **Steam Bug Report Template** | Structured bug report templates with Steam system info, crash dump guidance, known issues tracking, and forum integration. |
 | **Steam Anti-Cheat Integration** | Anti-cheat setup: EAC, BattlEye, VAC with Proton/Linux/Steam Deck compatibility matrix and server-side validation. |
 | **Steam Testing Sandbox** | Dev sandbox guide: App ID 480 (SpaceWar), test accounts, Steam console commands, testing achievements/leaderboards/inventory. |
+| **Steam Migration Guide** | Migrate games to Steam from Epic/GOG/itch.io. Engine-specific SDK integration (Unity, Unreal, Godot), feature parity mapping, store page strategy. |
 
 ### Rules
 
@@ -186,7 +187,7 @@ Compare Hades, Dead Cells, and Hollow Knight - price, reviews, and current playe
 ```
 
 <details>
-<summary><strong>More examples (all 29 skills)</strong></summary>
+<summary><strong>More examples (all 30 skills)</strong></summary>
 
 **Store Lookup**
 ```
@@ -333,6 +334,11 @@ I'm making a competitive FPS. I need anti-cheat that works on Steam Deck. What s
 I want to test Steam achievements in my game but I don't have an App ID yet. How do I get started?
 ```
 
+**Migration Guide**
+```
+I have a game on itch.io built with Godot. I want to bring it to Steam with achievements and cloud saves.
+```
+
 </details>
 
 ## Configuration
@@ -388,8 +394,8 @@ See [ROADMAP.md](ROADMAP.md) for the full themed release plan toward v1.0.0.
 | **v0.4.0** | Ship It | CI/CD automation, release checklist, steamcmd helper, build validation rules | Done |
 | **v0.5.0** | Grow | Community management, store page optimization, pricing strategy, DLC planning | Done |
 | **v0.6.0** | Quality | Playtest setup, bug reporting, anti-cheat, save compat / network security / error handling rules | Done |
-| **v0.7.0** | Full Power | Testing sandbox, 6 MCP write tools (lobbies, workshop, achievements, leaderboards, inventory) | **Current** |
-| v0.8.0 | Polish | Cross-references, troubleshooting sections, migration guide | Planned |
+| **v0.7.0** | Full Power | Testing sandbox, 6 MCP write tools (lobbies, workshop, achievements, leaderboards, inventory) | Done |
+| **v0.8.0** | Polish | Migration guide, common pitfalls across all 30 skills | **Current** |
 | v1.0.0 | Stable | Production release: 30 skills, 9 rules, 20 MCP tools | Planned |
 
 ## Contributing

ROADMAP.md

@@ -2,7 +2,7 @@
 
 Themed release plan toward v1.0.0.
 
-**Current:** v0.7.0 - 29 skills, 9 rules, companion [Steam MCP server](https://github.com/TMHSDigital/steam-mcp) with 16 tools (10 read-only + 6 write/guidance).
+**Current:** v0.8.0 - 30 skills, 9 rules, companion [Steam MCP server](https://github.com/TMHSDigital/steam-mcp) with 16 tools (10 read-only + 6 write/guidance).
 
 **Target:** v1.0.0 - 30 skills, 9 rules, 20 MCP tools.
 
@@ -14,8 +14,8 @@ Themed release plan toward v1.0.0.
 | v0.4.0 | Ship It | 3 | 2 | 0 | 21 | 6 |
 | v0.5.0 | Grow | 4 | 0 | 2 | 25 | 6 |
 | v0.6.0 | Quality | 3 | 3 | 0 | 28 | 9 |
-| v0.7.0 (current) | Full Power | 1 | 0 | 6 | 29 | 9 |
-| v0.8.0 | Polish | 1 | 0 | 0 | 30 | 9 |
+| v0.7.0 | Full Power | 1 | 0 | 6 | 29 | 9 |
+| v0.8.0 (current) | Polish | 1 | 0 | 0 | 30 | 9 |
 | v1.0.0 | Stable | 0 | 0 | 0 | 30 | 9 |
 
 ---
@@ -236,3 +236,5 @@ Update all 14 existing skills to reference MCP tools where applicable. Replace "
 - [x] ~~Testing sandbox skill~~ - `steam-testing-sandbox` added in v0.7.0
 - [x] ~~MCP write tools~~ - 6 write/guidance tools added to steam-mcp in v0.7.0 (createLobby, uploadWorkshopItem, updateWorkshopItem, setAchievement, uploadLeaderboardScore, grantInventoryItem)
 - [x] ~~App ID validation MCP enhancement~~ - `steam-appid-validation.mdc` updated with live validation via MCP in v0.7.0
+- [x] ~~Migration guide skill~~ - `steam-migration-guide` added in v0.8.0
+- [x] ~~Common Pitfalls sections~~ - added to all 30 skills in v0.8.0

skills/steam-achievement-designer/SKILL.md

@@ -172,6 +172,14 @@ This is useful for reviewing an existing game's achievement distribution before
 
 The design guidance, VDF/JSON generation, naming conventions, icon requirements, and SDK unlock code remain the same regardless of MCP availability.
 
+## Common Pitfalls
+
+1. **Forgetting `StoreStats()` after `SetAchievement()`** — achievements are only saved locally until you call `SteamUserStats()->StoreStats()`. Without it, progress is lost on restart.
+2. **Using spaces or special characters in API names** — achievement API names must be alphanumeric with underscores (e.g. `ACH_BEAT_BOSS_1`). Spaces cause silent failures.
+3. **Exceeding the 1000 achievement limit** — Steam enforces a hard cap of ~5000 stat/achievement entries per app. Plan achievement lists before implementation.
+4. **Not calling `RequestCurrentStats()` at startup** — the stats system won't work until you request the current user's stats. Must be called once before any `Get`/`Set` operations.
+5. **Unlocking achievements in offline mode without testing** — achievements queued offline are sent when the user reconnects, but only if `StoreStats()` was called. Test this flow.
+
 ## See Also
 
 - [Steam Player Stats](../steam-player-stats/SKILL.md) - query achievement unlock rates to inform achievement design

skills/steam-anticheat-integration/SKILL.md

@@ -205,6 +205,14 @@ if (playerSpeed > MAX_ALLOWED_SPEED) {
 
 Anti-cheat configuration requires the Steamworks Partner site and anti-cheat vendor portals — not available via MCP.
 
+## Common Pitfalls
+
+1. **Not enabling Proton/Wine support for EAC or BattlEye** — Linux and Steam Deck players are blocked unless you explicitly opt in via the anti-cheat vendor portal. This is a separate checkbox from Steamworks Deck compatibility.
+2. **Shipping EAC without the correct redistributable files** — the EAC service installer and `EasyAntiCheat` folder must be bundled with your build. Missing files cause immediate crashes.
+3. **Trusting VAC alone for competitive games** — VAC is reactive (ban waves), not preventive. For real-time protection, pair it with EAC or BattlEye.
+4. **Forgetting to test anti-cheat in dev builds** — anti-cheat services often behave differently in debug vs release. Always test with the release configuration before shipping.
+5. **Breaking modding support unintentionally** — EAC and BattlEye block DLL injection, which some mods rely on. If your game supports mods, configure allowlists or provide a "modded" launch option without anti-cheat.
+
 ## See Also
 
 - [Steam Multiplayer Networking](../steam-multiplayer-networking/SKILL.md) - networking setup that anti-cheat protects

skills/steam-api-reference/SKILL.md

@@ -127,6 +127,13 @@ When an MCP tool exists for a given endpoint, prefer it over raw `curl` calls. F
 
 The Steamworks SDK documentation and example generation logic remain the same regardless of MCP availability.
 
+## Common Pitfalls
+
+1. **Confusing Web API and Steamworks SDK endpoints** — the Web API (HTTP) and SDK (in-process C++) have overlapping functionality but different auth models. Web API uses API keys; SDK uses the logged-in Steam user.
+2. **Using the public API base for partner endpoints** — `api.steampowered.com` vs `partner.steam-api.com`. Partner endpoints require IP allowlisting and won't work from the public base.
+3. **Not checking API rate limits** — Steam rate-limits most endpoints to ~100K calls/day per key. Exceeding this results in HTTP 429 errors with no warning.
+4. **Ignoring the `format` parameter** — some older endpoints default to VDF output instead of JSON. Always pass `format=json` for programmatic consumption.
+
 ## See Also
 
 - [Steam Store Lookup](../steam-store-lookup/SKILL.md) - look up game store data using the APIs documented here

skills/steam-bug-report-template/SKILL.md

@@ -239,6 +239,13 @@ For developers using external trackers:
 
 Bug reporting setup requires the Steamworks Partner site — not available via MCP.
 
+## Common Pitfalls
+
+1. **Not including `steam://sysinfo` in the template** — this URL dumps the user's full system info (hardware, drivers, running processes) into a copyable format. Far more reliable than asking users to self-report specs.
+2. **Ignoring minidump files** — players often don't know where crash dumps are. Include the default paths (`%LOCALAPPDATA%\CrashDumps` on Windows, `~/.steam/` on Linux) in your template.
+3. **Not separating bug reports from feature requests** — mixing them in one template leads to triage chaos. Use separate templates or tags.
+4. **Asking for too many fields** — long forms reduce submission rates. Keep required fields to ~5 and make the rest optional.
+
 ## See Also
 
 - [Steam Community Management](../steam-community-management/SKILL.md) - forum setup and community engagement