skills.rest
LowyShin
LowyShinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

phase-1-schema

Define project terminology, entities, and relationships into a shared glossary and domain model.

33|5|Updated Jan 27, 2026
Search Tags:#schema#glossary#entity#terminology#data-structure#relationship#domain-model
One-click install
npx skills add https://github.com/LowyShin/giip-dev-agent --skill phase-1-schema-lowyshin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phase-1-schema
Source: https://github.com/LowyShin/giip-dev-agent/tree/main/.agent/skills/phase-1-schema
Command: npx skills add https://github.com/LowyShin/giip-dev-agent --skill phase-1-schema-lowyshin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes project terminology and data structures by creating a shared glossary, defining core entities, and mapping relationships to prevent miscommunication and rework.

Core Features & Use Cases

  • Build a glossary that covers terminology, domain entities, and relationships to align teams.
  • Define a scalable domain model and core data schema for new projects.
  • Use in project initialization to ensure consistent language and data structures across teams.

Quick Start

Define the core terms and relationships for your project to create a shared glossary and initial domain-model draft.

Frequently Asked Questions about phase-1-schema

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

FAQPage Schema
Why do I need to standardize project terminology and domain models before development?▼

Standardizing project terminology prevents miscommunication and rework by creating a shared glossary, defining core entities, and mapping relationships to ensure consistent language and data structures across teams.

How do I build a scalable domain model and data schema for a new project?▼

Build a scalable domain model by defining core terms, identifying domain entities, and mapping their relationships to create an initial glossary and data schema draft that aligns your team.

Can I use this approach to establish a glossary for cross-domain entity mapping?▼

Yes, you can establish a glossary for cross-domain entity mapping by identifying core entities and mapping their relationships to align teams and prevent miscommunication across different domains.

What's the best way to identify core entities and map relationships during project initialization?▼

The best way to identify core entities and map relationships during project initialization is to define consistent terminology and data structures, creating a shared glossary and initial domain-model draft.

Does domain modeling like this work for satisfying PDCA planning requirements?▼

Yes, domain modeling works for PDCA planning by satisfying the planning phase through glossary design, initial entity identification, and relationship mapping to establish consistent data structures.

Related Skills

Explore More Software Engineering Skills→
nikbrunnernikbrunner

dev-util-glossary

Extract and formalize domain terminology from conversations into GLOSSARY.md.

Community
Intermediate
omanjayaomanjaya

database-performance

Identify and implement database performance optimizations for queries, schemas, and caching.

Community
Advanced
sylin-orgsylin-org
4

koan-data-modeling

Define aggregate-first domain models with lifecycle hooks and value objects in Koan Framework.

Official
Intermediate
darelabs-techdarelabs-tech

dare-reverse

Generate documentation, flowcharts, and domain models from DARE CLI reverse-engineering artifacts.

Official
Advanced