database-design

Design or review database schemas, indexes, constraints, and data access trade-offs before implementation hardens around weak persistence choices.

Skill by gclm

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/gclm-database-design

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Design or review database schemas, indexes, constraints, and data access trade-offs before implementation hardens around weak persistence choices.

Use cases: design, backend, data

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/database-design

What's inside

Skill name: database-design
Description: Design or review database schemas, indexes, constraints, and data access trade-offs before implementation hardens around weak persistence choices.
License: MIT
Instructions: 42 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
schema-checklist.md · references/

SKILL.md (first lines)

# Database Design

Use this skill when a task changes persistence structure, query shape, indexing, or long-term data modeling.

## Read First

- current schema, models, or migration files
- query patterns and access paths
- data integrity or retention constraints
- `docs/reference/requirements.md` and `harness/state.md` if they exist
- `harness/history.md` if it exists
- `references/schema-checklist.md` when you need a stronger schema checklist

## Goals

- choose a schema that matches actual query and mutation paths
- make constraints and invariants explicit
- surface index, migration, and compatibility implications early
- avoid accidental coupling between application convenience and poor data design

## Steps

1. Restate the entities, relationships, and lifecycle rules.
2. Identify the dominant read and write paths.
3. Design the schema and constraints around those paths.
4. Consider indexing, integrity, and data-lifecycle implications.
5. Consider migration and backfill cost if the data already exists.
6. Report trade-offs rather than pretending there is only one valid shape.

Read `references/schema-checklist.md` when you need a more detailed schema pass.

## Output

Report:

- entities and relationships
- recommended schema shape
- indexes and constraints
- migration implications
- trade-offs and risks

From gclm/super-stack, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Mar 29, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/gclm/super-stack
Website: github.com/gclm/super-stack#readme
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from gclm

Cite this page

database-design skill. Agent Mart. https://agentmart.dev/skills/gclm-database-design (last updated 2026-10-24)