create-project-cortex-agent 1.0.0 → 1.0.2

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mateusz Zwierzycki
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,8 +1,10 @@
 # create-project-cortex-agent
 
+![Project Cortex](assets/hero.png)
+
 A command-line tool to instantly initialize your workspace with the **Project Cortex** AI Agent directory structure.
 
-This package bootstraps the foundational architecture needed for long-term AI-assisted development by preventing context degradation. It sets up strict boundaries, rules, and calendar-based memory logs for AI coding agents (such as Claude, Gemini, ChatGPT, or IDEs like Cursor and Copilot).
+This package bootstraps the foundational architecture needed for long-term AI-assisted development by preventing context degradation. It sets up strict boundaries, rules, and calendar-based .memory logs for AI coding agents (such as Claude, Gemini, ChatGPT, or IDEs like Cursor and Copilot).
 
 ---
 
@@ -58,11 +60,11 @@ The CLI safely injects the necessary constraints and guidelines into your reposi
 │   │   └── arch_hard_tech_stack.md      # Immutable tech stack rules for the AI
 │   └── workflows/
 │       ├── init.md                      # Workflow to start a new session
-│       └── save-memory.md               # Workflow template for memory operations
+│       └── save-memory.md               # Workflow template for .memory operations
 ├── code/
 │   └── README.md                        # Codebase operating rules for the AI
-└── memory/
-    └── README.md                        # Instructions on calendar-based long-term memory
+└── .memory/
+    └── README.md                        # Instructions on calendar-based long-term .memory
 ```
 
 ---
@@ -77,7 +79,7 @@ After running the initializer, your project is ready for smart AI assistance, bu
     > "Run Cortex" / "hey cortex, lets start" / "hey cortex, lets continue"
 
     *\*If your agent requires explicit file references (like Cursor), you can type `@init.md Run Cortex`.*
-3. **Log Your Sessions:** Simply use natural language like "that's it for today", "we are done", or "see ya later" to trigger the chronological summary in the `memory/` logs!
+3. **Log Your Sessions:** Simply use natural language like "that's it for today", "we are done", or "see ya later" to trigger the chronological summary in the `.memory/` logs!
 
 ---
 

package/dist/cli.js

@@ -63,6 +63,7 @@ program
         const dirs = [
             path.join(targetDir, '.agents', 'rules'),
             path.join(targetDir, '.agents', 'workflows'),
+            path.join(targetDir, '.memory'),
             path.join(targetDir, 'code'),
         ];
         for (const dir of dirs) {
@@ -88,8 +89,8 @@ program
                 dest: path.join(targetDir, '.agents', 'workflows', 'init.md')
             },
             {
-                src: path.join(templatesDir, 'memory', 'README.md'),
-                dest: path.join(targetDir, 'memory', 'README.md')
+                src: path.join(templatesDir, '.memory', 'README.md'),
+                dest: path.join(targetDir, '.memory', 'README.md')
             },
             {
                 src: path.join(templatesDir, 'code', 'README.md'),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-project-cortex-agent",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "CLI tool to initialize the Project Cortex agent directory structure and rules",
   "main": "dist/cli.js",
   "bin": {

package/templates/.agents/workflows/init.md

@@ -6,7 +6,7 @@ description: Bootstraps the AI's context for a new coding session.
 
 When the human says something like "Run Cortex", "hey cortex, lets start", "hey cortex, lets continue", "hey, let's start a new session", "initialize", or directly referring to this file, you must strictly follow these steps before answering any other prompt or writing any code.
 
-1. **Read System Rules:** Read the AI-only documentation in `memory/README.md`, `.agents/rules/arch_hard_tech_stack.md`, and `code/README.md`.
-2. **Contextualize Memory:** Review the `memory/` directory to understand what was done in the previous session (read the most recent log or rolling summary).
-3. **Check for Ghost Changes:** Check the state of the `code/` directory (e.g., using `git status` or `git diff`). If there are undocumented code changes that occurred after the last recorded memory log, you MUST retroactively create a `log_*.md` file summarizing those changes in the proper week's folder.
+1. **Read System Rules:** Read the AI-only documentation in `.memory/README.md`, `.agents/rules/arch_hard_tech_stack.md`, and `code/README.md`.
+2. **Contextualize .memory:** Review the `.memory/` directory to understand what was done in the previous session (read the most recent log or rolling summary).
+3. **Check for Ghost Changes:** Check the state of the `code/` directory (e.g., using `git status` or `git diff`). If there are undocumented code changes that occurred after the last recorded .memory log, you MUST retroactively create a `log_*.md` file summarizing those changes in the proper week's folder.
 4. **Ready:** Acknowledge you have loaded the context and ask the user what they want to work on.

package/templates/.agents/workflows/save-memory.md

@@ -1,8 +1,8 @@
 ---
-description: Trigger memory rollup on natural language '/save-memory' or 'thats it for today'
+description: Trigger .memory rollup on natural language '/save-.memory' or 'thats it for today'
 ---
 
-# Save Memory Workflow
+# Save .memory Workflow
 
 ## Triggers
 The user signals the end of a chat session using phrases like:
@@ -14,6 +14,6 @@ The user signals the end of a chat session using phrases like:
 ## Execution
 When the above intent is detected:
 1. Generate an overview log of the current conversation.
-2. Store this log inside `memory/` or update `.agents/rules/` if an architecture rule changed.
+2. Store this log inside `.memory/` or update `.agents/rules/` if an architecture rule changed.
 3. Archive older logs to ensure a maximum of 30 active files in the working directory.
-4. Announce that the session memory has been effectively committed.
+4. Announce that the session .memory has been effectively committed.

package/templates/{memory → .memory}/README.md

@@ -1,13 +1,13 @@
-# Memory Context
+# .memory Context
 
 > **Important: [AI-ONLY SYSTEM INSTRUCTION]**
-> This file establishes the operational requirements for AI agents managing the project's memory. Humans do not need to read or edit this file unless fundamentally changing the rules of the template.
-> This folder stores conversation logs organized into a nested calendar structure, acting as the long-term memory for the AI.
+> This file establishes the operational requirements for AI agents managing the project's .memory. Humans do not need to read or edit this file unless fundamentally changing the rules of the template.
+> This folder stores conversation logs organized into a nested calendar structure, acting as the long-term .memory for the AI.
 
 ## Folder Hierarchy
 
 * **`.agents/rules/`**: Holds system constraints, architectural rules, and core states that bypass all standard archiving rules. These files are permanently kept.
-* **`memory/[YYYY]/`**: The root folder for a given year.
+* **`.memory/[YYYY]/`**: The root folder for a given year.
     * `year_[YYYY].md`: Annual summary of the months.
     * **`[MM]/`**: Folder for the month (01 to 12).
         * `month_[YYYY]-[MM].md`: Monthly summary of the weeks.
@@ -22,7 +22,7 @@
 3.  **Month (Summarization):** At the month's end, the `week_` summaries are synthesized into `month_[YYYY]-[MM].md`.
 4.  **Year (Summarization):** At the year's end, the `month_` summaries are synthesized into `year_[YYYY].md`.
 5.  **Overrides:** Files in `.agents/rules/` are permanently kept and NEVER summarized or deleted by the calendar cleanup process.
-6.  **Session Termination Trigger:** Whenever the human user uses natural language indicating the end of a session (e.g., "that's it for today", "we are done", "wrap it up", "see ya later"), you MUST automatically initiate the memory rollup process, generating the required summaries and `log_` files in the `memory/` directory.
+6.  **Session Termination Trigger:** Whenever the human user uses natural language indicating the end of a session (e.g., "that's it for today", "we are done", "wrap it up", "see ya later"), you MUST automatically initiate the .memory rollup process, generating the required summaries and `log_` files in the `.memory/` directory.
 7.  **Auto-Recovery (Missing Logs):** If you are initialized in a new session and detect that the `code/` directory contains updates, new files, or Git changes that are NOT documented in the most recent `log_` or `week_` file, you must assume the previous session ended without a proper rollup. You MUST immediately analyze the undocumented code changes and generate a retroactive `log_` file summarizing them before proceeding with new human requests.
 
 ## Mandatory Formatting & Retention Rules
@@ -36,4 +36,4 @@ To prevent knowledge loss and context degradation during the summarization proce
     * **Context & Notes:** Any specific commands, environment variables, or quirks needed to run the current codebase.
 * **Critical Retention Tags:** If a raw daily log or a lower-level summary contains the tag `[CRITICAL_DECISION]` or `[ADR]`, the exact text associated with that tag MUST be copied verbatim into the higher-level summaries. Do not paraphrase or compress these points.
 * **Task Rollover:** Any incomplete tasks or open bugs mentioned in the active period MUST be explicitly listed under "Unresolved Issues & WIP" in the newly generated summary so the next AI session can immediately resume work.
-* **Knowledge Extraction:** While summarizing at the end of a week/month, if a core architectural pattern, tech stack, or global rule has changed, you MUST automatically update the relevant files in `.agents/rules/` to reflect the current state of the project.
+* **Knowledge Extraction:** While summarizing at the end of a week/month, if a core architectural pattern, tech stack, or global rule has changed, you MUST automatically update the relevant files in `.agents/rules/` to reflect the current state of the project.