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.3.0",
5
-
"description": "Integrates Steam and Steamworks APIs for game developers and power users. 18 skills covering store data, multiplayer networking, cloud saves, leaderboards, input, inventory, social features, profile lookups, game comparisons, review analysis, price history, market research, and wishlist estimates- plus 4 rules for App ID validation, secrets detection, Steam Deck compatibility, and MCP tool preference. Companion Steam MCP server provides 10 live API tools.",
4
+
"version": "0.4.0",
5
+
"description": "Integrates Steam and Steamworks APIs for game developers and power users. 21 skills covering store data, multiplayer networking, cloud saves, leaderboards, input, inventory, social features, profile lookups, game comparisons, review analysis, price history, market research, wishlist estimates, build automation, release checklists, and steamcmd scripting - plus 6 rules for App ID validation, secrets detection, Steam Deck compatibility, MCP tool preference, build config validation, and launch options checking. Companion Steam MCP server provides 10 live API tools.",
-**steam-launch-options-check** rule: flags launch option issues including missing executables, wrong OS targeting, missing descriptions for multi-launch configs, and invalid type values
17
+
18
+
### Changed
19
+
20
+
- Plugin version bumped to 0.4.0
21
+
- Plugin description updated to reflect 21 skills and 6 rules
22
+
- All documentation updated: README, CLAUDE.md, CONTRIBUTING.md, ROADMAP.md
23
+
8
24
## [0.3.0] - 2026-03-27
9
25
10
26
### Added
@@ -63,6 +79,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
Copy file name to clipboardExpand all lines: CLAUDE.md
+9-4Lines changed: 9 additions & 4 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.3.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, and estimating wishlists.
7
+
**Steam Developer Tools** is a Cursor IDE plugin (v0.4.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, and scripting steamcmd.
8
8
9
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.
10
10
11
-
The project is on a themed release roadmap toward v1.0.0 (see `ROADMAP.md`). The next major milestone (v0.4.0 "Ship It") adds CI/CD automation and build pipeline skills. Subsequent releases add community/monetization skills (v0.5.0), QA rules (v0.6.0), MCP write operations (v0.7.0), and 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.5.0 "Grow") adds community management and monetization skills. Subsequent releases add QA rules (v0.6.0), MCP write operations (v0.7.0), and polish (v0.8.0). 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 (18 total)
21
+
### Skills (21 total)
22
22
23
23
Each `SKILL.md` uses YAML frontmatter followed by markdown sections: **Trigger**, **Required Inputs**, **Workflow**, and **Example**.
24
24
@@ -42,15 +42,20 @@ Each `SKILL.md` uses YAML frontmatter followed by markdown sections: **Trigger**
42
42
|`steam-price-history`| Pricing trends, sale history, regional pricing, value scoring |
43
43
|`steam-market-research`| Genre trends, tag popularity, competitor ID, market gap analysis |
44
44
|`steam-wishlist-estimates`| Estimate wishlists from public signals, conversion benchmarks |
|`steam-appid-validation.mdc`|`steam_appid.txt`, `*.vdf`, steamcmd configs | Enforces App ID consistency; warns if `480` (SpaceWar test) is used in production |
51
54
|`steamworks-secrets.mdc`| Global (all files) | Flags Steam API keys (32-char hex), ssfn files, publisher credentials, DRM keys |
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).
@@ -68,6 +68,9 @@ flowchart LR
68
68
|**Steam Price History**| Pricing trends, sale history, regional pricing analysis, and price-to-value scoring for any Steam game. |
69
69
|**Steam Market Research**| Genre trend analysis, tag popularity, competitor identification, and market gap analysis using Steam store data. |
70
70
|**Steam Wishlist Estimates**| Estimate wishlists from public signals using the Boxleiter method, with conversion rate benchmarks and revenue projections. |
|**Steamworks Secrets**| Prevents committing API keys, partner credentials, and auth tokens. Flags sensitive patterns and suggests secure alternatives. |
78
81
|**Steam Deck Compatibility**| Flags common Deck compat issues in game code: hardcoded resolutions, mouse-only input, anti-cheat blockers, Windows-only paths, and missing controller support. |
79
82
|**MCP Tool Preference**| When the Steam MCP server is configured, flags raw `curl`/`fetch` calls to Steam APIs and suggests the equivalent MCP tool. |
description: Validate Steam build configuration files (VDF). Checks for missing depots, mismatched App IDs between app_build and depot_build files, invalid file mappings, empty content roots, and common SteamPipe configuration errors.
3
+
alwaysApply: false
4
+
globs:
5
+
- "**/*.vdf"
6
+
- "**/app_build*"
7
+
- "**/depot_build*"
8
+
---
9
+
10
+
# Steam Build Config Validation
11
+
12
+
When editing or reviewing VDF build configuration files, check for these issues:
13
+
14
+
## App Build Files (`app_build.vdf`)
15
+
16
+
1. **Missing `appid` field.** Every `app_build.vdf` must have a valid `appid`. Flag if the value is empty, `0`, or missing entirely.
17
+
18
+
2. **SpaceWar test ID in production.** If `appid` is `480` and the file appears to be a production config (not a test/example), warn: "App ID 480 is Valve's SpaceWar test app. Replace with your actual App ID before uploading."
19
+
20
+
3. **Empty `contentroot`.** The `contentroot` path must point to a valid directory containing build artifacts. Flag if empty or set to a placeholder like `TODO` or `CHANGEME`.
21
+
22
+
4. **Missing depot entries.** The `depots` block must reference at least one depot. Flag if the `depots` block is empty or missing.
23
+
24
+
5. **Depot ID mismatch.** Each depot referenced in `app_build.vdf` should have a corresponding `depot_build_*.vdf` file. Flag depot IDs that reference non-existent VDF files.
25
+
26
+
## Depot Build Files (`depot_build_*.vdf`)
27
+
28
+
6. **Missing `DepotID` field.** Every depot build file must have a `DepotID`. Flag if missing or `0`.
29
+
30
+
7. **Depot ID consistency.** The `DepotID` in `depot_build_XXXXX.vdf` should match the `XXXXX` in the filename. Flag mismatches.
31
+
32
+
8. **Missing `FileMapping`.** At least one `FileMapping` block is required. Flag depot configs with no file mappings — they would upload an empty depot.
33
+
34
+
9. **Invalid `FileMapping` patterns.** Flag `LocalPath` values that use absolute paths (should be relative to `contentroot`) or that reference suspicious patterns like `*.*` (usually should be `*`).
35
+
36
+
10. **Depot ID relationship.** Depot IDs should typically be `appid + N` (e.g., App ID `1234567` → depots `1234568`, `1234569`). Flag depot IDs that are wildly different from the app ID, as this may indicate a copy-paste error.
37
+
38
+
## Cross-File Consistency
39
+
40
+
11. **App ID vs depot ID sanity.** All depot IDs referenced in `app_build.vdf` should be in a reasonable range relative to the `appid` (typically `appid + 1` through `appid + 10`).
41
+
42
+
12. **`setlive` safety.** If `setlive` is set to `default`, warn: "This build will go live to all users immediately on upload. Consider using a beta branch name for testing first."
43
+
44
+
13. **`preview` mode.** If `preview` is `1`, note that the build will not actually upload — this is a dry run. Useful for validation but should be `0` for real uploads.
0 commit comments