platform-database
SQL database design, query optimization, and migration safety. Use when writing queries, designing schemas, or planning database migrations.
Best use case
platform-database is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
SQL database design, query optimization, and migration safety. Use when writing queries, designing schemas, or planning database migrations.
Teams using platform-database should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/platform-database/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How platform-database Compares
| Feature / Agent | platform-database | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
SQL database design, query optimization, and migration safety. Use when writing queries, designing schemas, or planning database migrations.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Principles - Prefer UNION ALL over UNION unless you specifically need deduplication # Rules See [rules index](rules/_sections.md) for detailed patterns. ## Examples ### Positive Trigger User: "Review this schema and migration plan for zero-downtime rollout." Expected behavior: Use `platform-database` guidance, follow its workflow, and return actionable output. ### Non-Trigger User: "Implement ARIA labels and focus rings on this modal." Expected behavior: Do not prioritize `platform-database`; choose a more relevant skill or proceed without it. ## Troubleshooting ### Skill Does Not Trigger - Error: The skill is not selected when expected. - Cause: Request wording does not clearly match the description trigger conditions. - Solution: Rephrase with explicit domain/task keywords from the description and retry. ### Guidance Conflicts With Another Skill - Error: Instructions from multiple skills conflict in one task. - Cause: Overlapping scope across loaded skills. - Solution: State which skill is authoritative for the current step and apply that workflow first. ### Output Is Too Generic - Error: Result lacks concrete, actionable detail. - Cause: Task input omitted context, constraints, or target format. - Solution: Add specific constraints (environment, scope, format, success criteria) and rerun. ## Workflow 1. Identify whether the request clearly matches `platform-database` scope and triggers. 2. Apply the skill rules and referenced guidance to produce a concrete result. 3. Validate output quality against constraints; if gaps remain, refine once with explicit assumptions.