Database
Database management and queries
sql
by miles990
SQL patterns for database querying and design
e-commerce
by miles990
E-commerce platforms, payment processing, and shopping cart patterns
database
by miles990
Database design, SQL, NoSQL, and data management patterns
JQL Patterns Skill
by yebot
Document organization-specific patterns
SQLite Skill for better-t-stack
by gruckion
```
Swift Concurrency Expert Guide
by mosif16
"Deep dive into Swift's async/await runtime, Sendable enforcement, actors, and migration strategies."
pydantic
by jiatastic
Pydantic models and validation. Use when: (1) Defining schemas, (2) Validating input/output, (3) Generating JSON schema.
architecture-monolith
by KentoShimizu
"Modular monolith architecture workflow for strong domain boundaries, transactional consistency, and operational simplicity in a single deployable. Use when teams need fast delivery and coherent data consistency with controlled complexity; do not use when independent runtime scaling boundaries are mandatory."
performance-audit
by truongnat
Audit and optimize application performance across frontend, backend, and database layers. Identifies bottlenecks, provides actionable optimization recommendations, and measures improvements. Use when the app feels slow, Lighthouse scores are low, or API response times exceed targets.
angular-migration
by ngxtm
"Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or ..."
code-review
by truongnat
Perform deep semantic code reviews that go beyond syntax checking. Evaluates architecture adherence, security vulnerabilities, performance bottlenecks, and maintainability. Use when reviewing PRs, auditing code quality, or when the user asks for a code review of any file or module.
db-migration-strategy
by KentoShimizu
"Schema migration strategy workflow for sequencing changes, compatibility windows, and rollback-safe rollout in live systems. Use when schema evolution impacts running services; do not use for static greenfield schemas without deployment constraints."
db-query-optimization
by KentoShimizu
"Query optimization workflow for reducing latency and resource cost through plan-aware rewrites and access-path improvements. Use when hot-path query behavior is the bottleneck; do not use for conceptual schema redesign without workload evidence."
senior-backend
by truongnat
Elite backend engineering standards focused on Clean Architecture, high-performance patterns, rigorous security, and standardized error handling. Use when building robust APIs, distributed systems, or implementing complex business logic.
db-index-strategy
by KentoShimizu
"Index strategy workflow for balancing read latency, write amplification, and plan stability on critical query paths. Use when query performance depends on index design trade-offs; do not use for high-level conceptual modeling."
Agent Tool Builder
by mayurrathi
"Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar..."
architecture-design
by truongnat
Design software architecture and produce formal Architectural Decision Records (ADRs). Analyzes trade-offs between approaches, defines component boundaries, data models, and technology choices. Use when planning a new feature, system migration, or when the user asks for architecture advice.
mercadopago-integration
by martinacostadev
Integrate MercadoPago Checkout Pro (redirect-based) into Next.js applications with any PostgreSQL database (Supabase, AWS RDS, Neon, PlanetScale, self-hosted, Prisma, Drizzle, or raw pg). Use when the user needs to: (1) Add MercadoPago payment processing to a Next.js app, (2) Create a checkout flow with MercadoPago, (3) Set up payment webhooks for MercadoPago, (4) Build payment success/failure pages, (5) Create a shopping cart with payment integration, (6) Troubleshoot MercadoPago integration issues (auto_return errors, webhook failures, hydration mismatches, double submissions). Triggers on requests mentioning MercadoPago, Mercado Pago, payment integration with MP, Argentine/Latin American payment processing, or checkout with MercadoPago. Supports all MercadoPago countries: Argentina (ARS), Brazil (BRL), Mexico (MXN), Colombia (COP), Chile (CLP), Peru (PEN), Uruguay (UYU). This skill is a code-generation template — it does NOT execute financial transactions. All generated code is presented for human review and requires explicit user approval before being written to disk. Financial code templates are stored in reference files and are never auto-executed.
code-quality-standards
by webdevtodayjason
Code quality standards including SOLID principles, design patterns, code smells, refactoring techniques, naming conventions, and technical debt management. Use when reviewing code, refactoring, ensuring quality, or detecting code smells.
airtable-automation
by ngxtm
"Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas."
agent-tool-builder
by ngxtm
"Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessar..."
db-replication-sharding
by KentoShimizu
"Replication and sharding workflow for scaling read/write throughput while managing consistency, failover, and data distribution risk. Use when single-node limits are reached or resilience requires topology changes; do not use for local query tuning only."
architecture-clean-architecture
by KentoShimizu
"Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications."
db-logical-design
by KentoShimizu
"Logical database design workflow for table structure, key strategy, constraints, and relational consistency. Use when durable schema semantics must be defined before physical tuning; do not use for query-only optimization tasks."