<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Domain Modeling on Top AI Skills</title><link>https://topaiskills.com/tags/domain-modeling/</link><description>Recent content in Domain Modeling on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 18 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/domain-modeling/index.xml" rel="self" type="application/rss+xml"/><item><title>Domain Modeling With AI: Build a CONTEXT.md Glossary</title><link>https://topaiskills.com/tutorials/guides/domain-modeling-procedural-guide/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/domain-modeling-procedural-guide/</guid><description>&lt;p&gt;Your AI keeps calling everything an &amp;ldquo;account&amp;rdquo; while your codebase has Customer, User, and Subscription scattered across three modules. Fixing that mismatch is what domain modeling is for: pin down one canonical term, list the rejected synonyms, and record the decisions that were genuinely hard to reverse. I ran Matt Pocock&amp;rsquo;s domain-modeling skill (412.8K installs, All-Time #65 on skills.sh) against a real repo and read its format files line by line — the skill looks trivial at first glance, but the bar it sets for writing anything down is the part worth copying even without the skill installed. This guide walks the full procedure: when the skill engages, the five moves it makes during a session, and the exact format rules for &lt;code&gt;CONTEXT.md&lt;/code&gt; and ADRs.&lt;/p&gt;</description></item></channel></rss>