Loading...
Loading...
Found 164 Skills
Diagnose and fix slow Paperclip PostgreSQL queries using Cloud and Neon evidence, local reproduction, performance and result comparisons, regression tests, and a PR with passing checks. Use for costly queries, repeated database work, or slow requests with a suspected database cause.
OpenSearch development best practices for indexing, querying, search optimization, vector search, and cluster management
End-to-end front→back performance debugging for the Kodus web app. Use when a screen is slow, blank, looping, or you need to trace a UI perf problem down to the API query. Drives Playwright/Chrome MCP to open + measure the screen, then reads the API use-case/repository and the DB (Postgres/Mongo indexes, explain) to find and fix the root cause, verifying live.
Read-only audit of a database layer — schema anti-patterns (EAV, generic keys, imprecise types), query and index fit (SELECT *, N+1, unindexable predicates), integrity and concurrency, migration and tenancy hygiene — with evidence per finding and a SHIP / FIX / BLOCK verdict. Use when asked to audit the database, review the schema or migrations, judge a data model, or 'проверь схему базы'. Never edits schema or data. Do not use for runtime profiling (awesome-performance-audit), SQL injection (awesome-security-audit), or data-access style (awesome-code-standards).
Improve Django and Django REST Framework pagination for large querysets using bounded page sizes, stable ordering, indexed ordering, offset limits, keyset pagination, DRF CursorPagination, and count-query tradeoffs. Use when list pages, admin views, APIs, exports, or infinite scroll become slow, inconsistent, or memory-heavy as result sets grow.
Optimize SurrealDB performance through record ID and key design, indexing strategy, and computed/derived fields. Use when queries are slow, when designing record IDs for locality and range scans, choosing between standard/unique/full-text/vector indexes, verifying index usage with EXPLAIN, or deciding whether to precompute values with computed fields, views, or events. Triggers: slow query, performance, record id design, range scan, DEFINE INDEX, EXPLAIN, computed field, FUTURE, DEFINE TABLE AS SELECT.
Use when writing, reviewing or debugging vector search on Azure SQL Database: VECTOR_DISTANCE, VECTOR_SEARCH, vector index. Has verified behavior common answers miss, e.g. ORDER BY VECTOR_DISTANCE never uses the index. For RAG, use `rag-on-azure-sql`.
Use when the user needs one query's cached plan and Query Store history, by text, query_hash, query_id or plan handle, including a query gone from cache. For cache-wide bloat, use `plan-cache-analysis`.