erd-studio CLAUDE.md

Project instructions for ERD Studio, an editor for organizing data-model files in a project. ERD means entity–relationship diagram, a way to describe data and how tables relate.

In plain words
What is it for?
Use them when modifying ERD Studio’s files, commands, directory structure, or support for its older command names.
Why use it?
They define the file locations, naming rules, settings, and compatibility aliases needed to work on the extension safely.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/liam-machine/erd-studio/claude-md
Clone the repo
git clone --depth 1 https://github.com/liam-machine/erd-studio
Per session 4,137 This file is loaded in full into every session.
When invoked 4,137 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.04137 $0.04137
Opus 5 $0.02069 $0.02069
Sonnet 5 $0.00827 $0.00827
Haiku 4.5 $0.00414 $0.00414

Measured 2d ago against content hash b0b990e9ceb1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

erd-studio CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 315 lines

How it starts

The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Naming

The extension display name is ERD Studio (package name erd-studio).

Directory Structure

ERD domain files live at {project_root}/.erd-studio/{layer}/{domain}.json. Each file is a unified domain containing the logical stage data. The custom editor activates for files matching:

  • **/.erd-studio/*/*.json

The base directory is configurable via the erdStudio.semanticDir setting (default: .erd-studio).

.erd-studio/
├── layers.json
├── templates/
├── silver/
│   ├── customer-360.json   ← domain file (logical stage)
│   └── orders.json
└── gold/
    └── reporting.json

Internal Identifiers

All internal identifiers use the erdStudio prefix (erd-studio for the activity bar container id), with the command palette category "ERD Studio". The extension was originally published with a dbtSemantic prefix; two compatibility shims keep pre-rename users working and must not be removed:

  • Legacy command aliases: every erdStudio.* command is also registered in code as dbtSemantic.* (see LEGACY_ALIASED_COMMANDS at the end of activate() in src/extension.ts) so old keybindings keep working. These are code-only registrations — never contribute them in package.json.
  • Legacy setting fallback: settings are read via getErdStudioSetting() (src/services/configService.ts), which prefers explicit erdStudio.* values and falls back to explicit dbtSemantic.* values. The deprecated dbtSemantic.projectPath / dbtSemantic.semanticDir entries in package.json carry markdownDeprecationMessage and must stay contributed. Never read settings with getConfiguration('erdStudio').get(...) directly — always use the helper.

Build & Test Commands

npm run build          # Build both extension + webview bundles (esbuild)
npm run watch          # Watch mode — rebuilds on change
npm run compile        # Type-check only (both tsconfigs, no emit)
npm run test           # Run unit tests (vitest)
npm run test:watch     # Run tests in watch mode
npm run package        # Production build (minified, no sourcemaps)

Read the full file on GitHub · 315 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 315 lines · 4,137 tokens per session scan A b0b990e9ceb1

Subscribe to this mod's changes

erd-studio CLAUDE.md is an instructions file published in the GitHub repository liam-machine/erd-studio (5 stars, last pushed 2mo ago), licensed MIT. It adds 4,137 tokens to every session, about $0.0207 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.