One-click install
npx skills add https://github.com/kcc989/logoer --skill minimal-modeling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minimal-modeling
Source: https://github.com/kcc989/logoer/tree/main/.claude/skills/minimal-modeling
Command: npx skills add https://github.com/kcc989/logoer --skill minimal-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Minimal Modeling provides a disciplined approach to design database schemas by separating business concepts from technical implementation, reducing cognitive load and aligning data structures with business needs.

Core Features & Use Cases

  • Two-Phase Process: Phase A focuses on logical modeling (anchors, attributes, links); Phase B translates the model into a physical SQL schema.
  • Stakeholder Validation: Enables non-technical stakeholders to validate concepts before implementation.
  • Deliverables: Logical model with identified anchors, attributes, and relationships plus a draft physical schema (table names, keys, and constraints).

Quick Start

Provide a brief business-domain description, then identify anchors, attributes, and links to build a complete logical model, and finally derive a physical schema with pluralized table names and keys.

Frequently Asked Questions about minimal-modeling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate vague business requirements into a database schema?

To translate vague business requirements into a database schema, use a two-phase process: first build a logical model identifying anchors, attributes, and links, then map them to a physical SQL schema with tables and keys.

What is the best way to design a logical data model for non-technical stakeholders?

The best way to design a logical data model for non-technical stakeholders is to separate business concepts from technical implementation, focusing on anchors and attributes to enable stakeholder validation before writing SQL.

How do you map a logical model to a physical SQL schema?

You map a logical model to a physical SQL schema by translating identified anchors into pluralized table names, defining primary keys, and applying constraints to finalize the database structure.

Can I validate database designs with stakeholders before writing SQL?

Yes, you can validate database designs with stakeholders before writing SQL by using Phase A logical modeling to review business concepts, ensuring alignment with business needs prior to physical schema implementation.

What are the limitations of separating logical modeling from physical schema design?

A limitation of separating logical modeling from physical schema design is that it requires strict discipline to maintain alignment; anchors and attributes must be manually mapped to tables and constraints, increasing design overhead.

Do I need prior database knowledge to use a two-phase schema design approach?

No, non-technical stakeholders do not need prior database knowledge for Phase A logical modeling, but technical knowledge is required for Phase B to generate physical SQL schemas with constraints and keys.