database-ops

Implement async SQLModel CRUD with per-user isolation on Neon PostgreSQL.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/Jawad-Chaudhary/Hackathone-2-TODO-Spec-Driven-Development --skill database-ops-jawad-chaudhary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-ops
Source: https://github.com/Jawad-Chaudhary/Hackathone-2-TODO-Spec-Driven-Development/tree/main/Phase03/.claude/skills/database-ops
Command: npx skills add https://github.com/Jawad-Chaudhary/Hackathone-2-TODO-Spec-Driven-Development --skill database-ops-jawad-chaudhary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers building apps with SQLModel and Neon PostgreSQL face boilerplate for model definitions, migrations, and enforcing per-user data isolation, leading to slow setup and potential data leakage.

Core Features & Use Cases

  • Async SQLModel integration with Neon PostgreSQL
  • Migrations and schema evolution
  • Per-user data isolation in CRUD operations
  • Efficient indexing and query patterns for multi-tenant apps

Quick Start

Define your models with SQLModel, configure an async session, and perform per-user operations to fetch or modify data.

Frequently Asked Questions about database-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce per-user data isolation in a multi-tenant app using SQLModel and Neon PostgreSQL?

Per-user data isolation in SQLModel and Neon PostgreSQL is enforced by applying per-user filtering directly within CRUD operations. The Skill implements per-user filtering on top of an async engine setup to prevent data leakage across tenants.

How do I set up an async database engine with Neon PostgreSQL and SQLModel?

You can set up an async database engine by configuring an async session with SQLModel for Neon PostgreSQL. The Skill provides an async engine setup and ready-to-test CRUD patterns with testing fixtures.

What's the best way to handle database migrations and schema evolution in a Neon PostgreSQL backend?

Handling database migrations and schema evolution in a Neon PostgreSQL backend is best achieved by using safe migration patterns. The Skill provides migration support to safely evolve schemas while maintaining high-performance queries.

Why do I need efficient indexing for multi-tenant apps using SQLModel?

Efficient indexing for multi-tenant apps using SQLModel is needed to maintain high-performance queries across isolated per-user data. Without it, filtering operations in multi-tenant architectures experience significant performance degradation.

Does this database operations approach provide testing fixtures for async CRUD patterns?

Yes, this database operations approach provides ready-to-test CRUD patterns complete with testing fixtures. These fixtures allow you to validate asynchronous database operations and per-user filtering before deployment.