You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .cursor-plugin/plugin.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
{
2
2
"name": "steam-cursor-plugin",
3
3
"displayName": "Steam Developer Tools",
4
-
"version": "0.6.0",
5
-
"description": "Integrates Steam and Steamworks APIs for game developers and power users. 28 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, and anti-cheat- plus 9 rules. Companion Steam MCP server provides 10 live API tools.",
4
+
"version": "0.7.0",
5
+
"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.",
Copy file name to clipboardExpand all lines: CHANGELOG.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,26 @@ All notable changes to Steam Developer Tools will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
8
+
## [0.7.0] - 2026-03-28
9
+
10
+
### Added
11
+
12
+
-**steam-testing-sandbox** skill: development sandbox guide — App ID 480 (SpaceWar) usage, test account setup, Steam client console commands, partner test environments, and dev-to-production checklist
13
+
-**6 new MCP write tools** in companion Steam MCP server (v0.3.0):
14
+
-`steam.createLobby` — SDK guidance for ISteamMatchmaking lobby creation (C++/C#/GDScript)
15
+
-`steam.uploadWorkshopItem` — SDK guidance for ISteamUGC Workshop uploads (C++/GDScript)
16
+
-`steam.updateWorkshopItem` — HTTP POST to update Workshop item metadata via partner API
17
+
-`steam.setAchievement` — HTTP POST to set/unlock achievements via partner API (dev/test)
18
+
-`steam.uploadLeaderboardScore` — HTTP POST to upload scores via partner API
19
+
-`steam.grantInventoryItem` — HTTP POST to grant inventory items via partner API
20
+
21
+
### Changed
22
+
23
+
-`steam-appid-validation` rule enhanced with MCP live validation — suggests `steam.getAppDetails()` to verify App IDs exist
24
+
- Plugin version bumped to 0.7.0
25
+
- Plugin description updated to reflect 29 skills and 16 MCP tools
26
+
- All documentation updated: README, CLAUDE.md, CONTRIBUTING.md, ROADMAP.md
27
+
8
28
## [0.6.0] - 2026-03-28
9
29
10
30
### Added
@@ -116,6 +136,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
Copy file name to clipboardExpand all lines: CLAUDE.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,11 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
4
4
5
5
## Project Overview
6
6
7
-
**Steam Developer Tools** is a Cursor IDE plugin (v0.6.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, and integrating anti-cheat.
7
+
**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.
8
8
9
-
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 10 read-only API tools for live data access. No build system, no npm, no compiled code in this repo.
9
+
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.
10
10
11
-
The project is on a themed release roadmap toward v1.0.0 (see `ROADMAP.md`). The next major milestone (v0.7.0 "Full Power") adds MCP write operations. Subsequent releases add polish (v0.8.0). Target at v1.0.0: 30 skills, 9 rules, 20 MCP tools.
11
+
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.
12
12
13
13
## Plugin Architecture
14
14
@@ -18,7 +18,7 @@ skills/<skill-name>/SKILL.md - AI workflow definitions (one per skill)
18
18
rules/<rule-name>.mdc - Code quality and security rules (applied by Cursor AI)
19
19
```
20
20
21
-
### Skills (28 total)
21
+
### Skills (29 total)
22
22
23
23
Each `SKILL.md` uses YAML frontmatter followed by markdown sections: **Trigger**, **Required Inputs**, **Workflow**, and **Example**.
24
24
@@ -52,6 +52,7 @@ Each `SKILL.md` uses YAML frontmatter followed by markdown sections: **Trigger**
52
52
|`steam-playtest-setup`| Steam Playtest config, open/closed playtests, key distribution |
53
53
|`steam-bug-report-template`| Bug report templates, crash dumps, system info, known issues |
|`steam-testing-sandbox`| App ID 480 sandbox, test accounts, console commands, dev workflow |
55
56
56
57
### Rules (9 total)
57
58
@@ -69,7 +70,7 @@ Each `SKILL.md` uses YAML frontmatter followed by markdown sections: **Trigger**
69
70
70
71
### Companion MCP Server
71
72
72
-
The [Steam MCP Server](https://github.com/TMHSDigital/steam-mcp) provides 10 read-only tools. Skills reference these tools in their `## MCP Usage` sections. When the MCP server is configured in Cursor, skills prefer MCP tool calls over shell `curl` commands.
73
+
The [Steam MCP Server](https://github.com/TMHSDigital/steam-mcp) provides 16 tools (10 read-only + 6 write/guidance). Skills reference these tools in their `## MCP Usage` sections. When the MCP server is configured in Cursor, skills prefer MCP tool calls over shell `curl` commands.
73
74
74
75
| MCP Tool | Auth | Maps to |
75
76
|----------|------|---------|
@@ -83,6 +84,12 @@ The [Steam MCP Server](https://github.com/TMHSDigital/steam-mcp) provides 10 rea
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 & Steamworks ecosystem with live data via the companion [Steam MCP Server](https://github.com/TMHSDigital/steam-mcp).
@@ -78,6 +78,7 @@ flowchart LR
78
78
|**Steam Playtest Setup**| Configure Steam Playtest: open vs closed playtests, key distribution, signup pages, feedback collection, and Next Fest integration. |
79
79
|**Steam Bug Report Template**| Structured bug report templates with Steam system info, crash dump guidance, known issues tracking, and forum integration. |
80
80
|**Steam Anti-Cheat Integration**| Anti-cheat setup: EAC, BattlEye, VAC with Proton/Linux/Steam Deck compatibility matrix and server-side validation. |
81
+
|**Steam Testing Sandbox**| Dev sandbox guide: App ID 480 (SpaceWar), test accounts, Steam console commands, testing achievements/leaderboards/inventory. |
81
82
82
83
### Rules
83
84
@@ -131,6 +132,12 @@ The `STEAM_API_KEY` is only required for tools that access user-specific data (p
Copy file name to clipboardExpand all lines: rules/steam-appid-validation.mdc
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -29,3 +29,5 @@ When editing or reviewing files that reference a Steam App ID:
29
29
- Is `0` or negative
30
30
31
31
4. **Depot ID relationships.** In VDF build configs, depot IDs should typically be `appid + N` (e.g., App ID `1234567`, depots `1234568`, `1234569`). Flag depot IDs that seem unrelated to the App ID.
32
+
33
+
5. **Live validation via MCP.** When the [Steam MCP server](https://github.com/TMHSDigital/steam-mcp) is available, suggest verifying that the App ID exists in the Steam store by calling `steam.getAppDetails({ appid })`. If the API returns no data or `success: false`, the App ID may be invalid, region-locked, or not yet published. This provides a stronger check than static file analysis alone.
0 commit comments