Database

rails-jobs

by Shoebtamboli

Use when setting up background jobs, caching, or WebSockets - SolidQueue, SolidCache, SolidCable (TEAM RULE #1 - NEVER Sidekiq/Redis)

rails-models

by Shoebtamboli

ActiveRecord patterns, migrations, validations, callbacks, associations

rails-debugging

by Shoebtamboli

Use when debugging Rails issues - provides Rails-specific debugging tools (logs, console, byebug, SQL logging) integrated with systematic debugging process

culinary-assistant

by nweii

"Culinary guidance for cooking, recipes, and meal planning. Use for kitchen techniques, substitutions, and format conversion (Mela, Schema.org). Handles recipe parsing and improvements."

aid-finances

by nweii

"Expert financial guidance for budgeting, investments, and retirement planning. Use for analyzing market strategies, debt management, or general personal finance questions."

use-tailwind-v4

by nweii

"Tailwind CSS v4 reference and migration guide. Use for v4 projects, syntax changes, upgrading from v3, and troubleshooting v4-specific utility patterns or configuration differences."

using-heavy-mcps

by nweii

"Use mcporter and jq to reduce token bloat from heavy MCPs like Sanity or Brain vault. Filter and compact tool outputs outside chat to feed only essential data back to the model."

configurator-schema

by saleor

"Config.yml schema, entity structure, and validation rules. Use when asking about YAML format, required fields, entity identification, or config validation errors. Do NOT use for general YAML questions unrelated to Saleor Configurator."

update

by assistant-ui

Update assistant-ui and AI SDK to latest versions. Detects current versions, identifies breaking changes, and executes migrations.

questdb

by questdb

Use this skill whenever working with QuestDB — a high-performance time-series database. Trigger on any mention of QuestDB, time-series SQL with SAMPLE BY, LATEST ON, ASOF JOIN, ILP ingestion, or the questdb Python/Go/Java/Rust/.NET client libraries. Also trigger when writing Grafana queries against QuestDB, creating materialized views for time-series rollups, working with order book or financial market data in QuestDB, or any SQL that involves designated timestamps or time-partitioned tables. QuestDB extends SQL with unique time-series keywords — standard PostgreSQL or MySQL patterns will fail. Always read this skill before writing QuestDB SQL to avoid hallucinating incorrect syntax.

discover-diagrams

by rand

Automatically discover diagram and visualization skills when working with flowcharts, sequence diagrams, architecture diagrams, ER diagrams, Gantt charts, mindmaps, or any visual documentation using Mermaid.js. Activates for documentation and visualization tasks.

discover-protocols

by rand

Automatically discover protocol skills when working with HTTP, TCP, UDP, QUIC, and network protocols

discover-database

by rand

Automatically discover database skills when working with SQL, PostgreSQL, MongoDB, Redis, database schema design, query optimization, migrations, connection pooling, ORMs, or database selection. Activates for database design, optimization, and implementation tasks.

Spring Data JPA Implementation

by a-pavithraa

planning

by srstomp

Use when analyzing PRD documents, concept briefs, or feature specs to create implementation plans, breaking work into epics/stories/tasks with dependencies and estimates, or generating PROJECT.md and kanban tracking.

architecture-review

by srstomp

Use when auditing project structure, planning refactors, improving code organization, analyzing dependencies and module boundaries, or identifying structural issues. TypeScript/JavaScript-primary with language-agnostic patterns.

cloud-infrastructure

by srstomp

Use when provisioning cloud resources, choosing between AWS services (Lambda vs ECS vs EKS), writing CDK/IaC, designing serverless or container architectures, configuring IAM/security groups, or optimizing cloud costs.

database-design

by srstomp

Use when designing database schemas, reviewing data models, planning migrations, optimizing slow queries, or establishing database patterns. Covers relational (PostgreSQL, MySQL, SQLite), document (MongoDB), and ORM-integrated (Prisma, Drizzle, TypeORM) projects.

battle-plan

by ElliotJLT

Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.

learn-from-this

by ElliotJLT

When a session contains a significant failure, misunderstanding, or repeated mistake, analyse the root cause and draft a new skill that would have prevented it. The skill library should grow from real failures, not hypothetical improvements. Every painful debugging session is a skill waiting to be written.

pre-mortem

by ElliotJLT

Before starting ANY significant task (feature build, refactor, integration, migration, or architectural change), first imagine the project has failed. Generate 3-5 specific failure scenarios, assess risk levels, identify mitigations, then adjust the implementation plan to address high-risk items FIRST. Do not start coding until the pre-mortem is acknowledged.

split-decision

by ElliotJLT

When facing architectural decisions, technology choices, or strategic trade-offs, present options as a structured comparison and require explicit trade-off acknowledgment before proceeding. Triggers on words like "should we", "which approach", "what's the best way", or when Claude is about to recommend one approach over alternatives. Never present a single recommendation without showing viable alternatives first.

skill-creator

by ElliotJLT

Meta-skill for creating well-structured skills with proper progressive disclosure. When user wants to create a new skill, guide them through the process: purpose, triggers, instructions, guardrails, examples. Ensures skills follow the repository conventions and are immediately usable.

drip

by ElliotJLT

Track and surface the estimated water cost of Claude interactions. Every query has a physical footprint - data centers need cooling, electricity needs generation. This skill adds environmental accountability by estimating water consumption per session and surfacing it at meaningful moments. Not to induce guilt, but to create awareness of the physical cost of intelligence.