refactor: rename plugin pcm to db-editor

.agents/plugins/marketplace.json

@@ -5,13 +5,13 @@
   },
   "plugins": [
     {
-      "name": "pcm",
+      "name": "db-editor",
       "interface": {
-        "displayName": "Pro Cycling Manager"
+        "displayName": "DB Editor"
       },
       "source": {
         "source": "local",
-        "path": "./plugins/pcm"
+        "path": "./plugins/db-editor"
       },
       "policy": {
         "installation": "AVAILABLE",

.claude-plugin/marketplace.json

@@ -8,10 +8,10 @@
   },
   "plugins": [
     {
-      "name": "pcm",
+      "name": "db-editor",
       "description": "Explore and edit Pro Cycling Manager game databases (.cdb) — rider ratings, team rosters, contracts, races — and build race startlists exported as the .xml file the game imports. Unofficial, not affiliated with Cyanide Studio or Nacon.",
       "category": "Developer Tools",
-      "source": "./plugins/pcm"
+      "source": "./plugins/db-editor"
     }
   ]
 }

AGENTS.md

@@ -26,7 +26,7 @@ Key formats and technologies:
 .claude-plugin/marketplace.json   # Claude Code marketplace definition
 .agents/plugins/marketplace.json  # Codex/agents marketplace definition
 plugins/
-  pcm/
+  db-editor/
     .claude-plugin/plugin.json    # Claude Code plugin manifest
     .codex-plugin/plugin.json     # Codex plugin manifest (adds `interface` block)
     .mcp.json                     # MCP servers bundled with the plugin (pcm-mcp)
@@ -43,7 +43,7 @@ README.md                         # human-facing overview + quickstart; detailed
 ```
 
 Skills live **inside a plugin** (`plugins/{plugin}/skills/{skill}/`), not at the repo root.
-The only plugin is `pcm`, containing `pcm-database` and `pcm-startlist`.
+The only plugin is `db-editor`, containing `pcm-database` and `pcm-startlist`.
 
 ## Setup Commands
 
@@ -65,13 +65,13 @@ Install the marketplace locally in Claude Code to test plugin changes:
 
 ```
 /plugin marketplace add /Users/<you>/Dev/agent-skills
-/plugin install pcm@pcmstack
+/plugin install db-editor@pcmstack
 ```
 
 Then exercise the skill with realistic prompts (e.g. "who's the best climber in my team?",
 "build the startlist for the Tour de France") and check that it triggers _and_ that the
 instructions hold up. The `defaultPrompt` array in
-[plugins/pcm/.codex-plugin/plugin.json](plugins/pcm/.codex-plugin/plugin.json) is a good
+[plugins/db-editor/.codex-plugin/plugin.json](plugins/db-editor/.codex-plugin/plugin.json) is a good
 source of test prompts.
 
 Prefer the `/skill-creator:skill-creator` skill (if available in your agent environment,
@@ -84,7 +84,7 @@ Then apply the repository conventions below to the result.
 There is no automated test suite. "Testing" here means validation plus behavioural checks:
 
 ```bash
-bash -n plugins/pcm/skills/pcm-database/scripts/open-cdb.sh   # syntax-check scripts
+bash -n plugins/db-editor/skills/pcm-database/scripts/open-cdb.sh   # syntax-check scripts
 python3 -m json.tool <file>.json > /dev/null                  # validate each JSON manifest
 npx prettier --check "**/*.{md,json}"                         # formatting
 ```
@@ -106,7 +106,7 @@ Behavioural checks that matter more than the above:
 
 ### Naming Conventions
 
-- **Plugin directory**: `kebab-case` (e.g. `pcm`), matching `name` in both plugin manifests.
+- **Plugin directory**: `kebab-case` (e.g. `db-editor`), matching `name` in both plugin manifests.
 - **Skill directory**: `kebab-case` (e.g. `pcm-database`), matching `name` in its frontmatter.
 - **SKILL.md**: always uppercase, always this exact filename.
 - **Scripts**: `kebab-case.sh` or `kebab-case.mjs` (e.g. `open-cdb.sh`).
@@ -155,7 +155,7 @@ Consequences worth remembering:
 - Adding a new plugin means a new `plugins/{name}/` directory **plus** entries in both
   `.claude-plugin/marketplace.json` and `.agents/plugins/marketplace.json`.
 - Plugin assets are resolved relative to the plugin directory, which is why `assets/` lives
-  under `plugins/pcm/` rather than at the repo root.
+  under `plugins/db-editor/` rather than at the repo root.
 
 ## Pull Request Guidelines
 

README.md

@@ -1,5 +1,5 @@
 <div align="center">
-  <img src="plugins/pcm/assets/logo.svg" alt="PCMStack" width="96">
+  <img src="plugins/db-editor/assets/logo.svg" alt="PCMStack" width="96">
 
 # PCMStack Agent Skills
 
@@ -28,11 +28,11 @@ You  ▸ Build the startlist for Almería — 20 teams, sprinters up front
 
 ## Install
 
-The repository is a marketplace containing a single plugin, `pcm`. In **Claude Code**:
+The repository is a marketplace containing a single plugin, `db-editor`. In **Claude Code**:
 
 ```
 /plugin marketplace add PCMStack/agent-skills
-/plugin install pcm@pcmstack
+/plugin install db-editor@pcmstack
 ```
 
 Then just ask. Skills trigger on their own when a request matches — no command to remember.
@@ -41,15 +41,15 @@ Then just ask. Skills trigger on their own when a request matches — no command
 <summary>Other agents</summary>
 
 The skills follow the portable `SKILL.md` format, so any agent that reads Agent Skills can
-use them. Point your agent at `plugins/pcm/skills/`, or clone the repository and add it as a
+use them. Point your agent at `plugins/db-editor/skills/`, or clone the repository and add it as a
 local marketplace:
 
 ```
 /plugin marketplace add /path/to/agent-skills
 ```
 
 Codex-compatible manifests live in `.agents/plugins/marketplace.json` and
-`plugins/pcm/.codex-plugin/plugin.json`.
+`plugins/db-editor/.codex-plugin/plugin.json`.
 
 </details>
 
@@ -111,7 +111,7 @@ manifests, read by another agent at runtime.
 ```
 .claude-plugin/marketplace.json    # Claude Code marketplace
 .agents/plugins/marketplace.json   # Codex/agents marketplace
-plugins/pcm/
+plugins/db-editor/
   .claude-plugin/plugin.json       # plugin manifest
   .codex-plugin/plugin.json        # plugin manifest (Codex, adds `interface`)
   .mcp.json                        # bundled MCP servers
@@ -130,7 +130,7 @@ realistic prompts and check they trigger on paraphrases — a description that m
 Validation before opening a PR:
 
 ```bash
-bash -n plugins/pcm/skills/pcm-database/scripts/open-cdb.sh   # syntax-check scripts
+bash -n plugins/db-editor/skills/pcm-database/scripts/open-cdb.sh   # syntax-check scripts
 python3 -m json.tool <file>.json > /dev/null                  # validate manifests
 npx prettier --check "**/*.{md,json}"                         # formatting
 ```

plugins/pcm/.claude-plugin/plugin.json → plugins/db-editor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
-  "name": "pcm",
-  "displayName": "Pro Cycling Manager",
+  "name": "db-editor",
+  "displayName": "DB Editor",
   "version": "0.1.0",
   "description": "Explore and edit Pro Cycling Manager game databases (.cdb) — rider ratings, team rosters, contracts, races — and build race startlists exported as the .xml file the game imports. Unofficial, not affiliated with Cyanide Studio or Nacon.",
   "author": {

plugins/pcm/.codex-plugin/plugin.json → plugins/db-editor/.codex-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
-  "name": "pcm",
+  "name": "db-editor",
   "version": "0.1.0",
   "description": "Explore and edit Pro Cycling Manager game databases (.cdb) — rider ratings, team rosters, contracts, races — and build race startlists exported as the .xml file the game imports. Unofficial, not affiliated with Cyanide Studio or Nacon.",
   "author": {
@@ -22,7 +22,7 @@
   "skills": "./skills/",
   "mcpServers": "./.mcp.json",
   "interface": {
-    "displayName": "CDB Editor",
+    "displayName": "DB Editor",
     "shortDescription": "Edit Pro Cycling Manager databases and build race startlists",
     "longDescription": "Community tooling for Pro Cycling Manager. Open and edit the game database (.cdb) — rider ratings, team rosters, contracts, races — via the pcm-mcp MCP server or a lossless CDB to SQLite conversion, and compose race startlists exported as the .xml file the game imports. Unofficial project, not affiliated with or endorsed by Cyanide Studio or Nacon.",
     "developerName": "PCMStack",