AugmentClaude

DataModelLM

Design database schemas visually with entity-relationship diagrams and Prisma format.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/datamodellm-nimbalyst/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Create visual data models for database schemas using Nimbalyst's DataModelLM editor. Use when the user wants to design a data model, database schema, entity relationship diagram, or Prisma schema.

What this skill does

DataModelLM - Visual Data Modeling

DataModelLM is Nimbalyst's visual editor for creating database schemas using Prisma format. It displays entity-relationship diagrams with a visual canvas.

When to Use DataModelLM

  • Designing database schemas
  • Creating entity relationship diagrams (ERDs)
  • Planning data models for applications
  • Working with Prisma schemas
  • Any visual data modeling task

File Format

  • Extension: .prisma
  • Format: Prisma schema with special metadata header
  • Location: Any directory (commonly workspace root or models/, schema/)

Required Header

Every DataModelLM file MUST start with a @nimbalyst metadata comment:

// @nimbalyst {"viewport":{"x":0,"y":0,"zoom":1},"positions":{},"entityViewMode":"standard"}

Basic Structure

// @nimbalyst {"viewport":{"x":0,"y":0,"zoom":1},"positions":{},"entityViewMode":"standard"}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
  id        Int      @id @default(autoincrement())
  email     String   @unique
  name      String?
  posts     Post[]
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

model Post {
  id        Int      @id @default(autoincrement())
  title     String
  content   String?
  published Boolean  @default(false)
  author    User     @relation(fields: [authorId], references: [id])
  authorId  Int
  createdAt DateTime @default(now())
}

Supported Types

Scalar Types

  • Int, BigInt, Float, Decimal
  • String, Boolean
  • DateTime, Json, Bytes

Modifiers

  • ? - Optional field
  • [] - Array/list

Attributes

  • @id - Primary key
  • @unique - Unique constraint
  • @default(value) - Default value
  • @updatedAt - Auto-update timestamp
  • @relation - Define relationships

Relationship Patterns

One-to-Many

model User {
  posts Post[]
}
model Post {
  author   User @relation(fields: [authorId], references: [id])
  authorId Int
}

One-to-One

model User {
  profile Profile?
}
model Profile {
  user   User @relation(fields: [userId], references: [id])
  userId Int  @unique
}

Many-to-Many (Implicit)

model Post {
  categories Category[]
}
model Category {
  posts Post[]
}

Best Practices

  1. Always include the @nimbalyst header - Required for visual editor
  2. Use meaningful model names - PascalCase, singular (User not Users)
  3. Include timestamps - Add createdAt and updatedAt to most models
  4. Define explicit relations - Always specify @relation with fields and references

Related skills