資料庫
SQL、NoSQL 和資料庫管理技能
4429 skills in this category
Subcategories
mongodb
Guide for implementing MongoDB - a document database platform with CRUD operations, aggregation pipelines, indexing, replication, sharding, search capabilities, and comprehensive security. Use when working with MongoDB databases, designing schemas, writing queries, optimizing performance, configuring deployments (Atlas/self-managed/Kubernetes), implementing security, or integrating with applications through 15+ official drivers. (project)
cloudflare
Guide for building applications on Cloudflare's edge platform. Use when implementing serverless functions (Workers), edge databases (D1), storage (R2, KV), real-time apps (Durable Objects), AI features (Workers AI, AI Gateway), static sites (Pages), or any edge computing solutions.
agent-sandboxes
Operate E2B agent sandboxes using the CLI. Use when user needs to run code in isolation, test packages, execute commands safely, or work with binary files in a sandbox environment. Keywords: sandbox, e2b, isolated environment, run code, test code, safe execution.
sveltekit-remote-functions
SvelteKit remote functions guidance. Use for command(), query(), form() patterns in .remote.ts files.
sudocode
ALWAYS use this skill for ALL sudocode spec and issue operations. Use when user mentions "spec", "issue", "ready", "blocked", "implement", "feature", "plan", or "feedback" with sudocode specs and issues. PROACTIVELY use at start of implementation tasks to check ready issues and understand work context. Operations include viewing (show_spec, show_issue, list_issues, list_specs), creating/modifying (upsert_spec, upsert_issue), planning features, breaking down work, creating dependency graphs, and providing implementation feedback.
ai-maestro-code-graph-query
PROACTIVELY query the code graph database to understand relationships and impact of changes. Use this skill WHEN READING any file to understand context, when searching for files, when exploring the codebase, or when you need to understand what depends on a component. This is your primary tool for understanding code structure and avoiding breaking changes.
srtd-cli
This skill should be used when the user mentions "srtd", "sql templates", "migrations-templates", "live reload sql", "supabase functions", when working with files in supabase/migrations-templates/, when .buildlog.json or srtd.config.json is detected, or when writing Postgres functions/views/triggers for Supabase.
analyze-compile-times-duckdb
Analyze Rust compilation profiling data using DuckDB to find performance bottlenecks, trait explosions, and monomorphization issues. Use after generating chrome_profiler.json with crox.
oracle
Use the @steipete/oracle CLI to bundle a prompt plus the right files and get a second-model review (API or browser) for debugging, refactors, design checks, or cross-validation.
auth
Implements authentication and payment features using Clerk, Supabase Auth, or Stripe. Use when user mentions ログイン, 認証, auth, authentication, Clerk, Supabase, 決済, payment, Stripe, 課金, サブスクリプション. Do NOT load for: 一般的なUI作成, データベース設計, 非認証機能.
ui
Generates UI components and feedback forms. Use when user mentions コンポーネント, component, UI, ヒーロー, hero, フォーム, form, フィードバック, feedback, 問い合わせ. Do NOT load for: 認証機能, バックエンド実装, データベース操作, ビジネスロジック.
fleet-agent
Context-aware development assistant for AgenticFleet with auto-learning and dual memory (NeonDB + ChromaDB). Handles development workflows with intelligent context management.
collaborating-with-codex
Delegates coding tasks to Codex CLI for prototyping, debugging, and code review. Use when needing algorithm implementation, bug analysis, or code quality feedback. Supports multi-turn sessions via SESSION_ID.
system-learn
Ingest new procedural memory (skills, patterns, docs) into the vector database.
knowledge-locator
Spatial indexing and retrieval system for finding information within memorypalaces using multi-modal search.Triggers: knowledge search, find information, locate concept, recall, spatialquery, cross-reference, discovery, memory retrieval, pr review search,past decisions, review patternsUse when: searching for stored knowledge, cross-referencing concepts,discovering connections, retrieving from palaces, finding past PR decisionsDO NOT use when: creating new palace structures - use memory-palace-architect.DO NOT use when: processing new external resources - use knowledge-intake.Consult this skill when searching or navigating stored knowledge.
testing-quality-standards
Shared testing quality metrics and standards for cross-plugin use. Referencedby pensive:test-review and parseltongue:python-testing.Triggers: testing standards, quality metrics, coverage thresholds, test quality,anti-patterns, testing best practices, quality gatesUse when: evaluating test quality, setting coverage thresholds, identifyingtesting anti-patterns, establishing quality standardsDO NOT use when: simple scripts without quality requirements.Consult this skill when establishing testing quality standards.
architecture-paradigm-hexagonal
Employ the Hexagonal (Ports & Adapters) pattern to decouple domain logic frominfrastructure, maximizing flexibility and testability.Triggers: hexagonal architecture, ports and adapters, infrastructure independence,dependency inversion, clean architecture, domain isolation, adapter pattern,infrastructure abstraction, database independence, framework independenceUse when: designing systems with strong business logic separation, anticipatinginfrastructure changes, needing easy mocking for tests, building portable domain codeDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: building simple CRUD apps without complex domain logic.Consult this skill when implementing hexagonal patterns or migrating to port-based design.
architecture-paradigm-space-based
Data-grid architecture for high-traffic stateful workloads with linear scalability.Triggers: space-based, data grid, in-memory, linear scaling, high trafficUse when: traffic overwhelms database nodes or linear scalability neededDO NOT use when: data doesn't fit in memory or simpler caching would work.
fix-issue
Fix GitHub issues using subagent-driven-development with parallel executionwhere appropriate.Triggers: fix issue, github issue, issue resolution, subagent development,parallel execution, issue workflow, gh issue, fix githubUse when: addressing GitHub issues systematically, multiple related issuesneed fixing, tasks can be parallelized across subagents, quality gates neededbetween task batchesDO NOT use when: single simple fix - just implement directly.DO NOT use when: issue needs clarification - comment first to clarify scope.Uses subagents for parallel execution with code review gates between batches.
full-stack-development
Ability to develop both front-end and back-end systems, integrating user interfaces with server logic and databases.