supabase-postgres-best-practices
ComunidadMITPostgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
El ZIP contiene solo este skill. Está en GitHub Releases del repo público orlandoneto/agent-skills — Ontoom es la vitrina. El crawler diario actualiza el catálogo.
Cómo instalar
- Descarga el ZIP y extrae la carpeta del skill.
- Cursor:
.agents/skills/aitmpl-supabase-postgres-best-practices/o.cursor/skills/aitmpl-supabase-postgres-best-practices/ - Claude Code:
.claude/skills/aitmpl-supabase-postgres-best-practices/ - Otras IAs:
.agents/skills/aitmpl-supabase-postgres-best-practices/
Origen / créditos: davila7/claude-code-templates
Otros skills de esta colección
- swift-concurrency-expert
Review and fix Swift concurrency issues such as actor isolation and Sendable violations.
- tailwind-patterns
Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
- tdd-workflow
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
- tech-resume-optimizer
Optimize resumes for software engineering, product management, and technical roles. Use when the user mentions software engineer, developer, PM, data scientist, ML, DevOps, or other technical role resumes.
- Telegram Bot Builder
This skill should be used when the user asks to "create a Telegram bot", "build a Telegram chatbot", "set up a Telegram webhook", "add inline keyboards to a bot", "handle Telegram callback queries", "implement Telegram payments", "send media via Telegram bot", "configure Telegram bot commands", "deploy a Telegram bot", or mentions the Telegram Bot API, telegram bot tokens, getUpdates, setWebhook, or bot frameworks like node-telegram-bot-api, grammy, python-telegram-bot, or aiogram. Provides comprehensive guidance for building production-ready Telegram bots with Node.js and Python.
- test-driven-development
You MUST use this before writing or changing any production code, including one-line fixes and when the user is in a hurry: a new feature, a bug fix, a refactor, a behavior change. Write the failing test first, run it and watch it fail for the right reason, write the minimal code that passes, then run the whole test suite before saying it is done. Skip it only for throwaway prototypes, generated code or configuration-only changes, and only with the user's OK.