484건 · 관련도순
SQL injection — error-based, blind boolean, time-based ve UNION tekniklerini kapsar; CTF'te login bypass, veri çekme ve flag okumak için tam otomatik exploit şablonları içerir
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert database administrator specializing in high-availability systems, performance optimization, and disaster recovery. Masters PostgreSQL, MySQL, MongoDB, and Redis with focus on reliability, scalability, and operational excellence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Database optimization, query tuning, indexing strategies, migration management, and performance monitoring for PostgreSQL with Drizzle ORM. Use when optimizing slow queries, designing schemas, creating migrations, or setting up database monitoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Change the sync configuration of an existing data warehouse schema — switch sync_type, pick a different incremental_field, set primary_key_columns, choose cdc_table_mode, or change sync_frequency. Use when the user asks "switch my orders table from full refresh to incremental", "this table is syncing too slowly / too frequently", "I need to pick a different incremental column", "set up CDC for this Postgres table", or when diagnosis of a failing sync pointed to an incremental-field or PK misconfiguration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks about revenue, payments, subscriptions, billing, CRM deals, support tickets, production database tables, or other data that PostHog does not collect natively. Also use when a query fails because a table does not exist or returns no results for expected external data. The data warehouse can import from SaaS tools (Stripe, Hubspot, etc.), production databases (Postgres, MySQL, BigQuery, Snowflake), and other arbitrary data sources. Covers checking existing sources, identifying the right source type, and guiding the setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose why a data warehouse sync is failing and recommend the right recovery action. Use when the user asks "why isn't my Stripe/Postgres/Hubspot sync working?", "this table has been stuck for hours", "the data in the warehouse looks wrong", or wants to troubleshoot a specific source or schema. Covers source-level vs schema-level failures, stuck Running states, credential and schema-drift errors, incremental-field misconfig, CDC prerequisite failures, and the cancel / reload / resync / delete-data recovery actions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Supabase (オープンソース Firebase 代替・BaaS) リファレンス。 PostgreSQL ベース、Auth (Email / OAuth / Magic Link / Phone / SSO)、Storage、 Edge Functions (Deno)、Realtime (subscriptions / presence / broadcast)、Vector embeddings、 supabase-js、@supabase/server (withSupabase)、supabase CLI (supabase stack)、 Supabase MCP サーバー、RLS (Row Level Security)、migrations。 SQL Server / node-mssql は別スキル mssql。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates strictly typed Drizzle ORM schemas for PostgreSQL with indexes, foreign keys, and Zod schema deduction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides patterns to configure AWS RDS (Aurora, MySQL, PostgreSQL) with Spring Boot applications. Configures HikariCP connection pools, implements read/write splitting, sets up IAM database authentication, enables SSL connections, and integrates with AWS Secrets Manager. Use when setting up RDS connections in Spring Boot, configuring connection pooling, or managing database credentials securely.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Revisa cambios de performance de queries ClickHouse y Postgres (vambe-datascience, CRM, réplicas) contra los errores y aprendizajes de la ronda
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for building and refactoring a FastAPI + Prefect + PostgreSQL/pgvector analytics pipeline that extracts insights from chat data using LLM classification, embeddings, UMAP/HDBSCAN clustering, and narrative generation. Use this skill whenever working on this project's codebase — including adding features, refactoring, debugging, creating new endpoints, modifying pipeline stages, or reviewing architecture decisions. Also trigger when the user asks about project structure, stack decisions, async migration, or best practices for this specific system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Develop Openrind Shell's OpenShell-supervised PostgreSQL FUSE runtime, compatibility sync runtime, and just-bash library.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch and diagnose the required Haloop-routed PostgreSQL FUSE runtime in Openrind Desktop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query PostgreSQL with pg and navigate Openrind Shell's primary FUSE or compatibility workspace; /db is custom-agent-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bun runtime and modern JavaScript backend practices, including Bun-native tooling (bun run/test/build) and PostgreSQL usage guidance. Use when building or reviewing Bun-based services, APIs, scripts, or when Bun-specific workflow questions arise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Database (PostgreSQL) SQL best practices for clean, performant, and maintainable queries. Use when writing or reviewing SQL, schema changes, or database-related guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when running analytical SQL over Parquet/CSV/JSON without a warehouse, replacing pandas for data wrangling, joining S3 data in-place, building local data marts, or embedding OLAP into an app. Triggers: read_parquet/read_csv setup, partitioned dataset queries, hive partitioning, glob patterns for S3, COPY TO export, attach Postgres/MySQL, UDFs in Python/R, MotherDuck cloud sync, columnar performance vs row stores. NOT for OLTP workloads (concurrent writes), distributed analytics at petabyte scale (use Spark/Trino), or vector search (use pgvector/Lance).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs and audits data retention and file compaction for an embedded SQLite datastore in a long-lived service — a unified retention registry (one declared policy per table), TTL / absolute-age / row-count-cap policies, a fail-loud coverage guard, WAL/checkpoint tuning, and auto_vacuum/incremental-vacuum so pruning actually shrinks the file. Use when a SQLite DB grows unbounded, a table has an index but no DELETE, a pruned DB never shrinks on disk, metrics are stored as raw events forever, or a new table needs bounding. Keywords retention policy, TTL, reaper, prune, VACUUM, auto_vacuum, incremental_vacuum, WAL checkpoint, freelist, DB bloat, row cap, per-tenant quota. NOT for Postgres/MySQL/server-DB partitioning or TTL, log-line rate-limiting/sampling, backup/replication, schema migrations, or query-performance indexing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PgBouncer, connection optimization, and pooling strategies for database performance. Activate on: connection pool, PgBouncer, database connections, pool size, connection limit, Prisma pool, Drizzle pool. NOT for: query optimization (use data-warehouse-optimizer), database schema design (use dimensional-modeler).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when applying Cloudflare D1 migrations, fighting Supabase migration history vs SQL execution, choosing direct psql over CLI, designing idempotent migrations, debugging schema drift between local and remote, or recovering after a half-applied migration. Triggers: supabase migration repair instructions appearing, table missing after "applied" status, "Tenant or user not found" when running psql, --remote vs --local D1 confusion, NOT NULL on a populated column, foreign key constraint failures, drift between staging and prod schemas. NOT for Mongo/document migrations, ORM-managed migrations specifically (Prisma/Drizzle have their own conventions), or pure data backfills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Doctrine for all Supabase realtime: postgres_changes, broadcast, presence. Use before writing a `.channel(`/useChannel subscription, echo suppression, reconnect logic, an autosave loop beside realtime, or replacing polling with live updates, or when the tab freezes, messages duplicate, or a subscription delivers nothing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Relocating a live, still-used table to another Postgres schema with every reference intact. Use when asked to move or rehome a table into a schema, or to pull a table out of public into a domain schema. NOT for retiring a table (use db-deprecate-table).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, SQL Server
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.