mirror of
https://github.com/ngthanhvu/kr-phim.git
synced 2026-08-10 13:27:46 +00:00
68 lines
1.9 KiB
Markdown
68 lines
1.9 KiB
Markdown
|
---
|
||
|
|
name: db-schema-designer
|
||
|
|
display_name: DB Schema Designer
|
||
|
|
description: Design normalized relational database schemas — ERDs, indexes, constraints, migrations, and performance optimization.
|
||
|
|
category: Development
|
||
|
|
platforms: [claude.ai, claude-code, api]
|
||
|
|
version: 1.0.0
|
||
|
|
author: Claude Code
|
||
|
|
tags: [db-schema-designer]
|
||
|
|
---
|
||
|
|
|
||
|
|
# DB Schema Designer
|
||
|
|
|
||
|
|
## Overview
|
||
|
|
|
||
|
|
Design normalized relational database schemas — ERDs, indexes, constraints, migrations, and performance optimization.
|
||
|
|
|
||
|
|
## When to Use This Skill
|
||
|
|
|
||
|
|
Use **DB Schema Designer** when you need to:
|
||
|
|
|
||
|
|
- Work with db schema designer tasks in your project or workflow
|
||
|
|
- Automate db schema designer operations at scale
|
||
|
|
- Generate production-quality db schema designer output quickly
|
||
|
|
|
||
|
|
## Instructions
|
||
|
|
|
||
|
|
When this skill is active, Claude will:
|
||
|
|
|
||
|
|
1. Understand the full context of your db schema designer request
|
||
|
|
2. Apply best practices and conventions for Development
|
||
|
|
3. Produce clean, well-structured, production-ready output
|
||
|
|
4. Explain key decisions and offer alternatives where relevant
|
||
|
|
|
||
|
|
## Examples
|
||
|
|
|
||
|
|
### Example 1 — Basic Usage
|
||
|
|
|
||
|
|
**User:** Help me get started with db schema designer.
|
||
|
|
|
||
|
|
**Claude:** I'll walk you through the essential steps for db schema designer in your context...
|
||
|
|
|
||
|
|
### Example 2 — Advanced Usage
|
||
|
|
|
||
|
|
**User:** I need a production-ready db schema designer setup with full error handling.
|
||
|
|
|
||
|
|
**Claude:** Here's a complete, production-hardened db schema designer implementation...
|
||
|
|
|
||
|
|
## Guidelines
|
||
|
|
|
||
|
|
- Always validate inputs before processing
|
||
|
|
- Follow the conventions of the target platform or language
|
||
|
|
- Prefer explicit over implicit — clarity beats cleverness
|
||
|
|
- Include comments for non-obvious logic
|
||
|
|
- Suggest tests or validation steps where appropriate
|
||
|
|
|
||
|
|
## Dependencies
|
||
|
|
|
||
|
|
Required: postgresql, mysql, sqlite
|
||
|
|
|
||
|
|
## Platforms
|
||
|
|
|
||
|
|
Available on: claude.ai, claude-code, api
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
*Part of the [claude-skills](https://github.com/inbharatai/claude-skills) collection — 183+ skills for Claude.*
|