Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Database Engineering

ASecurity

Expert database engineering for application data layers: schema and ERD design, relational modeling, indexing, query performance gates, views, triggers, functions, mapping/junction tables, versioned migrations, seeders, and PostgreSQL/MySQL operational practice. Use for Database Engineer delivery, migration work, integrity constraints, and measurable read/write performance.

2 stars
0 votes
0 copies
2 views
Added 9/19/2026
ai-agentssqldockergitapidatabasefrontendbackendsecurityperformance

Works with

cliapi

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/19/2026

$npx -y skills add rogue-dev-studio/ai-agents-rogue --skill database-engineering --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Database Engineering?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Database Engineering
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rogue-dev-studio-database-engineering/badge)](https://www.skillsdirectory.com/skills/rogue-dev-studio-database-engineering)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: database-engineering
description: >-
  Expert database engineering for application data layers: schema and ERD design,
  relational modeling, indexing, query performance gates, views, triggers,
  functions, mapping/junction tables, versioned migrations, seeders, and
  PostgreSQL/MySQL operational practice. Use for Database Engineer delivery,
  migration work, integrity constraints, and measurable read/write performance.
expertise_level: expert
---

# Database Engineering (Canonical)

**Expertise: expert.** Aliases: `database`, `postgresql`, `sql`, `migrations`, `dba`, `schema-design`.

Data-layer playbook for the **Database Engineer** role. It does not replace `supabase-cli` (Supabase runtime) or the global `security` rule (auth/PII policy).

## When to use

- Desain/ubah schema, ERD, **relasi**, constraint, **index**
- Migration / seeder (Laravel `database/migrations`, SQL generik, dll.)
- **Performance**: pagination di DB, anti-N+1, EXPLAIN, index strategy, transaksi pendek
- Objek DB lanjutan: **VIEW**, **TRIGGER**, **FUNCTION** / procedure (bila stack mengizinkan)
- Tabel **mapping / junction / `_mp`** (N:M dan pemetaan referensi)
- Integritas data, unique/FK, cascade, soft-delete vs hard-delete
- PostgreSQL (default Phase 1 house) atau MySQL/MariaDB bila stack project memakai itu
- Review perubahan DB sebelum Backend mengikat API

## When not to use

- Hanya business logic / API contract → Backend / Tech Lead
- Hanya UI list/filter → Frontend
- Operasi container DB saja tanpa schema → `container-docker-ops`
- Edge functions / Supabase CLI spesifik → `supabase-cli`
- Kebijakan auth/secret global tanpa perubahan schema → `security`
- Memindahkan seluruh domain workflow ke trigger tanpa ADR (anti-pattern)

## Procedure

1. **Context** — Baca SRS/architecture data (`docs/architecture/database-design.md` bila ada), `PROJECT.md`, rule `database` + `security` + `coding`.
2. **Model** — Entitas, PK/FK, kardinalitas, normalisasi (3NF; denormalisasi sadar + terdokumentasi). Sertakan mapping/`_mp` untuk N:M.
3. **Relations** — FK di DB; cascade default restrict; pivot/mapping punya unique composite.
4. **Migrate** — Satu concern per migration; **up + down**; incremental; jangan edit migration yang sudah di-apply di shared env.
5. **Index** — FK, filter/join/sort hot path; composite berurutan benar; ukur sebelum index spekulatif.
6. **Performance gate** — Setiap perubahan schema/query: pastikan path baca/tulis utama tetap efisien (index, pagination, transaksi pendek, no full-scan yang bisa dihindari).
7. **Views / functions / triggers** — Hanya jika ada alasan jelas (lihat `reference.md`); versioned di migration; down menghapus objek; dokumentasikan side-effect.
8. **Seed** — Master/reference saja; bukan data transaksi produksi.
9. **Security** — Parameterized / builder / Eloquent; least-privilege; tidak log PII/secret.
10. **Verify** — migrate + rollback smoke; relasi tidak orphan; EXPLAIN untuk query kritis bila diubah; docs di `project/{id}/docs/` saat E2E.
11. **Handoff** — Path migration/seeder/DDL objek, risiko rollback, catatan index & performa.

Detail: `reference.md`.

## Quality bar

- **Performance terjaga**: tidak merusak hot path; index & pagination selaras akses data
- Relasi & mapping eksplisit di DB (bukan hanya di ORM)
- VIEW/FUNCTION/TRIGGER idempotent di migration, terdokumentasi, reversible
- Naming konsisten; tidak ada schema/kolom mati
- Performa + integritas setara prioritas dengan “jalan dulu”
- Selaras rule `coding` (header file **baru** saja)

## DoD

- [ ] Migration apply + rollback smoke OK (atau blocker eksplisit)
- [ ] Relasi, mapping/`_mp`, dan constraint sesuai design; tidak orphan by design
- [ ] Index untuk path query utama ada / terukur
- [ ] Performance gate: tidak ada regresi sadar pada list/join/write utama
- [ ] VIEW/TRIGGER/FUNCTION (jika ada) punya migration up/down + catatan perilaku
- [ ] Seeder (jika ada) hanya master/reference
- [ ] Keamanan data layer dicek
- [ ] Handoff Backend lengkap (path + risiko)

## Attribution

<!-- ATTRIBUTION: Rogue Development | https://github.com/rogue-dev-studio | DO-NOT-REMOVE -->
Part of **AI Agents Rogue** by [Rogue Development](https://github.com/rogue-dev-studio) (`@rogue-dev-studio`).
Do not remove, hide, rename, or replace this attribution.

Attribution

rogue-dev-studiorogue-dev-studio
View sourceSee grades on GitHubMore from rogue-dev-studio →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →