# Aider Coding Assistant Guidelines Path: `.aideprules` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.aideprules) # Project Instructions & Agent Workflow Path: `INSTRUCTIONS.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/INSTRUCTIONS.md) # LLM Full Documentation Context Path: `llms-full.txt` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/llms-full.txt) # LLM Index & Context Digest Path: `llms.txt` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/llms.txt) # Core System Prompt & Persona Path: `PROMPT.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/PROMPT.md) # Agent Prompts Catalog Path: `PROMPTS.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/PROMPTS.md) # Multi-Agent Routing & Delegation Matrix Path: `ROUTING.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/ROUTING.md) # Development & Architecture Rules Path: `RULES.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/RULES.md) # Workspace Skills & Capabilities Index Path: `SKILLS.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/SKILLS.md) # System Architecture & Agent Directives Path: `SYSTEM.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/SYSTEM.md) # ProxySQL Test Infrastructure - Agent Skill Guide This guide provides step-by-step instructions for agents to run ProxySQL tests using the Unified CI infrastructure. ## Prerequisites Before running tests, ensure: 1. Docker is installed and running 2. The `proxysql-ci-base` image is built (see README.md section 0) 3. You have sudo access for log directory management ## Quick Start - Run a Specific Test Group ```bash # 1. Set required environment variables export INFRA_ID="dev-$USER" export TAP_GROUP="legacy-binlog-g1" # or your target group export INFRA_TYPE="infra-mysql57-binlog" # optional, inferred from group # 2. Run the full pipeline (starts infra + runs tests) ./test/infra/control/ensure-infras.bash ./test/infra/control/run-tests-isolated.bash ``` ## Step-by-Step Manual Execution Use this approach when you need more control or want to debug infrastructure issues. ### Step 1: Environment Setup ```bash export WORKSPACE=$(pwd) export INFRA_ID="dev-$USER" # Unique namespace for isolation export TAP_GROUP="legacy-binlog-g1" source test/infra/common/env.sh ``` **Critical Environment Variables:** - `INFRA_ID` - **Required**. Unique namespace for containers/networks - `TAP_GROUP` - The test group from `test/tap/groups/groups.json` - `ROOT_PASSWORD` - Auto-derived from INFRA_ID hash if not set ### Step 2: Start Infrastructure ```bash # Option A: Use the helper (recommended) ./test/infra/control/ensure-infras.bash # Option B: Manual per-infrastructure startup cd test/infra/infra-mysql57-binlog export INFRA_ID="dev-$USER" ./docker-compose-init.bash cd ../../../ ``` ### Step 3: Start ProxySQL ```bash export INFRA_ID="dev-$USER" ./test/infra/control/start-proxysql-isolated.bash ``` Wait for "Ready." message. If it crashes, check logs: ```bash docker logs proxysql.${INFRA_ID} ``` ### Step 4: Configure ProxySQL Backend ```bash cd test/infra/infra-mysql57-binlog export INFRA_ID="dev-$USER" ./bin/docker-proxy-post.bash ``` **Verify configuration:** ```bash docker exec proxysql.${INFRA_ID} mysql -uradmin -pradmin -h127.0.0.1 -P6032 \ -e "SELECT hostgroup_id, hostname, port, gtid_port, status FROM mysql_servers;" ``` ### Step 5: Run Tests ```bash export INFRA_ID="dev-$USER" export TAP_GROUP="legacy-binlog-g1" ./test/infra/control/run-tests-isolated.bash ``` **Run only specific tests:** ```bash export TEST_PY_TAP_INCL="test_binlog.*" ./test/infra/control/run-tests-isolated.bash ``` ## Common Issues and Solutions ### Issue: "Directory Not Empty" Error **Cause:** Previous infrastructure data exists. **Solution:** ```bash # Destroy existing infrastructure first cd test/infra/infra-mysql57-binlog export INFRA_ID="dev-$USER" ./docker-compose-destroy.bash sudo rm -rf ./logs/infra-mysql57-binlog-${INFRA_ID} sudo rm -rf ../../ci_infra_logs/${INFRA_ID} ``` ### Issue: "Access denied for user 'root'" **Cause:** ROOT_PASSWORD not set or empty in ProxySQL. **Solution:** 1. Ensure `.env` defines ROOT_PASSWORD: ``` ROOT_PASSWORD=${ROOT_PASSWORD:-$(echo -n "${INFRA_ID:-dev}" | sha256sum | head -c 10)} ``` 2. Re-run `docker-proxy-post.bash` after setting INFRA_ID 3. Verify: `docker exec proxysql.${INFRA_ID} mysql -uradmin -pradmin -h127.0.0.1 -P6032 -e "SELECT username, password FROM mysql_users;"` ### Issue: "Max connect timeout reached while reaching hostgroup" **Cause:** MySQL containers not running or misconfigured. **Solution:** ```bash # Check container status docker ps --format "table {{.Names}}\t{{.Status}}" | grep infra-mysql57-binlog # Check network aliases docker network inspect ${INFRA_ID}_backend # Restart infrastructure if needed ``` ### Issue: "GTID: failed to connect to ProxySQL binlog reader on port 6020" **Cause:** Reader containers not running or gtid_port misconfigured. **Solution:** 1. Verify reader containers are running: ```bash docker ps | grep reader ``` 2. Check mysql_servers has gtid_port set: ```bash docker exec proxysql.${INFRA_ID} mysql -uradmin -pradmin -h127.0.0.1 -P6032 \ -e "SELECT hostname, gtid_port FROM mysql_servers;" ``` ### Issue: Test runs but no queries executed (act_queries: 0) **Cause:** Connection pool not initialized or query routing issue. **Solution:** 1. Check mysql_users exist 2. Verify mysql_query_rules loaded 3. Check stats_mysql_connection_pool for connections 4. Try running test individually after infrastructure warms up ## Test Results Location After tests complete, logs are in: ``` ci_infra_logs/${INFRA_ID}/ ├── proxysql/ # ProxySQL logs │ ├── proxysql.log │ └── proxysql.db └── tests/proxysql-tester.py/ ├── tap_tests.log # Test runner log └── tests/ ├── test_name-t.log # Individual test output └── test_name-t.proxysql.log # ProxySQL log during test ``` **Check test results:** ```bash # Find test exit code grep "RC:" ci_infra_logs/${INFRA_ID}/tests/proxysql-tester.py/tests/test_name-t.log # View compressed logs zcat ci_infra_logs/${INFRA_ID}/tests/proxysql-tester.py/tests/test_name-t.log.gz ``` ## Debugging Tips ### 1. Check Container Connectivity ```bash # From ProxySQL container, test MySQL connection docker exec -it proxysql.${INFRA_ID} bash mysql -h mysql1.infra-mysql57-binlog -P 3306 -u root -p # Test reader connection telnet mysql1.infra-mysql57-binlog 6020 ``` ### 2. Monitor ProxySQL Runtime ```bash # Watch connection pool docker exec proxysql.${INFRA_ID} mysql -uradmin -pradmin -h127.0.0.1 -P6032 \ -e "SELECT * FROM stats_mysql_connection_pool;" -t # Watch query stats docker exec proxysql.${INFRA_ID} mysql -uradmin -pradmin -h127.0.0.1 -P6032 \ -e "SELECT * FROM stats_mysql_query_digest;" -t | head -20 ``` ### 3. Infrastructure Verification Script ```bash # Check all required containers are running docker ps --format "{{.Names}}" | grep ${INFRA_ID} # Verify network docker network ls | grep ${INFRA_ID} # Check logs for errors docker logs proxysql.${INFRA_ID} 2>&1 | grep -i error | tail -20 ``` ## Cleanup ```bash # Stop test runner (if still running) docker rm -f test-runner.${INFRA_ID} # Stop ProxySQL ./test/infra/control/stop-proxysql-isolated.bash # Destroy infrastructure cd test/infra/infra-mysql57-binlog export INFRA_ID="dev-$USER" ./docker-compose-destroy.bash # Clean up logs (optional) sudo rm -rf ci_infra_logs/${INFRA_ID} ``` ## Testing Different Configurations ### Run a Single Test ```bash export INFRA_ID="single-test" export TAP_GROUP="legacy-binlog-g1" export TEST_PY_TAP_INCL="test_binlog_reader-t" ./test/infra/control/ensure-infras.bash ./test/infra/control/run-tests-isolated.bash ``` ### Test with Different INFRA_ID (parallel runs) ```bash # Terminal 1 export INFRA_ID="test-a" export TAP_GROUP="legacy-binlog-g1" ./test/infra/control/ensure-infras.bash ./test/infra/control/run-tests-isolated.bash # Terminal 2 (completely isolated) export INFRA_ID="test-b" export TAP_GROUP="legacy-binlog-g1" ./test/infra/control/ensure-infras.bash ./test/infra/control/run-tests-isolated.bash ``` ## Agent Checklist Before asking user about test failures: - [ ] `INFRA_ID` is set and consistent across all commands - [ ] `TAP_GROUP` is defined in `test/tap/groups/groups.json` - [ ] Infrastructure containers are running (`docker ps`) - [ ] ProxySQL container is running and healthy - [ ] MySQL servers registered in ProxySQL (`SELECT * FROM mysql_servers`) - [ ] mysql_users exist with correct passwords - [ ] Test logs exist in `ci_infra_logs/${INFRA_ID}/tests/` - [ ] Checked test log for specific error messages - [ ] Checked ProxySQL log for crashes or errors # Cursor IDE Native Rules Path: `.cursorrules` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.cursorrules) # CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. ## Project Overview ProxySQL is a high-performance, protocol-aware proxy for MySQL (and forks like MariaDB, Percona Server) and PostgreSQL. Written in C++17, it provides connection pooling, query routing, caching, and monitoring. Licensed under GPL. ## Build Commands The build system is GNU Make-based with a three-stage pipeline: `deps` → `lib` → `src`. ```bash # Full release build (auto-detects -j based on nproc/hw.ncpu) make # Debug build (-O0, -ggdb, -DDEBUG) make debug # Build with ASAN (requires no jemalloc) NOJEMALLOC=1 WITHASAN=1 make build_deps_debug && make debug && make build_tap_test_debug # Build TAP tests (requires proxysql binary built first) make build_tap_tests # release make build_tap_test_debug # debug # Clean make clean # clean src/lib make cleanall # clean everything including deps # Build packages make packages ``` ### Feature Tiers The same codebase produces three product tiers via feature flags: | Tier | Flag | Version | Adds | |------|------|---------|------| | Stable | (default) | v3.0.x | Core proxy | | Innovative | `PROXYSQL31=1` | v3.1.x | FFTO, TSDB | | Plugin Chassis | `PROXYSQL40=1` | v4.0.x | Plugin loader + ABI (4-phase lifecycle, query-hook, shared Prometheus); builds and packages all v4.0 plugins including mysqlx and genai/MCP | **`PROXYSQL40=1` implies `PROXYSQL31=1` which implies `PROXYSQLFFTO=1` and `PROXYSQLTSDB=1`.** There is no separate `PROXYSQLGENAI` flag — `PROXYSQL40=1` builds and packages all v4.0 plugins (mysqlx, genai/MCP, anomaly detection). All AI/MCP/RAG/LLM features live in `plugins/genai/` and load as a `.so` at runtime. ### Building a tier — pass the flag on EVERY make, and clean when switching (IMPORTANT) **CI never builds the bare default.** Every CI package/test build sets a tier flag: `PROXYSQL31=1` (v3.1) or `PROXYSQL40=1` (v4.0/genai) — see `.github/workflows/CI-*.yml`. Build with the tier you are targeting. **Bare `make` compiles the Stable tier with FFTO and TSDB left OUT** (`MySQLFFTO.cpp`/`PgSQLFFTO.cpp` are excluded and the `#ifdef PROXYSQLFFTO` symbols like `*_thread___ffto_max_buffer_size` are not defined). For most work, build `PROXYSQL31=1` (or `PROXYSQL40=1` if touching plugins/genai). **The Makefile does NOT track the tier flag between invocations.** Object files and `lib/libproxysql.a` produced under one tier are silently reused when you next build under a different tier (or against a tree someone else built under a different tier). The classic symptom is a link failure: ``` undefined reference to `mysql_thread___ffto_max_buffer_size' undefined reference to `pgsql_thread___ffto_max_buffer_size' ``` This is **not** a real breakage and **not** a bug in the default build — it is a stale-object *tier mismatch* (e.g. an FFTO-enabled `libproxysql.a` linked against a `main.o` compiled without `PROXYSQLFFTO`). Do **not** "fix" it by dropping the tier flag. Fix / avoid it by cleaning when the tier changes, and by passing the SAME tier flag on every make in a session: ```bash # Switching tiers (or unsure what the tree was last built with): clean first. make clean # clears lib/ + src/ objects and libproxysql.a PROXYSQL31=1 make -j$(nproc) # then build the tier you want, consistently # If deps were built under a different tier, also: make cleanall (rebuilds deps — slow) ``` ### Build Flags - `NOJEMALLOC=1` — disable jemalloc - `WITHASAN=1` — enable AddressSanitizer (requires `NOJEMALLOC=1`) - `WITHGCOV=1` — enable code coverage - `PROXYSQLCLICKHOUSE=1` — enabled by default in current builds ## Testing Tests use TAP (Test Anything Protocol) with Docker-based backend infrastructure. ### Running TAP tests — DO NOT manually set up Docker containers **ALWAYS use `run-tests-isolated.bash`**. It handles infrastructure setup, ProxySQL start, test execution, and cleanup. Never manually create Docker networks, start containers, or run init scripts — the runner does all of that. **The proxysql binary under test must be a DEBUG build.** The isolated harness (`proxysql-tester.py`) issues debug-only admin commands (`LOAD DEBUG FROM DISK`, the `admin-debug` variable — both `#ifdef DEBUG`), so a release binary fails to (re)configure with errors like `Unknown global variable: 'admin-debug'` or `near "LOAD": syntax error`. Build with `make debug`, and pass the tier flag consistently (e.g. `PROXYSQL31=1 make debug`). The ProxySQL container runs the workspace-built binary, so after rebuilding, re-run `test/infra/control/start-proxysql-isolated.bash` to recreate **only** the ProxySQL container on the new binary (it leaves the backends up). A plain `ensure-infras.bash` will NOT pick up a rebuilt binary if ProxySQL is already running, and `docker restart` is not the supported mechanism. ```bash # Set up infrastructure (backends + ProxySQL container) WORKSPACE=$(pwd) INFRA_ID=dev-$USER TAP_GROUP=mysql84-g1 test/infra/control/ensure-infras.bash # Run all tests for a TAP group WORKSPACE=$(pwd) INFRA_ID=dev-$USER TAP_GROUP=mysql84-g1 test/infra/control/run-tests-isolated.bash # Run a SINGLE test within a group — use the TEST_PY_TAP_INCL regex filter. # DO NOT create a throwaway group to isolate one test; the test still lives in its # real group and you just filter. (See test/infra/SKILL.md and test/infra/README.md.) WORKSPACE=$(pwd) INFRA_ID=dev-$USER TAP_GROUP=legacy-g4 \ TEST_PY_TAP_INCL="pgsql-reg_test_5866_result_format-t" \ test/infra/control/run-tests-isolated.bash # Swap in a rebuilt binary without tearing down backends WORKSPACE=$(pwd) INFRA_ID=dev-$USER TAP_GROUP=mysql84-g1 test/infra/control/start-proxysql-isolated.bash # Build test binaries first (requires proxysql binary) make build_tap_tests # release make build_tap_test_debug # debug ``` Available TAP groups are defined in `test/tap/groups/groups.json`. Group names follow the pattern `-g` (e.g., `mysql84-g1`, `legacy-g2`, `pgsql16-g1`). `TEST_PY_TAP_INCL` is a regex matched against test names in the group — the documented way to run one test. ### DO NOT - **DO NOT** manually create Docker networks (`docker network create`) - **DO NOT** manually start containers (`docker start`, `docker run`) - **DO NOT** run `docker-compose-init.bash` directly — use `ensure-infras.bash` - **DO NOT** symlink build artifacts between worktrees — build in each worktree separately - **DO NOT** copy source files between worktrees or repos - **DO NOT** run `cd test/tap/tests && make` and expect tests to pass without infrastructure ### Test file conventions Test files follow the naming pattern `test_*.cpp` or `*-t.cpp` in `test/tap/tests/`. Test binaries are built via a pattern rule in `test/tap/tests/Makefile`: `make -t` compiles `-t.cpp` into `-t`. No special Makefile target is needed for new tests — just add the `.cpp` file and register it in `groups.json`. ### Reporting CI/test failures **Test quality is paramount on this project. Never dismiss a CI failure as "pre-existing" or "flaky".** Those words are observations, not analyses, and using them as a conclusion lets real bugs survive. When CI fails on a branch or PR: 1. **Read the actual failure.** Open the failing test log, the proxysql server log it produced, and the test source. Identify the specific assertion, timeout, crash, or non-zero exit. Quote the relevant lines in your report. 2. **State the root cause, not the symptom.** "Test X failed" is a symptom. The root cause is *why* — a race condition, a stale fixture, a resource leak, a protocol regression, an env mismatch, etc. 3. **Separate two distinct questions** and answer both with evidence: - *Did the current change cause this failure?* — answer via commit-by-commit reasoning and code-path analysis, not just by comparing baseline pass/fail rates. - *Is this test broken regardless of the current change?* — independent question. A failure that pre-dates the change is still a problem to fix or file, not a reason to merge over. 4. **If the root cause cannot be determined within the session**, say so explicitly and recommend the next investigation step (re-run with logs, instrument the test, file a tracking issue). Do not paper over uncertainty with "flaky". 5. **A repeatedly failing test is a higher-priority bug, not a lower one.** Recurrence is evidence that the failure mode is reproducible — that is exactly what makes it fixable. ## Architecture ### Build Pipeline ``` deps/ → builds 25+ vendored dependencies as static libraries lib/ → compiles ~121 .cpp files into libproxysql.a src/main.cpp → links against libproxysql.a to produce the proxysql binary ``` ### Dual-Protocol Design MySQL and PostgreSQL share parallel class hierarchies with the same architecture but protocol-specific implementations: | Layer | MySQL | PostgreSQL | |-------|-------|------------| | Protocol | `MySQL_Protocol` | `PgSQL_Protocol` | | Session | `MySQL_Session` | `PgSQL_Session` | | Thread | `MySQL_Thread` | `PgSQL_Thread` | | HostGroups | `MySQL_HostGroups_Manager` | `PgSQL_HostGroups_Manager` | | Monitor | `MySQL_Monitor` | `PgSQL_Monitor` | | Query Processor | `MySQL_Query_Processor` | `PgSQL_Query_Processor` | | Logger | `MySQL_Logger` | `PgSQL_Logger` | ### Core Components - **Admin Interface** (`ProxySQL_Admin.cpp`, `Admin_Handler.cpp`) — SQL-based configuration via SQLite3 backend. Supports runtime config changes without restart. Schema versions tracked in `ProxySQL_Admin_Tables_Definitions.h`. - **HostGroups Manager** — Routes connections based on hostgroup assignments. Supports master-slave, Galera, Group Replication, and Aurora topologies. - **Query Processor** — Parses queries, matches against routing rules, handles query caching via `Query_Cache`. - **Monitor** — Health-checks backends for replication lag, read-only status, and connectivity. - **Threading** — Event-based I/O using libev. `Base_Thread` base class with protocol-specific thread managers. - **HTTP/REST** (`ProxySQL_HTTP_Server`, `ProxySQL_RESTAPI_Server`) — Metrics and management endpoints. ### Key Dependencies (in deps/) - `jemalloc` — memory allocator - `sqlite3` — admin config storage - `mariadb-client-library` — MySQL protocol - `postgresql` — PostgreSQL protocol - `re2`, `pcre` — regex engines - `libev` — event loop - `libinjection` — SQL injection detection - `lz4`, `zstd` — compression - `curl`, `libmicrohttpd`, `libhttpserver` — HTTP - `prometheus-cpp` — metrics - `libscram` — SCRAM authentication ### Conditional Components - **FFTO** (Fast Forward Traffic Observer) — `MySQLFFTO.cpp`, `PgSQLFFTO.cpp` - **TSDB** — Time-series metrics with embedded dashboard - **ClickHouse** — Native ClickHouse protocol support - **GenAI / MCP / RAG / LLM** — Lives entirely in `plugins/genai/` as of the carve-out completed in Step 7. Loaded via `dlopen` when `plugins = (genai)` is configured in `proxysql.cnf`; not part of `libproxysql.a` or the `proxysql` binary. ## Code Layout - `include/` — All headers (.h/.hpp). Include guards use `#ifndef __CLASS_*_H`. - `lib/` — Core library sources (~121 files). One class per file typically. - `src/main.cpp` — Entry point, daemon init, thread spawning (~95K lines). - `test/tap/` — TAP test framework and tests. - `test/infra/` — Docker-based test environments. - `.github/workflows/` — CI/CD pipelines (selftests, TAP tests, package builds, CodeQL). **See `doc/GH-Actions/README.md` for the architecture overview** — ProxySQL uses a two-branch caller/reusable split (`CI-*.yml` on `v3.0`, `ci-*.yml` on the `GH-Actions` branch) and the doc is the authoritative reference for how it fits together. ## Agent Guidelines See `doc/agents/` for detailed guidance on working with AI coding agents: - `doc/agents/project-conventions.md` — ProxySQL-specific rules (directories, build, test harness, git workflow) - `doc/agents/task-assignment-template.md` — Template for writing issues assignable to AI agents - `doc/agents/common-mistakes.md` — Known agent failure patterns with prevention and detection ### Unit Test Harness Unit tests live in `test/tap/tests/unit/` and link against `libproxysql.a` via a custom test harness. Tests must use `test_globals.h` and `test_init.h` — see `doc/agents/project-conventions.md` for the full pattern. ## Coding Conventions - Class names: `PascalCase` with protocol prefixes (`MySQL_`, `PgSQL_`, `ProxySQL_`) - Member variables: `snake_case` - Constants/macros: `UPPER_SNAKE_CASE` - C++17 required; conditional compilation via `#ifdef PROXYSQL31`, `#ifdef PROXYSQL40`, `#ifdef PROXYSQLFFTO`, `#ifdef PROXYSQLTSDB`, `#ifdef PROXYSQLCLICKHOUSE`. (`PROXYSQLGENAI` no longer guards any core code as of Step 7 of the GenAI plugin carve-out — it lives only inside `plugins/genai/` now.) - Performance-critical code — consider implications of changes to hot paths - RAII for resource management; jemalloc for allocation - Pthread mutexes for synchronization; `std::atomic<>` for counters # Windsurf Cascade Agent Rules Path: `.windsurfrules` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.windsurfrules) # GitHub Copilot Instructions Path: `.github/copilot-instructions.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.github/copilot-instructions.md) # Roo Code Custom Persona Modes Path: `.roomodes` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.roomodes) # Roo Code Autonomous Agent Rules Path: `.roorules` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.roorules) # Cline Extension Native Directives Path: `.clinerules` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.clinerules) # Claude Plugin Marketplace Catalog Path: `.claude-plugin/marketplace.json` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.claude-plugin/marketplace.json) # Claude Plugin Marketplace Catalog Path: `marketplace.json` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/marketplace.json) # claude-plugin Plugin Manifest Path: `.claude-plugin/plugin.json` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.claude-plugin/plugin.json) # Plugin Plugin Manifest Path: `plugin.json` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/plugin.json) # genai Documentation Path: `plugins/genai/README.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/plugins/genai/README.md) # release-tools Documentation Path: `scripts/release-tools/README.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/scripts/release-tools/README.md) # pgsql_user_sync Documentation Path: `tools/pgsql_user_sync/README.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/tools/pgsql_user_sync/README.md) # Model Context Protocol (MCP) Configuration Path: `.cursor/mcp.json` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/.cursor/mcp.json) # Model Context Protocol (MCP) Configuration Path: `mcp.json` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/mcp.json) # Subagent: common-mistakes Path: `doc/agents/common-mistakes.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/doc/agents/common-mistakes.md) # Subagent: project-conventions Path: `doc/agents/project-conventions.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/doc/agents/project-conventions.md) # Subagent: readme Path: `doc/agents/README.md` [View Raw Content on GitHub](https://raw.githubusercontent.com/sysown/proxysql/HEAD/doc/agents/README.md)

Aider Coding Assistant Guidelines

Explore Related Technologies & Topics