database
@BA-CalderonMorales/database
Skill: Database Architecture: **Name**: database
Installation
$skills install @BA-CalderonMorales/database
Claude Code
Cursor
Copilot
Codex
Antigravity
Details
RepositoryBA-CalderonMorales/terminal-jarvis
Path.github/skills/database/SKILL.md
Branchmain
Scoped Name@BA-CalderonMorales/database
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
Skill: Database Architecture
Name: database Description: Schema-driven database patterns with QueryBuilder Trigger: Database operations, schema changes, migrations, queries
Objective
All database operations use schema.rs and QueryBuilder - NO hardcoded SQL strings.
Architecture Overview
src/db/
schema.rs # Single source of truth for table/column definitions
query_builder.rs # Fluent API for SQL construction
repository.rs # Base repository pattern
migrations.rs # Version-controlled schema changes (uses QueryBuilder)
*_repository.rs # Entity-specific data access
Core Rules
- Schema is Truth: All table/column definitions in
schema.rs - QueryBuilder for Queries: Never write raw SQL strings
- Repository Pattern: Each entity has its own repository
- Migrations via Schema: Use
table.create_table_sql(), never hardcode DDL
Correct Patterns
// GOOD: Using QueryBuilder
let sql = QueryBuilder::select(&TOOLS_TABLE)
.columns(&["id", "display_name"])
.where_eq("enabled")
.order_by("display_name", true)
.build();
// GOOD: Schema-driven DDL
let ddl = TOOLS_TABLE.create_table_sql();
Anti-Patterns to Avoid
// BAD: Hardcoded SQL
db.execute("SELECT * FROM tools WHERE id = ?", [id]).await?;
// BAD: Hardcoded DDL
db.execute("CREATE TABLE tools (id TEXT PRIMARY KEY)", ()).await?;
// BAD: SQL in migrations
db.execute("INSERT INTO schema_migrations...", params).await?;
Why This Matters
- Single point of maintenance for schema
- Compile-time verification of column names
- Consistent query patterns across codebase
- Easier migrations and schema evolution