@eventcatalog/create-eventcatalog 4.2.6 → 4.2.8

package/dist/index.js

@@ -29808,7 +29808,7 @@ var import_os2 = __toESM(require("os"));
 var package_default = {
   name: "@eventcatalog/create-eventcatalog",
   description: "Create EventCatalog with one command",
-  version: "4.2.6",
+  version: "4.2.8",
   license: "MIT",
   bin: {
     "create-catalog": "./dist/index.js"
@@ -29891,6 +29891,14 @@ async function raiseEvent(eventData) {
 }
 
 // templates/index.ts
+var AGENT_RULES = `<!-- BEGIN:eventcatalog-agent-rules -->
+# EventCatalog: ALWAYS read docs before coding
+
+Before any EventCatalog work, find and read the relevant doc in \`node_modules/@eventcatalog/core/dist/docs/\`. Your training data may be outdated. The bundled docs are the source of truth.
+
+<!-- END:eventcatalog-agent-rules -->
+`;
+var CLAUDE_RULES = "@AGENTS.md\n";
 var installTemplate = async ({
   appName,
   root,
@@ -29970,6 +29978,8 @@ var installTemplate = async ({
       }
     }
   });
+  import_fs16.default.writeFileSync(import_path9.default.join(root, "AGENTS.md"), AGENT_RULES);
+  import_fs16.default.writeFileSync(import_path9.default.join(root, "CLAUDE.md"), CLAUDE_RULES);
   const cId = (0, import_uuid.v4)();
   const eventCatalogConfigPath = import_path9.default.join(root, "eventcatalog.config.js");
   let eventCatalogConfig = import_fs16.default.readFileSync(eventCatalogConfigPath, "utf8");

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@eventcatalog/create-eventcatalog",
   "description": "Create EventCatalog with one command",
-  "version": "4.2.6",
+  "version": "4.2.8",
   "license": "MIT",
   "bin": {
     "create-catalog": "./dist/index.js"

package/templates/default/domains/E-Commerce/index.mdx

@@ -68,13 +68,7 @@ The E-Commerce domain is built on the following sub domains:
   </ResourceLink>
   - Generic subscription domain handling users subscriptions
 
-## Target Architecture (Event Storming Results)
-
-Our target architecture was defined through collaborative event storming sessions with product, engineering, and business stakeholders. This represents our vision for FlowMart's commerce capabilities.
-
-<Miro boardId="uXjVIHCImos=/" moveToWidget="3074457347671667709" edit={false} />
-
-## Current Production Architecture
+## Architecture
 
 Our current event-driven architecture powering FlowMart's shopping experience:
 

package/templates/index.ts

@@ -16,6 +16,16 @@ export const getTemplateFile = ({ template, mode, file }: GetTemplateFileArgs):
   return path.join(__dirname, template, mode, file);
 };
 
+const AGENT_RULES = `<!-- BEGIN:eventcatalog-agent-rules -->
+# EventCatalog: ALWAYS read docs before coding
+
+Before any EventCatalog work, find and read the relevant doc in \`node_modules/@eventcatalog/core/dist/docs/\`. Your training data may be outdated. The bundled docs are the source of truth.
+
+<!-- END:eventcatalog-agent-rules -->
+`;
+
+const CLAUDE_RULES = '@AGENTS.md\n';
+
 /**
  * Install a Next.js internal template to a given `root` directory.
  */
@@ -132,6 +142,9 @@ export const installTemplate = async ({
     },
   });
 
+  fs.writeFileSync(path.join(root, 'AGENTS.md'), AGENT_RULES);
+  fs.writeFileSync(path.join(root, 'CLAUDE.md'), CLAUDE_RULES);
+
   const cId = v4();
 
   // update the properties in the eventcatalog.config.js