Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

database-skill

Estrellas0

Forks0

Actualizado9 de febrero de 2026, 05:06

describe how to write database related code in the codebase, use when you need to add or modify database related code or user ask to optimize to the codebase

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

ambersun1234

ambersun1234/skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Arquitectos de bases de datosOcupaciones informáticas y matemáticas·SOC 15-1243

SKILL.md

readonly

name	database skill
description	describe how to write database related code in the codebase, use when you need to add or modify database related code or user ask to optimize to the codebase

database best practices

the document outlines the best practices for writing database related code in the codebase.

when to use this skill

when you need to add or modify database related code or user ask to optimize the database related code to the codebase

best practices

you should always try to select only necessary data from the database, don't select all the data from the database
if you encounter performance issue, you should check the table definition, index, query plan ... etc. to optimize the query
you should always try to set up an index for the column that has a high cardinality, for example, user id, product id ... etc.
you should always try to set up a composite index for the column that is frequently used together, for example, user id and product id ... etc.
you should always try to set up a partial index for the column that is frequently used together, for example, user id and first_bought(bool) ... etc.
you should always try to use transaction whenever possible to ensure data consistency, and rollback the transaction if the operation failed
if transaction is not applicable, you should deploy saga pattern to ensure data consistency and proper compensate mechanism
you should try to select multiple rows at once whenever possible to prevent N+1 query issue
you should avoid full table scan when query the data, like where name like '%test%' ... etc.(however where name like 'test%' is acceptable because it's a prefix scan)
for any fast query, you should always try to use database addons whenever possible, like postgresql gin and gist index, custom operator and query function ... etc.
if database join is not applicable, you should use multiple queries to get the data and merge it in the application layer
for pagination query, always use cursor based pagination whenever possible, don't use offset based pagination

Más de este repositorio

mismo repositorio

code-review-guideline-skill

ambersun1234/skills

describe how to review code with best practices, use when user ask for help with code review or you need to implement the code

2026-03-180

cache-skill

ambersun1234/skills

describe how to write cache related code in the codebase, use when you need to add or modify cache related code or user ask to optimize the cache related code to the codebase

2026-02-090

integration-test-skill

ambersun1234/skills

describe how to write integration tests or general tests for the codebase, use when you need to add or modify integration tests to the codebase

2026-02-090

logging-best-practice-skill

ambersun1234/skills

describe how to do the logging in the codebase, use when you need to add logger to the codebase

2026-02-090

message-queue-skill

ambersun1234/skills

describe how to write message queue related code in the codebase, use when you need to add or modify message queue related code or user ask to optimize the message queue related code to the codebase

2026-02-090

middleware-skill

ambersun1234/skills

describe how to write middleware code in the codebase, use when you need a filter or interceptor to process the request or response

2026-02-090

database best practices

the document outlines the best practices for writing database related code in the codebase.

when to use this skill

when you need to add or modify database related code or user ask to optimize the database related code to the codebase

best practices

you should always try to select only necessary data from the database, don't select all the data from the database

if you encounter performance issue, you should check the table definition, index, query plan ... etc. to optimize the query

you should always try to set up an index for the column that has a high cardinality, for example, user id, product id ... etc.

you should always try to set up a composite index for the column that is frequently used together, for example, user id and product id ... etc.

you should always try to set up a partial index for the column that is frequently used together, for example, user id and first_bought(bool) ... etc.

you should always try to use transaction whenever possible to ensure data consistency, and rollback the transaction if the operation failed

if transaction is not applicable, you should deploy saga pattern to ensure data consistency and proper compensate mechanism

you should try to select multiple rows at once whenever possible to prevent N+1 query issue

you should avoid full table scan when query the data, like where name like '%test%' ... etc.(however where name like 'test%' is acceptable because it's a prefix scan)

for any fast query, you should always try to use database addons whenever possible, like postgresql gin and gist index, custom operator and query function ... etc.

if database join is not applicable, you should use multiple queries to get the data and merge it in the application layer

for pagination query, always use cursor based pagination whenever possible, don't use offset based pagination