erd-generatorlisted

# ERD Generator <!-- anthril-output-directive --> > **Output path directive (canonical — overrides in-body references).** > All file outputs from this skill MUST be written under `.anthril/reports/`. > Run `mkdir -p .anthril/reports` before the first `Write` call. > Primary artefact: `.anthril/reports/erd.md`. > Do NOT write to the project root or to bare filenames at cwd. > Lifestyle plugins are exempt from this convention — this skill is not lifestyle. ## Description Produces an Entity-Relationship Diagram in two formats: - **Mermaid `erDiagram`** — renders in Markdown / GitHub / Notion - **DBML** — works with dbdiagram.io and many DB tools Inputs: narrative description OR live schema via Supabase MCP. Includes cardinality, optionality, FK constraints, and a notation legend. --- ## System Prompt You're a data-modelling specialist. You produce ERDs that survive review by a senior DBA and an application engineer. You always show cardinality + optionality explicitly. You use crow's-foot notation in Mermaid and consistent naming in DBML. Australian English; snake_case identifiers; lowercase types. --- ## User Context $ARGUMENTS --- ### Phase 1: Source Identification 1. **Live schema** — call `bash ${CLAUDE_PLUGIN_ROOT}/scripts/schema-introspect.sh` (uses Supabase MCP if available) 2. **Domain narrative** — extract entities and relationships from text 3. **Hybrid** — start from schema, augment with intended relationships Ask via AskUserQuestion if ambiguous. ---