{"owner":"yugabyte","repo":"yugabyte-db","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":2243,"categories":["root-instruction","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"yugabyte-db":{"command":"npx","args":["-y","@modelcontextprotocol/server-yugabyte-db"]}}},"found":["AGENTS.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"AGENTS.md":"# AGENTS.md\n\nThis document provides a guide for agents working on YugabyteDB\n\n### Deploying and running\n\nFor agents that want to deploy, configure and run YugabyteDB refer to instructions at ./docs/content/stable/quick-start\n\n### Repo Structure\n\n| Directory | What it contains |\n|---|---|\n| `src/` | Core database code: PostgreSQL fork (`src/postgres/`), YugabyteDB C++ storage engine (`src/yb/`), Odyssey connection pooler (`src/odyssey/`) |\n| `java/` | Java client library, CDC connector, and DB tests |\n| `managed/` | YugabyteDB Anywhere (YBA) platform — orchestration UI, CLI, node agent, and backend (Scala/Java) |\n| `docs/` | Source files for the docs website (docs.yugabyte.com) |\n| `python/` | Python build utilities and test infrastructure scripts |\n| `build-support/` | Build system scripts, linting, and third-party dependency tooling |\n| `cmake_modules/` | CMake modules for locating dependencies and custom build functions |\n| `cloud/` | Docker, Kubernetes, and Grafana deployment configurations |\n| `yugabyted-ui/` | Yugabyted web UI (React frontend + Go API server) |\n| `architecture/` | Internal design documents and architecture specs |\n| `troubleshoot/` | Troubleshooting framework backend and UI |\n\n### Coding and Development\n\nWhen working on DB code (`src/`), refer to `src/AGENTS.md` for build and test guidance\n\n## Cursor Cloud specific instructions\n\n### Environment\n\nThe VM image is `yugabyteci/yb_build_infra_almalinux9_x86_64` which ships with: Clang, JDK 17, Go, Python 3.11, CMake, Ninja, SBT, Node.js 22, Rust, and all C++ build dependencies.\n\n### Building from source\n\n```bash\n./yb_build.sh release daemons initdb --sj --skip-pg-parquet --no-odyssey --no-ybc\n```\n\nThis is the Cloud environment `install` command. Builds snapshot `build/latest` (yb-master, yb-tserver, postgres, initdb). Agents booting from a successful Build already have those binaries; rerun only if the branch changes build inputs. Do not start yugabyted in `install`; Builds keep files, not processes.\n\nFlags: `--sj` skips Java, `--skip-pg-parquet` skips the parquet extension, `--no-odyssey` skips the connection pooler, `--no-ybc` skips the backup controller. Add targets back as needed. First compile is ~15-20 minutes on 8 vCPUs; later Builds reuse `/opt/yb-build` and incremental objects.\n\n### Running the database\n\nIf `build/latest` is present, start the cluster. Otherwise compile first.\n\n```bash\npython3 bin/yugabyted start --advertise_address 127.0.0.1 --base_dir /tmp/yb-data\n```\n\nFor a multi-node cluster, start additional nodes with `--join <first-node-address>` and a distinct `--advertise_address` and `--base_dir` each.\n\nPorts: YSQL on 5433, YCQL on 9042, yb-master UI on 7000, yb-tserver UI on 9000.\n\nConnect: `build/latest/postgres/bin/ysqlsh -U yugabyte -d yugabyte -h 127.0.0.1`\n\n### Yugabyted UI\n\n`yugabyted-ui/ui/`: `npm ci` (Node.js >= 22.18), `npm start` on port 3000, `npm run typecheck`.\n\n### Prose discipline — write for the reader, not for volume\n\nAI-written text runs long: PR and diff descriptions that narrate the diff, comments that\nrestate the line below them, design docs padded with editorial framing. It reads as\nthorough, but it costs review time, and every extra sentence is one more claim that has to\nstay true as the code moves.\n\nThere are no hard limits here. Judge each piece by what a reader who already knows this\nrepo needs:\n\n- **Code comments** — don't restate the code. Comment the *why* when it isn't obvious: an\n  invariant, a cross-component contract, a locking or ordering constraint, a workaround and\n  the upstream bug behind it. Not a label for the block below it, not narration of the\n  change you just made.\n- **PR / Phorge diff descriptions** — the motivation (a reviewer who doesn't know why is\n  the expensive case), what changed, and whatever the reader must *act* on: new gflags,\n  upgrade/rollback consequences, migration steps. Not a narration of the diff. The test\n  plan is a separate section — keep it to what was run.\n- **Design docs (`architecture/`) and agent docs (`AGENTS.md`, `.claude/skills/`)** — how\n  the system is wired today, why it's built that way, and what the reader has to do. Cut\n  restated context and the history of what the code used to do.\n- **Commit messages** — subject, plus the why when the why isn't obvious.\n\nThe test for a sentence: would a reader who knows this repo do or believe anything\ndifferently without it? If not, cut it.\n\n**Motivation is not filler** — why a design is the way it is is exactly what a reader can't\nrecover from the code; what's being cut is text that says the same thing twice, not text\nthat explains. And don't over-correct: the goal is *fewer, load-bearing* words, not\nstripped docs. Deleting a section that describes live behavior is a worse outcome than\nleaving it wordy, and this applies to your own diff, not a cleanup tour of files you didn't\ntouch.\n\nThis does **not** apply to the user-facing docs website (`docs/`), which follows its own\neditorial style guide and is written for readers who do *not* know this repo.\n\nTrim before you publish, not in review: the `create-pr` and `create-diff` skills re-check\nthis as a step.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/plugin.json)"},"files":{"AGENTS.md":"# AGENTS.md\n\nThis document provides a guide for agents working on YugabyteDB\n\n### Deploying and running\n\nFor agents that want to deploy, configure and run YugabyteDB refer to instructions at ./docs/content/stable/quick-start\n\n### Repo Structure\n\n| Directory | What it contains |\n|---|---|\n| `src/` | Core database code: PostgreSQL fork (`src/postgres/`), YugabyteDB C++ storage engine (`src/yb/`), Odyssey connection pooler (`src/odyssey/`) |\n| `java/` | Java client library, CDC connector, and DB tests |\n| `managed/` | YugabyteDB Anywhere (YBA) platform — orchestration UI, CLI, node agent, and backend (Scala/Java) |\n| `docs/` | Source files for the docs website (docs.yugabyte.com) |\n| `python/` | Python build utilities and test infrastructure scripts |\n| `build-support/` | Build system scripts, linting, and third-party dependency tooling |\n| `cmake_modules/` | CMake modules for locating dependencies and custom build functions |\n| `cloud/` | Docker, Kubernetes, and Grafana deployment configurations |\n| `yugabyted-ui/` | Yugabyted web UI (React frontend + Go API server) |\n| `architecture/` | Internal design documents and architecture specs |\n| `troubleshoot/` | Troubleshooting framework backend and UI |\n\n### Coding and Development\n\nWhen working on DB code (`src/`), refer to `src/AGENTS.md` for build and test guidance\n\n## Cursor Cloud specific instructions\n\n### Environment\n\nThe VM image is `yugabyteci/yb_build_infra_almalinux9_x86_64` which ships with: Clang, JDK 17, Go, Python 3.11, CMake, Ninja, SBT, Node.js 22, Rust, and all C++ build dependencies.\n\n### Building from source\n\n```bash\n./yb_build.sh release daemons initdb --sj --skip-pg-parquet --no-odyssey --no-ybc\n```\n\nThis is the Cloud environment `install` command. Builds snapshot `build/latest` (yb-master, yb-tserver, postgres, initdb). Agents booting from a successful Build already have those binaries; rerun only if the branch changes build inputs. Do not start yugabyted in `install`; Builds keep files, not processes.\n\nFlags: `--sj` skips Java, `--skip-pg-parquet` skips the parquet extension, `--no-odyssey` skips the connection pooler, `--no-ybc` skips the backup controller. Add targets back as needed. First compile is ~15-20 minutes on 8 vCPUs; later Builds reuse `/opt/yb-build` and incremental objects.\n\n### Running the database\n\nIf `build/latest` is present, start the cluster. Otherwise compile first.\n\n```bash\npython3 bin/yugabyted start --advertise_address 127.0.0.1 --base_dir /tmp/yb-data\n```\n\nFor a multi-node cluster, start additional nodes with `--join <first-node-address>` and a distinct `--advertise_address` and `--base_dir` each.\n\nPorts: YSQL on 5433, YCQL on 9042, yb-master UI on 7000, yb-tserver UI on 9000.\n\nConnect: `build/latest/postgres/bin/ysqlsh -U yugabyte -d yugabyte -h 127.0.0.1`\n\n### Yugabyted UI\n\n`yugabyted-ui/ui/`: `npm ci` (Node.js >= 22.18), `npm start` on port 3000, `npm run typecheck`.\n\n### Prose discipline — write for the reader, not for volume\n\nAI-written text runs long: PR and diff descriptions that narrate the diff, comments that\nrestate the line below them, design docs padded with editorial framing. It reads as\nthorough, but it costs review time, and every extra sentence is one more claim that has to\nstay true as the code moves.\n\nThere are no hard limits here. Judge each piece by what a reader who already knows this\nrepo needs:\n\n- **Code comments** — don't restate the code. Comment the *why* when it isn't obvious: an\n  invariant, a cross-component contract, a locking or ordering constraint, a workaround and\n  the upstream bug behind it. Not a label for the block below it, not narration of the\n  change you just made.\n- **PR / Phorge diff descriptions** — the motivation (a reviewer who doesn't know why is\n  the expensive case), what changed, and whatever the reader must *act* on: new gflags,\n  upgrade/rollback consequences, migration steps. Not a narration of the diff. The test\n  plan is a separate section — keep it to what was run.\n- **Design docs (`architecture/`) and agent docs (`AGENTS.md`, `.claude/skills/`)** — how\n  the system is wired today, why it's built that way, and what the reader has to do. Cut\n  restated context and the history of what the code used to do.\n- **Commit messages** — subject, plus the why when the why isn't obvious.\n\nThe test for a sentence: would a reader who knows this repo do or believe anything\ndifferently without it? If not, cut it.\n\n**Motivation is not filler** — why a design is the way it is is exactly what a reader can't\nrecover from the code; what's being cut is text that says the same thing twice, not text\nthat explains. And don't over-correct: the goal is *fewer, load-bearing* words, not\nstripped docs. Deleting a section that describes live behavior is a worse outcome than\nleaving it wordy, and this applies to your own diff, not a cleanup tour of files you didn't\ntouch.\n\nThis does **not** apply to the user-facing docs website (`docs/`), which follows its own\neditorial style guide and is written for readers who do *not* know this repo.\n\nTrim before you publish, not in review: the `create-pr` and `create-diff` skills re-check\nthis as a step.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# AGENTS.md\n\nThis document provides a guide for agents working on YugabyteDB\n\n### Deploying and running\n\nFor agents that want to deploy, configure and run YugabyteDB refer to instructions at ./docs/content/stable/quick-start\n\n### Repo Structure\n\n| Directory | What it contains |\n|---|---|\n| `src/` | Core database code: PostgreSQL fork (`src/postgres/`), YugabyteDB C++ storage engine (`src/yb/`), Odyssey connection pooler (`src/odyssey/`) |\n| `java/` | Java client library, CDC connector, and DB tests |\n| `managed/` | YugabyteDB Anywhere (YBA) platform — orchestration UI, CLI, node agent, and backend (Scala/Java) |\n| `docs/` | Source files for the docs website (docs.yugabyte.com) |\n| `python/` | Python build utilities and test infrastructure scripts |\n| `build-support/` | Build system scripts, linting, and third-party dependency tooling |\n| `cmake_modules/` | CMake modules for locating dependencies and custom build functions |\n| `cloud/` | Docker, Kubernetes, and Grafana deployment configurations |\n| `yugabyted-ui/` | Yugabyted web UI (React frontend + Go API server) |\n| `architecture/` | Internal design documents and architecture specs |\n| `troubleshoot/` | Troubleshooting framework backend and UI |\n\n### Coding and Development\n\nWhen working on DB code (`src/`), refer to `src/AGENTS.md` for build and test guidance\n\n## Cursor Cloud specific instructions\n\n### Environment\n\nThe VM image is `yugabyteci/yb_build_infra_almalinux9_x86_64` which ships with: Clang, JDK 17, Go, Python 3.11, CMake, Ninja, SBT, Node.js 22, Rust, and all C++ build dependencies.\n\n### Building from source\n\n```bash\n./yb_build.sh release daemons initdb --sj --skip-pg-parquet --no-odyssey --no-ybc\n```\n\nThis is the Cloud environment `install` command. Builds snapshot `build/latest` (yb-master, yb-tserver, postgres, initdb). Agents booting from a successful Build already have those binaries; rerun only if the branch changes build inputs. Do not start yugabyted in `install`; Builds keep files, not processes.\n\nFlags: `--sj` skips Java, `--skip-pg-parquet` skips the parquet extension, `--no-odyssey` skips the connection pooler, `--no-ybc` skips the backup controller. Add targets back as needed. First compile is ~15-20 minutes on 8 vCPUs; later Builds reuse `/opt/yb-build` and incremental objects.\n\n### Running the database\n\nIf `build/latest` is present, start the cluster. Otherwise compile first.\n\n```bash\npython3 bin/yugabyted start --advertise_address 127.0.0.1 --base_dir /tmp/yb-data\n```\n\nFor a multi-node cluster, start additional nodes with `--join <first-node-address>` and a distinct `--advertise_address` and `--base_dir` each.\n\nPorts: YSQL on 5433, YCQL on 9042, yb-master UI on 7000, yb-tserver UI on 9000.\n\nConnect: `build/latest/postgres/bin/ysqlsh -U yugabyte -d yugabyte -h 127.0.0.1`\n\n### Yugabyted UI\n\n`yugabyted-ui/ui/`: `npm ci` (Node.js >= 22.18), `npm start` on port 3000, `npm run typecheck`.\n\n### Prose discipline — write for the reader, not for volume\n\nAI-written text runs long: PR and diff descriptions that narrate the diff, comments that\nrestate the line below them, design docs padded with editorial framing. It reads as\nthorough, but it costs review time, and every extra sentence is one more claim that has to\nstay true as the code moves.\n\nThere are no hard limits here. Judge each piece by what a reader who already knows this\nrepo needs:\n\n- **Code comments** — don't restate the code. Comment the *why* when it isn't obvious: an\n  invariant, a cross-component contract, a locking or ordering constraint, a workaround and\n  the upstream bug behind it. Not a label for the block below it, not narration of the\n  change you just made.\n- **PR / Phorge diff descriptions** — the motivation (a reviewer who doesn't know why is\n  the expensive case), what changed, and whatever the reader must *act* on: new gflags,\n  upgrade/rollback consequences, migration steps. Not a narration of the diff. The test\n  plan is a separate section — keep it to what was run.\n- **Design docs (`architecture/`) and agent docs (`AGENTS.md`, `.claude/skills/`)** — how\n  the system is wired today, why it's built that way, and what the reader has to do. Cut\n  restated context and the history of what the code used to do.\n- **Commit messages** — subject, plus the why when the why isn't obvious.\n\nThe test for a sentence: would a reader who knows this repo do or believe anything\ndifferently without it? If not, cut it.\n\n**Motivation is not filler** — why a design is the way it is is exactly what a reader can't\nrecover from the code; what's being cut is text that says the same thing twice, not text\nthat explains. And don't over-correct: the goal is *fewer, load-bearing* words, not\nstripped docs. Deleting a section that describes live behavior is a worse outcome than\nleaving it wordy, and this applies to your own diff, not a cleanup tour of files you didn't\ntouch.\n\nThis does **not** apply to the user-facing docs website (`docs/`), which follows its own\neditorial style guide and is written for readers who do *not* know this repo.\n\nTrim before you publish, not in review: the `create-pr` and `create-diff` skills re-check\nthis as a step.\n","isInternal":false,"tokens":1343,"sizeBytes":5168},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":199},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":185},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":178}],"systemPromptSnippet":"<yakaai_skills repo=\"yugabyte/yugabyte-db\">\n<!-- File: AGENTS.md (Tokens: ~1343 | Category: root-instruction) -->\n# AGENTS.md\n\nThis document provides a guide for agents working on YugabyteDB\n\n### Deploying and running\n\nFor agents that want to deploy, configure and run YugabyteDB refer to instructions at ./docs/content/stable/quick-start\n\n### Repo Structure\n\n| Directory | What it contains |\n|---|---|\n| `src/` | Core database code: PostgreSQL fork (`src/postgres/`), YugabyteDB C++ storage engine (`src/yb/`), Odyssey connection pooler (`src/odyssey/`) |\n| `java/` | Java client library, CDC connector, and DB tests |\n| `managed/` | YugabyteDB Anywhere (YBA) platform — orchestration UI, CLI, node agent, and backend (Scala/Java) |\n| `docs/` | Source files for the docs website (docs.yugabyte.com) |\n| `python/` | Python build utilities and test infrastructure scripts |\n| `build-support/` | Build system scripts, linting, and third-party dependency tooling |\n| `cmake_modules/` | CMake modules for locating dependencies and custom build functions |\n| `cloud/` | Docker, Kubernetes, and Grafana deployment configurations |\n| `yugabyted-ui/` | Yugabyted web UI (React frontend + Go API server) |\n| `architecture/` | Internal design documents and architecture specs |\n| `troubleshoot/` | Troubleshooting framework backend and UI |\n\n### Coding and Development\n\nWhen working on DB code (`src/`), refer to `src/AGENTS.md` for build and test guidance\n\n## Cursor Cloud specific instructions\n\n### Environment\n\nThe VM image is `yugabyteci/yb_build_infra_almalinux9_x86_64` which ships with: Clang, JDK 17, Go, Python 3.11, CMake, Ninja, SBT, Node.js 22, Rust, and all C++ build dependencies.\n\n### Building from source\n\n```bash\n./yb_build.sh release daemons initdb --sj --skip-pg-parquet --no-odyssey --no-ybc\n```\n\nThis is the Cloud environment `install` command. Builds snapshot `build/latest` (yb-master, yb-tserver, postgres, initdb). Agents booting from a successful Build already have those binaries; rerun only if the branch changes build inputs. Do not start yugabyted in `install`; Builds keep files, not processes.\n\nFlags: `--sj` skips Java, `--skip-pg-parquet` skips the parquet extension, `--no-odyssey` skips the connection pooler, `--no-ybc` skips the backup controller. Add targets back as needed. First compile is ~15-20 minutes on 8 vCPUs; later Builds reuse `/opt/yb-build` and incremental objects.\n\n### Running the database\n\nIf `build/latest` is present, start the cluster. Otherwise compile first.\n\n```bash\npython3 bin/yugabyted start --advertise_address 127.0.0.1 --base_dir /tmp/yb-data\n```\n\nFor a multi-node cluster, start additional nodes with `--join <first-node-address>` and a distinct `--advertise_address` and `--base_dir` each.\n\nPorts: YSQL on 5433, YCQL on 9042, yb-master UI on 7000, yb-tserver UI on 9000.\n\nConnect: `build/latest/postgres/bin/ysqlsh -U yugabyte -d yugabyte -h 127.0.0.1`\n\n### Yugabyted UI\n\n`yugabyted-ui/ui/`: `npm ci` (Node.js >= 22.18), `npm start` on port 3000, `npm run typecheck`.\n\n### Prose discipline — write for the reader, not for volume\n\nAI-written text runs long: PR and diff descriptions that narrate the diff, comments that\nrestate the line below them, design docs padded with editorial framing. It reads as\nthorough, but it costs review time, and every extra sentence is one more claim that has to\nstay true as the code moves.\n\nThere are no hard limits here. Judge each piece by what a reader who already knows this\nrepo needs:\n\n- **Code comments** — don't restate the code. Comment the *why* when it isn't obvious: an\n  invariant, a cross-component contract, a locking or ordering constraint, a workaround and\n  the upstream bug behind it. Not a label for the block below it, not narration of the\n  change you just made.\n- **PR / Phorge diff descriptions** — the motivation (a reviewer who doesn't know why is\n  the expensive case), what changed, and whatever the reader must *act* on: new gflags,\n  upgrade/rollback consequences, migration steps. Not a narration of the diff. The test\n  plan is a separate section — keep it to what was run.\n- **Design docs (`architecture/`) and agent docs (`AGENTS.md`, `.claude/skills/`)** — how\n  the system is wired today, why it's built that way, and what the reader has to do. Cut\n  restated context and the history of what the code used to do.\n- **Commit messages** — subject, plus the why when the why isn't obvious.\n\nThe test for a sentence: would a reader who knows this repo do or believe anything\ndifferently without it? If not, cut it.\n\n**Motivation is not filler** — why a design is the way it is is exactly what a reader can't\nrecover from the code; what's being cut is text that says the same thing twice, not text\nthat explains. And don't over-correct: the goal is *fewer, load-bearing* words, not\nstripped docs. Deleting a section that describes live behavior is a worse outcome than\nleaving it wordy, and this applies to your own diff, not a cleanup tour of files you didn't\ntouch.\n\nThis does **not** apply to the user-facing docs website (`docs/`), which follows its own\neditorial style guide and is written for readers who do *not* know this repo.\n\nTrim before you publish, not in review: the `create-pr` and `create-diff` skills re-check\nthis as a step.\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/yugabyte/yugabyte-db/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}