kentoshimizu/sw-agent-skills/db-conceptual-modeling

Claude Code and agent skill by kentoshimizu/sw-agent-skills

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Conceptual data modeling workflow for domain entities, relationships, and lifecycle boundaries. Use when teams must align on domain meaning before logical/physical schema decisions; do not use for index-only or migration-only tasks.

Install

npx vskill@latest install kentoshimizu/sw-agent-skills/db-conceptual-modeling

SKILL.md

The same SKILL.md was published earlier as kentoshimizu/sw-agent-skills/db-conceptual-modeling.

DB Conceptual Modeling

Overview

Use this skill to model domain meaning first, so later schema decisions reflect business semantics rather than accidental implementation details.

Scope Boundaries

  • Teams disagree on entity meaning or relationship semantics.
  • A new domain area is being introduced.
  • Existing schema complexity suggests conceptual drift.

Core Judgments

  • Entity versus value concept boundaries.
  • Cardinality and ownership semantics of relationships.
  • Lifecycle states and temporal meaning.
  • Bounded-context boundaries and shared concepts.

Practitioner Heuristics

  • Model business invariants explicitly before table design.
  • Use language from domain experts, not only engineering jargon.
  • Treat temporal facts (history, validity windows) as first-class concepts.
  • Avoid polymorphic catch-all concepts that hide domain distinctions.

Workflow

  1. Identify core concepts, actors, and business events.
  2. Define entity relationships with ownership and lifecycle semantics.
  3. Capture key invariants and conflict rules.
  4. Resolve term collisions across bounded contexts.
  5. Document conceptual assumptions that drive downstream logical design.

Common Failure Modes

  • Conceptual model mirrors current tables instead of domain reality.
  • Relationship ownership is left implicit, causing write conflicts later.
  • State transitions are not modeled, forcing ad hoc status flags.

Failure Conditions

  • Stop when core terms remain ambiguous across stakeholders.
  • Stop when invariants cannot be expressed at conceptual level.
  • Escalate when bounded context boundaries are politically unresolved.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
5
7-day trend score
9

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 12 May 2026, 6 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/kentoshimizu/sw-agent-skills/db-conceptual-modeling/badge)](https://verified-skill.com/skills/kentoshimizu/sw-agent-skills/db-conceptual-modeling)

Something wrong with this skill or its page? Tell us.