typescript-bun-drizzle-quality

Analyze Bun fullstack TypeScript projects with Drizzle SQL for type safety and boundaries.

1|Updated Apr 1, 2026

Search Tags:#typescript #drizzle #orm #code-quality #bun #fullstack #type-safety

Ready to run

npx skills add https://github.com/izadoesdev/toolbase --skill typescript-bun-drizzle-quality-izadoesdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: typescript-bun-drizzle-quality
Source: https://github.com/izadoesdev/toolbase/tree/main/.agents/skills/bun-fullstack
Command: npx skills add https://github.com/izadoesdev/toolbase --skill typescript-bun-drizzle-quality-izadoesdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure their Bun-based fullstack TypeScript projects using Drizzle-backed SQL meet production quality standards, including strong type safety, clear API-domain-persistence boundaries, and predictable data changes.

Core Features & Use Cases

App/API logic track for changing handlers, services, and contracts while keeping domain rules consistent with persistence.
Data layer and migration track for Drizzle schemas, migrations, indexes, and query shapes with safe rollback paths.
Fullstack integration track for cross-boundary changes that touch API contracts, domain rules, and database effects.

Quick Start

Run the repository's Bun+Drizzle quality checks to begin.

Frequently Asked Questions about typescript-bun-drizzle-quality

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

FAQPage Schema

How do I ensure type safety in a Bun fullstack project using Drizzle ORM?▼

Ensure type safety in a Bun fullstack project by analyzing Drizzle SQL schemas, codifying runtime assumptions, and enforcing validation contracts with Zod across API, domain, and persistence boundaries.

What's the best way to manage Drizzle migrations safely in a production TypeScript app?▼

Manage Drizzle migrations safely by enforcing repository constraints, verifying query shapes, and applying migration safety practices with safe rollback paths to guarantee deterministic data changes.

Can I use this to enforce clear boundaries between API logic and database persistence?▼

Yes, you can enforce clear API-domain-persistence boundaries by analyzing handlers, services, and contracts to keep domain rules consistent with Drizzle-backed SQL persistence effects.

How do I validate runtime assumptions and contracts in a Bun and Drizzle codebase?▼

Validate runtime assumptions and contracts in a Bun and Drizzle codebase by codifying them through Zod validation, enforcing repository constraints, and applying deterministic testing guidance.

Does this approach work for fullstack changes that touch both API contracts and database schemas?▼

Yes, it handles fullstack integration by analyzing cross-boundary changes that intersect API contracts, domain rules, and Drizzle database effects to maintain production quality.

Why do my Drizzle schema migrations cause unpredictable data changes in production?▼

Drizzle schema migrations cause unpredictable data changes when repository constraints and validation contracts are missing, requiring codified runtime assumptions and migration safety practices to ensure deterministic outcomes.

Nick777-Pixel