AI SummaryVespertide enables developers to define database schemas declaratively in JSON and automatically generate typed migrations and SQL for Vespertide-based projects. Teams building data-driven applications benefit from schema validation, type safety, and streamlined database model management.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "vespertide" skill in my project. Please run this command in my terminal: # Install skill into the correct directory (2 files) mkdir -p .claude/skills/vespertide && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/vespertide/SKILL.md "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/data-ai/vespertide/SKILL.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/vespertide/metadata.json "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/data-ai/vespertide/metadata.json" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Define database schemas in JSON and generate migration plans. Use this skill when creating or modifying database models, defining tables with columns, constraints, and ENUM types for Vespertide-based projects.
Vespertide Database Schema Definition
Declarative database schema management. Define tables in JSON, generate typed migrations and SQL. > CRITICAL: Always validate your model against the JSON Schema before committing. > Use $schema in every model file for IDE validation.
Schema Validation (MANDATORY)
Every model file MUST include the $schema field: `json { "$schema": "https://raw.githubusercontent.com/dev-five-git/vespertide/refs/heads/main/schemas/model.schema.json", "name": "table_name", "columns": [] } ` Before saving any model: • Ensure $schema URL is present • Verify IDE shows no validation errors • Run vespertide diff to check for parsing errors The schema URL provides: • Real-time validation in VS Code, WebStorm, etc. • Autocompletion for all fields • Type checking for column types and constraints ---
Post-Edit Validation (MANDATORY)
After EVERY edit to a model file, ALWAYS run these checks: `bash
2. Preview generated SQL to verify correctness
vespertide sql ` Verify the output: • vespertide diff shows expected changes (no unexpected additions/removals) • vespertide sql generates valid SQL for your target database • IDE shows no red squiggles (schema validation errors) • All required fields (name, type, nullable) are present Only proceed to vespertide revision after verification passes. ---
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster