Data Mesh And Domain Oriented Design

Community

vaquarkhan

data-mesh-and-domain-oriented-design

Guides agents through domain-oriented data product and data mesh design. Use when organizing ownership, domain boundaries, federated governance, and shared platform responsibilities across multiple teams.

Overview

Publisher	vaquarkhan
Repository	`data-engineering-agent-skills`
Skill name	`data-mesh-and-domain-oriented-design`
Stars	60
Forks	8
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by vaquarkhan on GitHub. Read the source before you install it.

Installation

Install the Data Mesh And Domain Oriented Design AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/data-mesh-and-domain-oriented-design
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/data-mesh-and-domain-oriented-design

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skills.git /tmp/data-engineering-agent-skills
mkdir -p .claude/skills
cp -r /tmp/data-engineering-agent-skills/skills/data-mesh-and-domain-oriented-design .claude/skills/data-mesh-and-domain-oriented-design

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Data Mesh And Domain Oriented Design in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Data Mesh And Domain Oriented Design on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Data Mesh And Domain Oriented Design is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Data Mesh And Domain-Oriented Design

Overview

Use this skill when the problem is organizational scale as much as technical scale. It helps agents design domain-owned data products with explicit boundaries, interoperable contracts, and platform guardrails that do not collapse back into central bottlenecks.

When to Use

designing domain-oriented data products
defining ownership boundaries across multiple teams
introducing or refining a data mesh operating model
clarifying platform versus domain responsibilities
reducing central-team bottlenecks in large data organizations

Do not use this to rename ordinary pipelines as "data products" without ownership, contracts, or service expectations.

Workflow

Identify domains and business boundaries. Clarify:
- which team owns the source behavior
- which team owns publish-ready data
- where cross-domain dependencies exist
Define data products, not just datasets. A data product should include:
- owner
- contract
- consumers
- freshness expectations
- support and change path
Separate domain ownership from platform ownership. Platform teams should provide capabilities, standards, and guardrails rather than own every dataset.
Define federated governance rules. Include:
- minimum contract rules
- lineage requirements
- discoverability
- security and privacy baselines
Check whether mesh adds real value. Not every small team or simple platform needs full mesh operating complexity.

Common Rationalizations

Rationalization	Reality
"We can call every table a data product."	Without ownership and service expectations, it is just a dataset with better branding.
"Data mesh means no central standards."	Federated governance still needs common interoperability rules.
"Each domain can optimize however it wants."	Unbounded local choices make shared discovery, trust, and reuse much worse.

Red Flags

data products have no named owner
domain boundaries are driven only by org chart convenience
the platform team still owns operational details for every domain pipeline
governance standards are implied but not codified

Verification

Domain boundaries and ownership are explicit
Data products have contracts, consumers, and support expectations
Platform versus domain responsibilities are clearly separated
Federated governance rules exist for interoperability and trust

Frequently asked questions

What does the Data Mesh And Domain Oriented Design AI skill do?

Why use Data Mesh And Domain Oriented Design on TypingMind?

Because you install it once and use it with any model. Data Mesh And Domain Oriented Design is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Data Mesh And Domain Oriented Design in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/data-mesh-and-domain-oriented-design. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Data Mesh And Domain Oriented Design?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Data Mesh And Domain Oriented Design?

As many as you like. As long as a model supports skills, you can use Data Mesh And Domain Oriented Design with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Data Mesh And Domain Oriented Design AI skill free?

Yes. It is published on GitHub by vaquarkhan under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Sketch

NousResearch

OrganizationPopular

Throwaway HTML mockups: 2-3 design variants to compare.

Tldraw Offline

Drive and script tldraw offline canvases with an agent.

Brand Guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Data Mesh And Domain-Oriented Design

Overview

When to Use

Workflow

Common Rationalizations

Red Flags

Verification

Frequently asked questions

Related AI Skills

Set up your own AI workspace now