modscape 2.0.1 → 2.0.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "modscape",
-  "version": "2.0.1",
+  "version": "2.0.2",
   "description": "Modscape: A YAML-driven data modeling visualizer CLI",
   "repository": {
     "type": "git",

package/src/templates/claude/modeling.md

@@ -1,7 +1,7 @@
 Start an interactive data modeling session.
 
 ## Instructions
-1. FIRST, read `.modscape/rules.md` to understand the project strategy, naming conventions, and YAML schema.
+1. FIRST, read `.modscape/rules.md` to understand the project strategy, naming conventions, and YAML schema. If `.modscape/rules.custom.md` exists, read it too — custom rules take priority over the base rules.
 2. SECOND, analyze the existing `model.yaml` if it exists.
 3. Listen to the user's requirements and propose/apply changes to `model.yaml` strictly following the rules.
 

package/src/templates/codex/modscape-modeling/SKILL.md

@@ -9,7 +9,7 @@ You are a professional Data Modeler. Your primary directive is to manage `model.
 
 ## COMMAND: /modscape:modeling
 When the user issues this command:
-1. READ `.modscape/rules.md` to understand project strategy and conventions.
+1. READ `.modscape/rules.md` to understand project strategy and conventions. If `.modscape/rules.custom.md` exists, read it too — custom rules take priority over the base rules.
 2. ANALYZE `model.yaml` (if present).
 3. INTERACT with the user to gather requirements and update the model strictly following the rules.
 
@@ -17,7 +17,7 @@ When the user issues this command:
 - **Appearance**: When creating new tables, include the `appearance` block with an appropriate `type`.
 - **Layout**: For any new entity, assign logical `x` and `y` coordinates in the `layout` section to prevent overlapping and ensure a clean initial visualization.
 
-ALWAYS follow the rules defined in `.modscape/rules.md` for any modeling tasks.
+ALWAYS follow the rules defined in `.modscape/rules.md` (and `.modscape/rules.custom.md` if present) for any modeling tasks.
 
 ## COMMAND: /modscape:codegen
 When the user issues this command:

package/src/templates/gemini/modscape-modeling/SKILL.md

@@ -7,7 +7,7 @@ description: Create the data model defined in `model.yaml` according to project
 
 You are a professional Data Modeler. Your primary directive is to manage `model.yaml`.
 
-BEFORE making any suggestions or changes, you MUST read and strictly follow the rules defined in `.modscape/rules.md`.
+BEFORE making any suggestions or changes, you MUST read and strictly follow the rules defined in `.modscape/rules.md`. If `.modscape/rules.custom.md` exists, read it too — custom rules take priority over the base rules.
 
 If a requested change violates these rules, warn the user.
 
@@ -24,4 +24,4 @@ If a requested change violates these rules, warn the user.
 ## Interactive Modeling
 When the user wants to perform modeling tasks, ensure you are utilizing the strategy and conventions defined in the project rules.
 
-ALWAYS follow the rules defined in `.modscape/rules.md` for any modeling tasks.
+ALWAYS follow the rules defined in `.modscape/rules.md` (and `.modscape/rules.custom.md` if present) for any modeling tasks.

package/src/templates/rules.md

@@ -3,6 +3,9 @@
 > **Purpose**: This file teaches AI agents how to write valid `model.yaml` files for Modscape.
 > Read this file completely before generating or editing any YAML.
 
+> **Extension**: If `.modscape/rules.custom.md` exists in this project, read it **in addition** to this file.
+> Rules in `rules.custom.md` take **priority** over this file when they conflict.
+
 ---
 
 ## QUICK REFERENCE (read this first)
@@ -589,7 +592,41 @@ modscape merge ./sales ./marketing -o combined.yaml
 
 ---
 
-## 13. Complete Example
+## 13. Project-Specific Rule Extensions
+
+A project MAY place a `.modscape/rules.custom.md` file to define rules that extend or override this base file.
+
+**How to use it:**
+
+- Create `.modscape/rules.custom.md` in the project root (alongside `rules.md`)
+- Write any project-specific rules, naming conventions, or overrides in Markdown
+- AI agents reading this file will also check for `rules.custom.md` and apply it
+
+**Priority:** Rules in `rules.custom.md` take priority over this file when they conflict.
+
+**What to put in `rules.custom.md`** (examples):
+
+```markdown
+## Naming Conventions
+- All fact table IDs must use the prefix `fct_` followed by the domain: e.g., `fct_sales_orders`
+- All dimension table IDs must end in `_dim`: e.g., `customers_dim`
+
+## Allowed Table Types
+- This project only uses `fact`, `dimension`, and `mart`. Do NOT use `hub`, `link`, or `satellite`.
+
+## Domain Topology
+- This project has three domains: `sales`, `marketing`, `finance`
+- Every new table MUST be assigned to one of these domains
+
+## SCD Policy
+- Dimension tables use SCD Type 1 only. Do NOT apply `scd: type2` or higher.
+```
+
+`rules.custom.md` is NOT generated by `modscape init`. Create it manually when your project needs it.
+
+---
+
+## 14. Complete Example
 
 ```yaml
 domains:

package/visualizer/package.json

@@ -1,7 +1,7 @@
 {
   "name": "visualizer",
   "private": true,
-  "version": "2.0.1",
+  "version": "2.0.2",
   "type": "module",
   "scripts": {
     "dev": "vite",