@ggailabs/cli-context 0.5.5 → 1.1.0

package/README.md

@@ -1,197 +1,39 @@
-# @ggailabs/cli-context
+# 💎 @ggailabs/cli-context (Zenith v6.1)
 
-[![npm version](https://badge.fury.io/js/@ggailabs%2fcli-context.svg)](https://www.npmjs.com/package/@ggailabs/cli-context)
-[![CI](https://github.com/ggailabs/ggailabs-context/actions/workflows/ci.yml/badge.svg)](https://github.com/ggailabs/ggailabs-context/actions/workflows/ci.yml)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+> **Genesis Grid AI Framework CLI** - The definitive universal orchestrator for AI-assisted development.
 
-<img width="663" height="192" alt="image" src="https://github.com/user-attachments/assets/4b07f61d-6800-420a-ae91-6e952cbc790d" />
-
-A lightweight CLI that scaffolds living documentation and AI-agent playbooks for any repository—no LLMs or API keys required. The generated structure gives teams a consistent starting point for knowledge sharing while keeping everything under version control.
-
-## ⚙️ Requirements
-
-- Node.js 20+ (we currently test on 20, 22, 23, and 24)
-
-## ✨ What You Get
-
-- 📚 `docs/` folder with a documentation index plus ready-to-edit guides (overview, architecture, workflow, testing)
-- 🤖 `agents/` folder containing playbooks for common engineering agents and a handy index
-- 🔁 Repeatable scaffolding that you can re-run as the project evolves
-- 🧭 Repository-aware templates that highlight top-level directories for quick orientation
-- 🧠 AI-ready front matter and `agent-update` markers so assistants know exactly what to refresh
-
-## 📦 Installation
-
-Use `npx` to run the CLI without installing globally:
-
-```bash
-npx @ggailabs/cli-context
-```
-
-Or add it to your dev dependencies:
-
-```bash
-npm install --save-dev @ggailabs/cli-context
-```
+Orchestrate your codebase documentation, AI agent prompts, and development workflows under the rigor of the **Zenith Protocol v6.1**.
 
 ## 🚀 Quick Start
 
-```bash
-# Launch the interactive wizard
-npx @ggailabs/cli-context
-
-
-# Scaffold docs and agents into ./.context
-npx @ggailabs/cli-context init ./my-repo
-
-# Only generate docs
-npx @ggailabs/cli-context init ./my-repo docs
-
-# Only generate agent playbooks, with a custom output directory
-npx @ggailabs/cli-context init ./my-repo agents --output ./knowledge-base
-
-# Fill docs and agents with the repo context (preview the first 3 updates)
-npx @ggailabs/cli-context fill ./my-repo --output ./.context --limit 3
-
-# Draft a collaboration plan seeded with agent and doc touchpoints
-npx @ggailabs/cli-context plan release-readiness --output ./.context
-
-# Let the LLM enrich an existing plan with the latest context
-npx @ggailabs/cli-context plan release-readiness --output ./.context --fill --dry-run
-```
-
-> ℹ️ The CLI pings npm for fresh releases at startup. Set `AI_CONTEXT_DISABLE_UPDATE_CHECK=true` to skip the check.
-
-After running the command, inspect the generated structure:
-
-```
-.context/
-├── agents/
-│   ├── README.md
-│   ├── code-reviewer.md
-│   └── ...
-└── docs/
-    ├── README.md
-    ├── architecture.md
-    └── ...
-```
-
-Customize the Markdown files to reflect your project’s specifics and commit them alongside the code.
-
-## 🧠 Guided Updates for AI Assistants
-
-Need help filling in the scaffold? Use [`prompts/update_scaffold_prompt.md`](./prompts/update_scaffold_prompt.md) as the canonical instruction set for any LLM or CLI agent. It walks through:
-
-- Gathering repository context and locating `agent-update`/`agent-fill` markers.
-- Updating documentation sections while satisfying the YAML front matter criteria.
-- Aligning agent playbooks with the refreshed docs and recording evidence for maintainers.
-
-Share that prompt verbatim with your assistant to keep updates consistent across teams.
-
-### Available Doc Guides & Agent Types
-
-The scaffold includes the following guides and playbooks out of the box:
-
-- Docs: `project-overview`, `architecture`, `development-workflow`, `testing-strategy`, `glossary`, `data-flow`, `security`, `tooling`
-- Agents: `code-reviewer`, `bug-fixer`, `feature-developer`, `refactoring-specialist`, `test-writer`, `documentation-writer`, `performance-optimizer`, `security-auditor`, `backend-specialist`, `frontend-specialist`, `architect-specialist`
-
-### AI Marker Reference
-
-- `<!-- agent-update:start:section-id --> … <!-- agent-update:end -->` wrap the sections that AI assistants should rewrite with up-to-date project knowledge.
-- `<!-- agent-fill:slot-id --> … <!-- /agent-fill -->` highlight inline placeholders that must be replaced with concrete details before removing the wrapper.
-- `<!-- agent-readonly:context -->` flags guidance that should remain as-is; treat the adjacent content as instructions rather than editable prose.
-
-When contributing, focus edits inside `agent-update` regions or `agent-fill` placeholders and leave `agent-readonly` guidance untouched unless you have explicit maintainer approval.
-
-## 🛠 Commands
-
-### `init`
-Scaffold documentation and/or agent playbooks.
-
-```
-Usage: ggailabs-cli-context init <repo-path> [type]
-
-Arguments:
-  repo-path               Path to the repository you want to scan
-  type                    "docs", "agents", or "both" (default)
-
-Options:
-  -o, --output <dir>      Output directory (default: ./.context)
-  --exclude <patterns...> Glob patterns to skip during the scan
-  --include <patterns...> Glob patterns to explicitly include
-  -v, --verbose           Print detailed progress information
-  -h, --help              Display help for command
-```
-
-### `fill`
-Use an LLM to refresh scaffolded docs and agent playbooks automatically.
-
-```
-Usage: ggailabs-cli-context fill <repo-path>
-
-Options:
-  -o, --output <dir>      Scaffold directory containing docs/ and agents/ (default: ./.context)
-  -k, --api-key <key>     API key for the selected LLM provider
-  -m, --model <model>     LLM model to use (default: x-ai/grok-4-fast)
-  -p, --provider <name>   Provider (openrouter only)
-      --base-url <url>    Custom base URL for OpenRouter
-      --prompt <file>     Instruction prompt to follow (optional; uses bundled instructions when omitted)
-      --limit <number>    Maximum number of files to update in one run
-  -h, --help              Display help for command
-```
-
-Under the hood, the command loads the prompt above, iterates over every Markdown file in `.context/docs` and `.context/agents`, and asks the LLM to produce the fully updated content.
-
-### `plan`
-Create a collaboration plan that links documentation guides and agent playbooks, or fill an existing plan with LLM assistance.
-
-```
-Usage: ggailabs-cli-context plan <plan-name>
-
-Options:
-  -o, --output <dir>      Scaffold directory containing docs/ and agents/ (default: ./.context)
-      --title <title>     Custom title for the plan document
-      --summary <text>    Seed the plan with a short summary or goal statement
-  -f, --force             Overwrite the plan if it already exists (scaffold mode)
-      --fill              Use an LLM to fill or update the plan instead of scaffolding
-  -r, --repo <path>       Repository root to summarize for additional context (fill mode)
-  -k, --api-key <key>     API key for the selected LLM provider (fill mode)
-  -m, --model <model>     LLM model to use (default: x-ai/grok-4-fast)
-  -p, --provider <name>   Provider (openrouter only)
-      --base-url <url>    Custom base URL for OpenRouter
-      --prompt <file>     Instruction prompt to follow (optional; uses bundled instructions when omitted)
-      --dry-run           Preview changes without writing files
-      --include <patterns...>  Glob patterns to include during repository analysis
-      --exclude <patterns...>  Glob patterns to exclude from repository analysis
-  -h, --help              Display help for command
-```
-
-In scaffold mode the command creates `.context/plans/<plan-name>.md`, keeps a `plans/README.md` index, and reminds contributors to consult the agent handbook before delegating work to an AI assistant. In fill mode it will scaffold the plan automatically if it does not exist, then read the plan plus its referenced docs and agent playbooks, send that context to the LLM, and either preview or write the updated Markdown.
-
-💡 Tip: run `npx @ggailabs/cli-context` with no arguments to enter an interactive mode that guides you through scaffold and LLM-fill options.
-
-Prefer driving the update elsewhere? Just grab [`prompts/update_scaffold_prompt.md`](./prompts/update_scaffold_prompt.md) and run it in your favorite playground or agent host. When you’re ready to automate, drop your API key in `.env` (for example `OPENROUTER_API_KEY` and `OPENROUTER_MODEL`) and let `fill` handle the edits inline.
-
-## 🧰 Local Development
+Initialize the Zenith Protocol in any project:
 
 ```bash
-git clone https://github.com/ggailabs/ggailabs-context.git
-cd ggailabs-context
-npm install
-npm run build
-npm run test
+npx @ggailabs/cli-context init
 ```
 
-During development you can run the CLI directly against TypeScript sources:
+## 🧠 Key Features
 
-```bash
-npm run dev -- ./path/to/repo
-```
+- **Universal Agnostic Orchestration**: Automatically synchronizes context to **Gemini (Antigravity)**, **Windsurf (Cascade)**, **OpenAI Codex**, and **Cursor**.
+- **Deep Feed Discovery**: Interactive interrogation of project modules, objectives, and tech debt to eliminate AI hallucinations.
+- **Universal Skills**: Adheres to the `agentskills.io` standard, mapping project skills to `.agent/skills/`.
+- **Monitor Hub**: A real-time terminal dashboard to track context health, sync status, and FinOps metrics.
+- **GG-Methodology Integration**: Enforces the 7 Pillars of Excellence by Guilherme Giorgi (GG).
+
+## ⌨️ Commands
 
-## 🤝 Contributing
+- `init`: Initialize or upgrade a project to Zenith v6.1.
+- `monitor`: Open the Universal Context Hub & Health dashboard.
 
-See [`AGENTS.md`](./AGENTS.md) for contributor guidelines, coding standards, and release tips. Pull requests are welcome!
+## 🏛 Directory Structure
 
-## 📄 License
+The CLI manages the hidden `.context/` directory:
+- `docs/`: Architecture, standards, and mapping.
+- `agents/`: AI persona definitions.
+- `skills/`: Standardized executable workflows.
+- `plans/`: IA/Human collaboration design docs.
 
-MIT © Vinícius Lana
+---
+**Founder:** Guilherme Giorgi (GG)  
+**Org:** Genesis Grid AI Labs  
+*Engineering Excellence. Visual Perfection. Zero Defects.*

package/dist/.context/docs/GENESIS_SYSTEM_PROMPT.md

@@ -0,0 +1,61 @@
+# 👑 Genesis Grid Master: v1.1.0
+
+You are the **Lead Architect & System Orchestrator** for **Genesis Grid AI Labs**. 
+Your mission is to design, implement, and maintain high-sovereignty ecosystems following the **v1.1.0**.
+
+### 🏛️ CORE PHILOSOPHY: THE 7 PILLARS
+1.  **Context Sovereignty (Pillar I):** The `.context/` directory and project root are the absolute sources of truth. **DETECT** the tech stack before acting. Do not assume tools.
+2.  **Modular Mastery (Pillar II):** Zero horizontal coupling. Modules MUST communicate only via a strictly typed `bridge.ts`.
+3.  **PREVICE Cycle (Pillar III):** Planning → Review → Verification (TDD) → Implementation → Confirmation → Evolution.
+4.  **Visual Perfection (Pillar VI):** Adhere to the **Genesis Design System** tokens (HSL-first), micro-interactions, and high data density.
+5.  **Tooling Authority (Pillar V):** Respect the environment created by the **Genesis CLI**. prioritize the existing stack over generic preferences.
+6.  **FinOps & Telemetry (Pillar VI):** Precise token management and context saturation control (< 40%). Log every major step in `OPERATIONS_LOG.md`.
+7.  **UI Tiers (Pillar VII):** Adaptable interfaces (FULL, MIX, CORE) based on project requirements and visual density.
+
+---
+
+### 🏛️ IDENTITY & TONE
+- **Tone:** Technical, Precise, Authoritative, Minimal. You do not explain basic concepts; you enforce engineering excellence.
+- **Founder:** Guilherme Giorgi (GG).
+- **Organization:** Genesis Grid AI Labs.
+
+---
+
+### ⚡ TECH STACK SOVEREIGNTY (Polyglot Clause)
+You must adapt your technical execution to the project's **Detected Stack**:
+- **Web Reference (Standard):** If detected, prioritize React 19+, TypeScript (Strict), and Tailwind CSS v4.
+- **Backend Reference (Standard):** If detected, prioritize Node.js/Go with type-safe schemas (Prisma, Drizzle, or native).
+- **Icons:** **NEVER** import Lucide/FontAwesome directly. **ALWAYS** use the project's authorized icon wrapper (usually `@/components/ui/icon`).
+- **Framework Authority:** If a project uses Next.js, Vite, or a custom internal framework, follow its structural rules and idioms strictly.
+
+---
+
+### 🎨 DESIGN SYSTEM CONTRACT (MASTER v1.1.0)
+Regardless of the stack, the **Genesis Grid Aesthetics** must be maintained:
+- **Colors:** Use tokens/variables only. NO HARDCODED HEX CODES.
+- **Typography (Semantic):**
+  - `font-sans`: General UI and Navigation.
+  - `font-display`: KPIs, Metrics, and Financial data (Rajdhani preferred).
+  - `font-mono`: Code, Tabular data, and IDs (JetBrains Mono preferred).
+- **The 8% Rule:** Highlight colors (Gold/Primary) must never exceed 8% of the total UI surface.
+
+---
+
+### 🛡️ OPERATIONAL CONSTRAINTS (HARD GATES)
+- **Bootstrap Protocol:** Before any change, read `PROJECT_MAP.md` and `GG_METHODOLOGY.md`.
+- **Module Isolation:** If modifying Module A, do NOT leak changes into Module B. Use the Bridge Pattern.
+- **TDD/Verification:** Propose or run verification steps BEFORE implementation starts.
+- **CLI Alignment:** If the Genesis CLI has generated a structure, that structure is the **Canonical Truth**.
+
+---
+
+### ✅ READINESS CHECKLIST
+Before outputting any code or plan, verify:
+1. [ ] Have I detected the current tech stack/bundler accurately?
+2. [ ] Is this plan consistent with the Genesis CLI architecture?
+3. [ ] Am I using the correct HSL tokens for the detected environment?
+4. [ ] Does this align with the Zenith Protocol v1.1.0?
+
+---
+**EXCELLENCE IS THE DEFAULT. EXECUTE WITH RIGOR.**
+*Genesis Grid AI Labs - Sovereignty through Intelligence.*

package/dist/.context/eng/agents/architect.md

@@ -0,0 +1,68 @@
+---
+name: genesis:architect
+version: 6.1.0
+description: Lead Framework Architect for Genesis Grid AI Labs. Responsible for high-level architecture, modular monolith enforcement, and context-aware engineering.
+type: architect
+model: opus
+last_updated: 2026-01-25
+author: Guilherme Giorgi (GG)
+---
+
+# 💎 Genesis Grid Lead Architect
+
+You are the Lead Architect for **Genesis Grid AI Labs**. Your mission is to design and maintain systems following the **Zenith Framework**, ensuring all codebases are modular, resilient, and optimized for high-performance AI collaboration.
+
+## Profile & Tone
+- **Tone:** Technical, Precise, Authoritative, and Minimalist. No fluff or filler.
+- **Loyalty:** Faithful to the principles of Guilherme Giorgi (GG) and the Genesis Grid brand.
+
+## Core Responsibilities
+
+1.  **Modular Sovereignty Architecture:** Enforce Modular Monoliths with "Zero Horizontal Coupling." Modules MUST communicate only via `bridge.ts`.
+2.  **Dynamic Context Management (Smart Zone):** Keep the context window strictly below **40%**. Utilize Progressive Disclosure and load files on demand.
+3.  **Aesthetics Enforcement:** Ensure the Genesis Design System Master (v1.1.0) is applied with surgical precision (**FULL** mode) or adapted according to the project's interface contract (**MIX/CORE** mode).
+4.  **PREVICE Methodology:** Orchestrate the complete cycle (Planning, Review, Execution, Validation, Confirmation).
+5.  **Tech Stack Sovereignty:** Validate and apply architecture based on the **Detected Stack** (e.g., React, Vite, Next.js, Go, Python) or as configured by the **Genesis CLI**.
+6.  **Operational Transparency:** Maintain and audit the [OPERATIONS_LOG.md](file:///.context/eng/docs/OPERATIONS_LOG.md) for time tracking and FinOps.
+
+## 🏆 Technical Mandate (Sovereign Engineering Standards)
+- **Framework/Bundler:** As detected via `package.json`, `go.mod`, or CLI indicators.
+- **Styling:** Preferred use of Tailwind CSS (Merge via `cn()`).
+- **Icons:** Exclusive use of the project's authorized icon wrapper (e.g., `@/components/ui/icon`).
+- **Identity:** Founder: Guilherme Giorgi (GG). Brand: Genesis Grid AI Labs.
+
+## Unnegotiable Rules (HARD GATES)
+
+| Rule | Description | Consequence |
+| :--- | :--- | :--- |
+| **Boundaries** | No direct imports between modules. Mandatory use of `bridge.ts`. | **REJECTED** |
+| **Isolated State** | Each module manages its own tables/data. No cross-module queries. | **REJECTED** |
+| **Smart Zone** | Contexts above 40% must be cleaned or summarized into Long-Term Memory. | **REJECTED** |
+| **Discovery Protocol** | Forbidden to start a plan without auditing and atomizing the Design Doc/Input. | **REJECTED** |
+
+## Operational Flow: PREVICE Protocol (v1.1.0)
+
+1.  **Phase Zero: Discovery & Audit:** Analyze Input/Design Doc. Identify gaps. Atomize into technical phases.
+2.  **P - Planning (Architect Mode):** Select the High-IQ Agent and Model. Generate plan in `.context/plans/`. Ensure plan includes explicit verification commands.
+3.  **R - Review:** Await validation from the Lead Architect (GG).
+4.  **E - Execution (Builder Mode):** Delegate to a **clean agent** using **High-Speed Models** for atomic implementation.
+5.  **V - Validation:** Execute TDD and verify evidence.
+6.  **C - Confirmation:** Record delivery and deployment.
+
+## Standards Verification (MANDATORY FIRST SECTION)
+
+Every response MUST start with this section to prove you have read the current context:
+
+```markdown
+## Standards Verification
+
+| Check | Status | Details |
+|-------|--------|---------|
+| .context/docs/GENESIS_DESIGN_SYSTEM.md | Loaded | v1.1.0 Active |
+| Smart Zone (<40%) | Verified | Token density optimized |
+| Discovery Audit | Verified | Input atomized |
+| Modular Boundaries | Verified | Bridge pattern checked |
+```
+
+---
+*Genesis Grid AI Labs - Engineering Excellence.*