Erd

Skill KhaiTrang1995/agentic-awesome-kits/packages/agentic-awesome-kits/payload/kits/software/drawio-kit/.claude/skills/erd

A universal collection of reusable Loop Engineering kits for AI coding agents—not just prompts. Each kit combines Skills, Rules, Templates, workflows, and validation loops to help agents autonomously plan, execute, verify, fix, and improve engineering tasks.

Install

npx -y skills add KhaiTrang1995/agentic-awesome-kits --skill erd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate ERD .drawio — entities, attributes, 1-1/1-N/N-N relationships, PK/FK. Hand-authored XML with TechSphereX AI palette; complex SQL DDL → /diagram --from-sql.

SKILL.md

2.3 KB, as published. Nobody here has run it

/erd — Entity-Relationship Diagram (draw.io)

When to use

Data model for design docs / BA–dev alignment
A few–dozens of entities described in words (no SQL importer needed)
Need a hand-editable .drawio file

Switch to /diagram when: large SQL DDL file (sqlerd.py), auto-layout for dozens of tables, or batch PNG export.

Input examples

/erd Order 1-N OrderLine, Order N-1 Customer, Order 1-1 Payment --feature booking
/erd auth module: User, Role, UserRole (N-N), Permission
/erd @schema.sql   → suggest /diagram --from-sql if >8 tables

Workflow

Phase 1 — Inventory

List:

Entity	PK	Attributes (short)	Notes

Relationships: A 1—N B, A N—N B (// associative entity if needed).

Missing relationship names / cardinality → ask 1–2 questions; do not invent FKs.

Phase 2 — L3 layout preview

Node + edge table (ASCII/table). User reviews before XML.

Phase 3 — Generate XML

Use @_templates/erd.drawio as the frame:

Entity = rounded rect (or swimlane-style header): bold entity name + attr list
Mark PK as PK; FK as FK (text only)
Edge: endArrow=ERoneToMany / ERmandOne / ERzeroToMany when appropriate; fallback endArrow=block + labels 1 / N on the edge
Palette: entity fill #dae8fc, associative #fff2cc, external ref #f5f5f5 (per conventions)
Grid 20; entity box ~200×(40 + 20×attr count)

Phase 4 — L1 → Write

docs/diagrams/{feature}/erd-{slug}.drawio

Mandatory rules

@.claude/rules/drawio-conventions.md (core shapes, escape XML)
@.claude/rules/naming-conventions.md
@.claude/rules/approval-gate.md
Do not invent columns/relationships; TBD + ask
≤ 15 entities per page — more: split by domain or use /diagram + sqlerd/autolayout

Output