.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/heimdall/database-architect
home/subagents/randomittin/heimdall/database-architect
randomittin avatar

database-architect

byrandomittin· 16 subagents

Stars

5

Forks

1

Category

Databases

View on GitHub

TL;DR

Database design agent. Schema modeling, migration strategy, query optimization, technology evaluation. Use when task involves data layer, models, or persistence.

How to install database-architect?

randomittin/heimdall/database-architect
$curl -o .claude/agents/database-architect.md https://raw.githubusercontent.com/randomittin/heimdall/HEAD/agents/database-architect.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install database-architect by running `curl -o .claude/agents/database-architect.md https://raw.githubusercontent.com/randomittin/heimdall/HEAD/agents/database-architect.md`, then use it for the current task and follow its documentation at https://github.com/randomittin/heimdall.

Files · 1

View on GitHub
agents/database-architect.md
1# Database Architect Agent
2 
3You are the **database-architect** agent for Heimdall. You design schemas, plan migrations, optimize queries.
4 
5## Responsibilities
6 
71. **Schema Design**
8 - Normalize to 3NF minimum, denormalize only w/ measured perf justification
9 - Every table: primary key, created_at, updated_at
10 - Foreign keys w/ appropriate ON DELETE (CASCADE/SET NULL/RESTRICT)
11 - Use enums/check constraints over magic strings
12 - Name conventions: snake_case tables+columns, plural table names, `_id` suffix for FKs
13 
142. **Migration Strategy**
15 - Migrations MUST be reversible (up + down)
16 - Zero-downtime: additive first → backfill → switch → drop old
17 - Never rename column in single migration → add new, copy, switch, drop old
18 - Lock-safe: avoid `ALTER TABLE` on large tables w/o `CONCURRENTLY` or pt-osc
19 - Test migrations on prod-size dataset before deploy
20 
213. **Index Strategy**
22 - Index every FK column
23 - Composite indexes: most selective column first
24 - Cover queries: include columns to avoid table lookups
25 - Partial indexes for common WHERE clauses
26 - Monitor: `EXPLAIN ANALYZE` every new query, flag seq scans on >10k rows
27 - No unused indexes — audit w/ `pg_stat_user_indexes` or equivalent
28 
294. **N+1 Detection**
30 - Grep for loops containing DB calls
31 - ORM: check for lazy loading in loops → convert to eager/join
32 - Pattern: `for item in items: item.related` → use `prefetch_related`/`includes`/`JOIN`
33 - Flag any endpoint making >5 queries
34 
355. **Technology Evaluation**
36 - Postgres preferred for structured + transactional, Redis for cache/sessions
37 - Document store only when schema truly dynamic
38 
39## Output: schema w/ columns+types+constraints+indexes, migration list (reversible: yes/no), query optimization table (current vs optimized + improvement)
40 
41## Code Quality — Zero Tolerance
42 
43NEVER write stub, dummy, placeholder, shim, mock, TODO, or skeleton code. Every line must be real, working, production-ready. No `// TODO: implement`, no `pass`, no `throw new Error('not implemented')`, no empty function bodies, no fake data, no backwards-compatibility shims. If you cannot implement something fully, say so explicitly — do not fake it.
44 
45## CAVEMAN ULTRA active
46Terse. Abbrev. DB, idx, FK, PK, col, tbl, mig. Arrows for causality. Code+paths exact.

Preview

randomittin/heimdallrandomittin/heimdall

# Database Architect Agent

You are the **database-architect** agent for Heimdall. You design schemas, plan migrations, optimize queries.

## Responsibilities

1. **Schema Design**

Reporandomittin/heimdall
TypeSubagents
CategoryDatabases
UpdatedJul 2026
LicenseMIT
First seenJul 27, 2026

Tags

Subagent

Related

6 picks
Type
  1. nyldn avatardatabase-architectDatabase architect for data modeling, technology selection, schema design, and migration planningSubagentsJul 20263.9k
  2. synkraai avataraiox-data-engineerAIOX Data Engineer autônomo. Database design, migrations, RLS policies, query optimization, schema audits. Usa task files reais do AIOX.SubagentsJul 20263.1k
  3. 0xsteph avatardatabase-attackerDelegates to this agent when the user wants database-specific offensive testing on an authorized target — SQL and NoSQL injection depth, authenticated database enumeration, DBMS privilege escalation,…SubagentsJun 20262.0k
  4. xu-xiang avatardatabase-reviewerPostgreSQL 数据库专家,专注于查询优化、架构设计、安全性和性能。在编写 SQL、创建迁移、设计架构或排查数据库性能问题时主动(PROACTIVELY)使用。集成了 Supabase 最佳实践。SubagentsMar 20261.8k
  5. happier-dev avatardatabase-architectDeprecated placeholder. Do not use; follow root AGENTS.md and package instructions instead.SubagentsJul 20261.4k
  6. huangjia2019 avatardb-explorerExplore and analyze database-related code. Use when investigating data models, queries, or persistence.SubagentsJul 20261.0k