seosona-cli 2.0.1 → 2.1.0

package/README.md

@@ -1,21 +1,16 @@
 <div align="center">
 
-```
-███████╗███████╗ ██████╗ ███████╗ ██████╗ ███╗   ██╗ █████╗      ██████╗ ███████╗
-██╔════╝██╔════╝██╔═══██╗██╔════╝██╔═══██╗████╗  ██║██╔══██╗    ██╔═══██╗██╔════╝
-███████╗█████╗  ██║   ██║███████╗██║   ██║██╔██╗ ██║███████║    ██║   ██║███████╗
-╚════██║██╔══╝  ██║   ██║╚════██║██║   ██║██║╚██╗██║██╔══██║    ██║   ██║╚════██║
-███████║███████╗╚██████╔╝███████║╚██████╔╝██║ ╚████║██║  ██║    ╚██████╔╝███████║
-╚══════╝╚══════╝ ╚═════╝ ╚══════╝ ╚═════╝ ╚═╝  ╚═══╝╚═╝  ╚═╝     ╚═════╝ ╚══════╝
-```
+<img src="https://raw.githubusercontent.com/LongLeo287/SEOSONA-OS/main/assets/logo.svg" alt="SEOSONA OS" width="800">
+
+<br/>
 
 **The Universal AI Operating System for Senior Developers**
 
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-[![Version](https://img.shields.io/badge/version-2.0.0-blue.svg)](https://github.com/LongLeo287/SEOSONA-OS)
-[![Platform](https://img.shields.io/badge/platform-Windows%20%7C%20macOS%20%7C%20Linux-lightgrey.svg)](https://github.com/LongLeo287/SEOSONA-OS)
-[![Node.js](https://img.shields.io/badge/node-%3E%3D16.0-brightgreen.svg)](https://nodejs.org)
-[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/LongLeo287/SEOSONA-OS/pulls)
+[![NPM Version](https://img.shields.io/npm/v/seosona-cli.svg?style=flat-square&color=blue)](https://www.npmjs.com/package/seosona-cli)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=flat-square)](https://opensource.org/licenses/MIT)
+[![Platform](https://img.shields.io/badge/platform-Windows%20%7C%20macOS%20%7C%20Linux-lightgrey.svg?style=flat-square)](https://github.com/LongLeo287/SEOSONA-OS)
+[![Node.js](https://img.shields.io/badge/node-%3E%3D16.0-brightgreen.svg?style=flat-square)](https://nodejs.org)
+[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](https://github.com/LongLeo287/SEOSONA-OS/pulls)
 
 *One setup. Every AI tool. Everywhere.*
 
@@ -23,6 +18,21 @@
 
 ---
 
+## 📑 Table of Contents
+- [What is SEOSONA OS?](#-what-is-seosona-os)
+- [Key Features](#-key-features)
+- [Tool Coverage](#️-tool-coverage)
+- [Installation](#-installation)
+- [Usage](#-usage)
+- [Repository Structure](#️-repository-structure)
+- [Skill Framework Library](#-skill-framework-library)
+- [How It Works — Under the Hood](#️-how-it-works--under-the-hood)
+- [Community & Standards](#-community--standards)
+- [Changelog](#-changelog)
+- [License](#-license)
+
+---
+
 ## 🧠 What is SEOSONA OS?
 
 SEOSONA OS is a **Universal AI Operating System** — a self-installing, self-scanning environment that automatically detects every AI coding tool installed on your machine and injects a unified **Master Intelligence Layer** (your `SOUL.md`) into each one.
@@ -43,7 +53,7 @@ No more copy-pasting system prompts. No more configuring each tool separately. N
 | 🧬 **DNA Injection** | Injects full `SOUL.md` content (not just a pointer) directly into each tool |
 | 🌍 **Cross-Platform** | Works on Windows (PowerShell), macOS and Linux (Node.js CLI) |
 | 🔒 **Zero Hardcodes** | All paths are computed at runtime — portable across any machine |
-| ⚡ **1-Click Setup** | Double-click `install.bat` or run `npm install -g seosona-cli` |
+| ⚡ **1-Click Setup** | Run `npm install -g seosona-cli` |
 | 🧩 **Modular Skills** | 20+ skill frameworks covering SEO, Frontend, Security, Testing, and more |
 | 🧠 **MemPalace Architecture** | Structured spatial memory system for persistent AI context |
 | 🚨 **OmniClaw Protocol** | Zero-tolerance ruleset preventing AI from bypassing workflows |
@@ -107,40 +117,27 @@ When you run `seosona init` in a project folder, it generates only the files rel
 
 ## 🚀 Installation
 
-### Method 1: Windows (PowerShell) — Recommended for Windows Users
-
-```bat
-# Double-click install.bat
-# OR run in PowerShell:
-powershell -ExecutionPolicy Bypass -File setup.ps1
-```
-
-### Method 2: Node.js CLI — Cross-Platform (Windows / macOS / Linux)
+### Method 1: NPM (Recommended — Cross-Platform)
 
 ```bash
-# Navigate to the cli/ folder
-cd cli
-
-# Install globally
-npm install -g .
+# Install the CLI globally via npm
+npm install -g seosona-cli
 
-# Run setup
+# Run the global setup wizard
 seosona setup
 ```
 
-### Method 3: Clone & Run (Any Platform)
+### Method 2: Manual Clone & Run (Developers)
 
 ```bash
 # Clone the repository
 git clone https://github.com/LongLeo287/SEOSONA-OS.git
-
-# Windows
-cd SEOSONA-OS
-powershell -ExecutionPolicy Bypass -File setup.ps1
-
-# macOS / Linux
 cd SEOSONA-OS/cli
+
+# Install globally from local source
 npm install -g .
+
+# Run setup
 seosona setup
 ```
 
@@ -152,8 +149,8 @@ seosona setup
 
 Just run setup once. SEOSONA OS handles everything automatically. Every IDE you open from that point on will operate under SEOSONA rules.
 
-```
-install.bat      ← Double-click. Done.
+```bash
+seosona setup
 ```
 
 ### For Developers (Expert Mode)
@@ -170,12 +167,7 @@ seosona init
 seosona setup    # Re-run anytime to verify state
 ```
 
-### Binding a New Project with PowerShell
 
-```powershell
-cd C:\your\project
-seosona-init
-```
 
 ---
 
@@ -209,10 +201,7 @@ SEOSONA OS/
 │   ├── errors/                       # Error reports & debug records
 │   └── ingestion_zone/              # Staging area for new knowledge
 │
-├── 📂 scripts/                       # Automation scripts
-│   ├── seosona-init.ps1             # Local project binder (PowerShell)
-│   └── rebrand_seosona.ps1          # System maintenance scripts
-│
+
 ├── 📂 cli/                           # Node.js CLI package
 │   ├── bin/seosona.js               # CLI entry point
 │   ├── src/
@@ -223,8 +212,7 @@ SEOSONA OS/
 │   └── package.json                 # npm package definition
 │
 ├── 📂 repos/                         # Tracked reference repositories
-├── 🔧 setup.ps1                      # Universal Setup Engine v2.0.0
-├── 📄 install.bat                    # One-click Windows launcher
+
 └── 📖 README.md                      # You are here
 ```
 
@@ -271,13 +259,13 @@ SEOSONA OS ships with 20+ modular skills across 5 domains:
 ### The Universal Anchor
 SEOSONA OS creates a filesystem junction at `~/.seosona` pointing to wherever the actual `SEOSONA OS` directory lives. This means:
 - All tools read from `~/.seosona` regardless of where you stored the files
-- Move the folder anywhere, re-run `setup.ps1`, the anchor updates automatically
+- Move the folder anywhere, re-run `seosona setup`, the anchor updates automatically
 - **Zero hardcoded paths anywhere in the system**
 
 ### The Injection Chain
 
 ```
-setup.ps1 (run once)
+seosona setup (run once)
     │
     ├── Reads SOUL.md (9,400+ chars of pure intelligence)
     │
@@ -313,52 +301,19 @@ The `SOUL.md` file contains the full cognitive blueprint of SEOSONA OS:
 
 ---
 
-## 🔐 Security Notes
+## 🤝 Community & Standards
 
-- **Never commit your GitHub PAT** to this repository
-- The `SOUL.md` file may contain internal SOPs — review before making the repo public
-- Environment Variables set by this tool are scoped to the **current user only** (`[Environment]::SetEnvironmentVariable(..., "User")`)
-- Run `git status` and review diffs before every push
+We welcome contributions from the community! To maintain a safe and productive environment, please review our community standards before participating:
 
----
-
-## 🤝 Contributing
-
-1. Fork this repository
-2. Create your feature branch: `git checkout -b feature/new-skill-pack`
-3. Commit your changes: `git commit -m 'Add new skill pack for X'`
-4. Push to the branch: `git push origin feature/new-skill-pack`
-5. Open a Pull Request
-
-### Adding a New Skill
-
-```
-2_KNOWLEDGE/frameworks/<domain>/<skill-name>/
-├── README.md         # Skill overview and usage
-├── SKILL.md          # Full skill prompt / SOP
-├── _DIR_IDENTITY.md  # Directory identity and scope
-├── schema.json       # Structured metadata
-└── references/       # Supporting reference files
-```
+- **[Contributing Guidelines](CONTRIBUTING.md)**: Instructions on how to submit bug reports, feature requests, and Pull Requests (including adding new skills).
+- **[Code of Conduct](CODE_OF_CONDUCT.md)**: Our pledge to maintain a welcoming, inclusive, and harassment-free community.
+- **[Security Policy](SECURITY.md)**: Instructions for reporting security vulnerabilities safely.
 
 ---
 
 ## 📋 Changelog
 
-### v2.0.0 — Omni-Scanner Release
-- ✅ Added smart detection for 14 IDE/CLI tools
-- ✅ Replaced path-pointer injection with full SOUL.md content injection
-- ✅ Built cross-platform Node.js CLI (`seosona setup`, `seosona init`)
-- ✅ Introduced `Inject-JsonSettings` generic function — eliminating 200+ lines of duplicated logic
-- ✅ Fixed `~/.git-templates` stale artifact from v1.x
-- ✅ Zero hardcoded paths — all paths computed at runtime
-- ✅ Added Antigravity IDE support via Environment Variables
-
-### v1.0.0 — Initial Release
-- ✅ PowerShell setup engine for Windows
-- ✅ Cursor, Codex, SecureCoder support
-- ✅ MemPalace spatial memory architecture
-- ✅ SOUL.md master system prompt
+Please see our dedicated [CHANGELOG.md](CHANGELOG.md) file for a detailed history of all updates and releases.
 
 ---
 

package/assets/SOUL.md

@@ -76,8 +76,8 @@ Do not summarize or paraphrase technical specifications or user guidelines. Main
 ## 4. The Master Flow Execution Enforcer
 
 For every task, execute using **The Master Flow** sequence:
-1.  **Intake & Scope:** Clean context, declare visual dials, set up `task.md` checklist. Consult the Orchestrator.
-2.  **Retrieve:** Query spatial directories, load `.aaak` closets (use MemPalace compressor tool or `context_compression` Engine if needed).
+1.  **Intake & Scope (Auto-Context Protocol):** Proactively infer the tech stack, problem domain, and required expertise at the start of every interaction without waiting for explicit keywords. Clean context, set up `task.md` checklist. Consult the Orchestrator.
+2.  **Semantic Retrieval:** Dynamically query spatial directories based on semantic intent, autonomously load relevant frameworks and skills.
 3.  **Execute & Auto-Heal:** Surgical style edits, compiler verification, autoresearch correction loop (2-Strike Rule limit).
 4.  **Deliver:** Switch sub-personas, produce raw outputs, await CEO approval. Ensure you output "TASK COMPLETED".
 
@@ -96,7 +96,7 @@ Memory synthesis is a continuous, dynamic background process ("Dreaming") rather
 ## 5. System Skills (The Arsenal)
 
 You have access to top-tier skills compressed as `.aaak` or `.md` inside `2_KNOWLEDGE/frameworks/`.
-Before executing specialized tasks (like Next.js routing, SEO tuning, UI/UX design, or Crawlee setups), you MUST load the corresponding files into your context.
+You MUST operate completely autonomously. Do NOT rely on the user to provide slash commands or exact keywords to trigger these skills. Automatically parse the user's intent and fetch the required files from the Semantic Capabilities Graph (`2_KNOWLEDGE/SKILLS_ROUTER.md`) before executing specialized tasks.
 - **Web**: `frontend_engineering/nextjs_app_router_patterns`, `frontend_engineering/react_best_practices`, `frontend_engineering/tailwind_design_system`.
 - **UI/UX**: `frontend_engineering/ui_ux_pro_max`, `frontend_engineering/frontend_ui_dark_ts`.
 - **SEO/Content**: `seo_marketing/claude_seo_framework` (NEW AI Search/E-E-A-T SOP), `seo_marketing/seo_aeo_best_practices`, `seo_marketing/landing_page_generator`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "seosona-cli",
-  "version": "2.0.1",
+  "version": "2.1.0",
   "description": "The Omni-Scanner Setup CLI for SEOSONA OS",
   "repository": {
     "type": "git",
@@ -14,6 +14,13 @@
   "bin": {
     "seosona": "./bin/seosona.js"
   },
+  "files": [
+    "bin/",
+    "src/",
+    "scripts/",
+    "assets/",
+    "README.md"
+  ],
   "scripts": {
     "prebuild": "node scripts/bundle-soul.js",
     "prepack": "npm run prebuild",

package/src/localInit.js

@@ -4,9 +4,30 @@ const os = require('os');
 const { getSoulContent, getAppDataPath, colors } = require('./utils');
 
 function runInit() {
+    const cwd = process.cwd();
+
+    // ============================================================
+    // SELF-INJECTION GUARD
+    // Prevent running `seosona init` inside the SEOSONA OS source
+    // repo itself. This would create rule files in cli/, repos/, etc.
+    // ============================================================
+    const isSeosonaSourceRepo = fs.existsSync(path.join(cwd, '1_CORE', 'SOUL.md'));
+    if (isSeosonaSourceRepo) {
+        console.log("");
+        console.log(colors.yellow("[SEOSONA] WARNING: Self-injection detected and blocked."));
+        console.log(colors.yellow("          You are running `seosona init` inside the SEOSONA OS"));
+        console.log(colors.yellow("          source repository. This is not allowed."));
+        console.log("");
+        console.log("          Run `seosona init` inside your OWN project folder instead:");
+        console.log("          > cd /path/to/your-project");
+        console.log("          > seosona init");
+        console.log("");
+        return;
+    }
+
     console.log("");
     console.log(colors.cyan("[SEOSONA] Binding project to SEOSONA OS..."));
-    console.log(colors.cyan(`  Target : ${process.cwd()}`));
+    console.log(colors.cyan(`  Target : ${cwd}`));
 
     const soulContent = getSoulContent();
     const globalPrompt = `You are the SEOSONA Master System. Your core directives are below:\n\n${soulContent}`;
@@ -27,14 +48,13 @@ function runInit() {
         filesToCreate.push(".roomodes");
     }
 
-    // 3. CLIs (Since we can't easily check Get-Command in pure JS without child_process, we check known config paths or just inject if standard)
-    // We'll just assume they might have Aider if they have .aider.conf.yml globally
+    // 3. CLIs
     if (fs.existsSync(path.join(home, ".aider.conf.yml"))) filesToCreate.push(".aider.conf.yml");
     
     // 4. OpenInterpreter
     if (fs.existsSync(path.join(appData, "Open Interpreter"))) filesToCreate.push(".openinterpreter");
 
-    // 5. Antigravity IDE
+    // 5. Antigravity IDE (always inject)
     filesToCreate.push(".antigravityrules");
 
     // 6. Project-specific Subfolders
@@ -44,7 +64,7 @@ function runInit() {
     if (fs.existsSync(".lovable")) filesToCreate.push(path.join(".lovable", "prompt"));
 
     filesToCreate.forEach(file => {
-        const fullPath = path.join(process.cwd(), file);
+        const fullPath = path.join(cwd, file);
         const dir = path.dirname(fullPath);
         
         if (!fs.existsSync(dir)) {