persistence-analyst

Audit database schemas, Drizzle ORM models, and persistence patterns.

Updated Feb 22, 2026

Search Tags:#database #schema #domain-driven design #auditing #drizzle orm #persistence

Ready to run

npx skills add https://github.com/Muath2000/TradeStation --skill persistence-analyst

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: persistence-analyst
Source: https://github.com/Muath2000/TradeStation/tree/main/.claude/skills/persistence-analyst
Command: npx skills add https://github.com/Muath2000/TradeStation --skill persistence-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and examples (resource) components.

What problem does it solve?

This Skill ensures the integrity, performance, and maintainability of your application's data layer by thoroughly auditing database schemas, ORM models, and persistence patterns.

Core Features & Use Cases

Schema Auditing: Validates table designs, column types, indexes, and constraints against best practices.
ORM Model Review: Audits Drizzle ORM models, ensuring they accurately reflect the domain.
Pattern Enforcement: Verifies implementation of patterns like repository, outbox, and soft-delete.
Use Case: Before deploying a new microservice, use this Skill to generate a comprehensive report on its database schema, migration history, and adherence to domain-driven design principles, ensuring production readiness.

Quick Start

Analyze the persistence layer for the identity-svc service, focusing on its Drizzle ORM schema and repository implementations.

Frequently Asked Questions about persistence-analyst

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

FAQPage Schema

How do I audit database schema design and Drizzle ORM models for best practices?▼

To audit database schema design and Drizzle ORM models, you can trigger an analysis that validates table designs, column types, indexes, and constraints. It generates a comprehensive report ensuring your schema accurately reflects the domain and adheres to best practices.

What is the outbox pattern and how does it relate to transaction boundaries in domain-driven design?▼

The outbox pattern ensures reliable event publishing within transaction boundaries in domain-driven design. Auditing verifies its implementation alongside aggregate roots and state machines to maintain data integrity and consistent state transitions across your persistence layer.

How do I check if my repository pattern and multi-tenant isolation strategies are correctly implemented?▼

Checking repository pattern and multi-tenant isolation implementations involves auditing your persistence layer to verify transaction boundaries and data segregation. This process ensures state machines and soft-delete strategies are consistently enforced across tenant data.

Can I review migration history and query performance for a microservice before deployment?▼

Yes, you can review migration history and query performance for a microservice before deployment. The analysis audits your database schema and Drizzle ORM models to ensure production readiness, verifying domain models and persistence patterns.

When do I need to generate a persistence model for domain-driven design?▼

You need to generate a persistence model for domain-driven design when validating ORM models against domain models, aggregate roots, and transaction boundaries. It ensures your database schema, soft-delete strategy, and multi-tenant isolation maintain application data layer integrity.