layers-domain

Map domain concepts and terminology conflicts for product modelling.

Updated Apr 8, 2026

Search Tags:#product discovery #bounded contexts #event storming #domain mapping #concept modeling #terminology audit

Ready to run

npx skills add https://github.com/codesour-design/gravity --skill layers-domain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: layers-domain
Source: https://github.com/codesour-design/gravity/tree/main/.agents/skills/layers-domain
Command: npx skills add https://github.com/codesour-design/gravity --skill layers-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams understand complex domains by capturing real-world concepts, conflicting terminology, and natural boundaries before making product or system design decisions.

Core Features & Use Cases

Domain Concept Mapping: Builds concept maps, identifies relationships, and captures the vocabulary people use in a domain.
Terminology Analysis: Documents synonyms, conflicting meanings, and bounded contexts without prematurely resolving differences.
Use Case: A product team entering a complex industry can use this Skill to harvest domain nouns, uncover stakeholder language differences, and prepare a foundation for conceptual modelling.

Quick Start

Tell the layers-domain skill what domain you want to map and provide the known roles, concepts, and workflows to begin a structured domain analysis session.

Frequently Asked Questions about layers-domain

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

FAQPage Schema

What is domain concept mapping and how does it help with product discovery?▼

Domain concept mapping captures real-world concepts, relationships, and stakeholder vocabulary to build a raw conceptual foundation for product modelling. It helps teams understand complex domains and uncover terminology conflicts before making system design decisions.

How do I identify bounded contexts from expert interviews and workflow analysis?▼

You identify bounded contexts by applying structured methods like noun harvesting and event storming to synthesize expert interviews. This process documents synonyms and conflicting meanings to find natural domain boundaries without prematurely resolving differences.

When do I need a terminology audit for domain mapping?▼

A terminology audit is needed when a product team enters a complex industry and encounters stakeholder language differences. It documents synonyms and conflicting meanings to prepare a foundation for conceptual modelling without prematurely designing solutions.

What's the best way to uncover terminology gaps in complex domains?▼

The best way to uncover terminology gaps is through structured domain analysis sessions that harvest domain nouns and document conflicting stakeholder language. This maps real-world concepts to identify where terminology conflicts exist before product modelling.

Why should I not prematurely resolve terminology conflicts during domain mapping?▼

You should not prematurely resolve terminology conflicts because documenting synonyms and conflicting meanings within their bounded contexts preserves the raw conceptual foundation. Premature resolution risks designing solutions before fully understanding the real-world domain.