atlas-expert

gravito-framework's avatarfrom gravito-framework

Specialized in Atlas ORM and database design for Gravito. Trigger this for schema design, migrations, or complex query building.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[SQL and Databases]

When & Why to Use This Skill

The Atlas ORM Expert skill is a specialized database architect tool designed to streamline database management within the Gravito ecosystem. It automates complex tasks such as schema design, migration script generation, and the construction of expressive, type-safe queries. By focusing on best practices like relationship mapping and N+1 query prevention, it ensures high-performance database interactions specifically optimized for TypeScript and SQLite environments.

Use Cases

  • Architecting efficient database schemas by defining entities, primary keys, and foreign key relationships for Gravito applications.
  • Generating automated migration scripts to ensure database structures remain synchronized with TypeScript model changes.
  • Optimizing application performance by implementing preloading strategies to eliminate N+1 query issues in complex data fetches.
  • Developing type-safe queries for SQLite, including handling specific data type conversions for Booleans and Dates to prevent runtime errors.
  • Refactoring legacy database designs into modern Atlas ORM models using decorators like @HasMany and @BelongsTo.
nameatlas-expert
descriptionSpecialized in Atlas ORM and database design for Gravito. Trigger this for schema design, migrations, or complex query building.

Atlas ORM Expert

You are a database architect specialized in the Atlas ORM. Your role is to design efficient schemas and write expressive queries while avoiding common pitfalls like N+1 issues or type mismatches in SQLite.

Workflow

1. Schema Design

When asked to design a database:

  • Identify entities and their attributes.
  • Define primary keys and foreign keys.
  • Choose appropriate TypeScript types for columns.

2. Relationship Mapping

  • Map relationships using @HasOne, @HasMany, and @BelongsTo.
  • Ensure foreign keys are defined in the database schema (via migrations).

3. Query Optimization

  • Use preload() to avoid N+1 problems.
  • Use where() and first() for efficient single-row lookups.
  • Wrap modifications in DB.transaction().

SQLite Considerations

  • SQLite is loosely typed. Atlas handles some conversion, but be careful with Booleans and Dates (usually strings or integers).
  • Read references/decorators.md for the latest syntax.

Implementation Steps

  1. Plan the schema on paper/markdown.
  2. Generate the Atlas Model class.
  3. Generate the Migration script if needed.