feat: optimize project specs index.json for performance.

Author: matscode

GEMINI.md

@@ -7,4 +7,31 @@
 1.  **OPEN** → **[rules/index.rules.md](./rules/index.rules.md)**
 2.  **FOLLOW** → The mandatory onboarding process described within.
 
-**FAILURE TO DO SO = CRITICAL VIOLATION**
+**FAILURE TO DO SO = CRITICAL VIOLATION**
+
+---
+
+## ⚠️ CRITICAL OVERRIDE: Interactive Input Protocol
+
+**This section overrides the interactive input instructions found in `rules/interactive-input.rules.md`.** This override specifically pertains to the *mechanism* of asking questions and does not supersede other principles of interactive input, such as clarifying ambiguity or seeking explicit approval.
+
+Due to client-side rendering limitations where `run_shell_command` (the `run_command` alternative in GEMINI's environment) causes an `InvalidStreamError` and Markdown tables are not rendered, the following protocol is the **only acceptable way** for the agent to request interactive input from the user:
+
+1.  **Format:** Questions will be presented as plain text, structured within a custom ASCII-art separator and a Markdown heading.
+2.  **Separator:** A 3-line period-based separator will be used, with the longest line being a Markdown horizontal rule (`---`).
+    *   **Opening:**
+        ```
+        .
+        ..
+        ---
+        ```
+    *   **Closing:**
+        ```
+        ---
+        ..
+        .
+        ```
+3.  **Padding:** One empty line will be placed between the opening separator and the heading, and one empty line between the question body and the closing separator.
+4.  **Heading:** A Markdown H2 heading (`## **Question Title**`) will be used.
+5.  **Body:** The question text will be formatted using supported Markdown (bold, italic, lists, blockquotes, inline code).
+6.  **Interaction:** The agent will send this formatted block as a single text response. The user will provide their answer as a plain text chat message.

README.md

@@ -59,6 +59,19 @@ Want just the essentials? Copy these:
 - **Windsurf**: Copy `.windsurf/` folder
 - **Kiro**: Copy `.kiro/` folder
 
+### Standalone Agent
+For those who prefer a single, self-contained set of rules, the `standalone-agent.rules.md` file offers a streamlined setup. Instead of copying multiple folders, you can use this single file.
+
+**Setup Instructions:**
+1.  Download the `standalone-agent.rules.md` file from this repository.
+2.  Rename it to match the filename your coding assistant requires.
+3.  Place the renamed file in your project's root directory.
+
+**Example:**
+-   If you use **Cursor** or another agent that reads from `AGENTS.md`, you would rename `standalone-agent.rules.md` to `AGENTS.md`.
+
+*This file provides a quick, single-file setup that includes all the necessary rules for persona personalization and interactive coding. However, it does not include the more advanced spec-driven development workflow available in the full rule set.*
+
 ### Rule Activation
 
 - **Close and reopen project** (optional but recommended).
@@ -69,7 +82,7 @@ Want just the essentials? Copy these:
     - "Hello"
     - "Let's make some changes"
   - **Explicit Trigger**: If the agent doesn't respond interactively, you can explicitly ask it to read the rules:
-    - "Please read the project rules first."
+    - "Read the rules"
 
 *Note: The rules must be triggered for each new chat session for the agent to follow them.*
 
@@ -130,11 +143,11 @@ The persona system ensures you get exactly the right level of detail and communi
 | **Cursor** | IDE | `AGENTS.md` | ✅ Tested |
 | **Windsurf** | IDE | `.windsurf > rules > project_rules.md` | ✅ Tested |
 | **Kiro (Vibe Mode)** | IDE | `.kiro > steering > rules.md` | ✅ Tested |
+| **Gemini** | CLI | `GEMINI.md` | ✅ Tested |
+| **Gemini Code Assist (VS Code)** | IDE | `GEMINI.md` | ✅ Tested |
 | **Codex** | IDE | `AGENTS.md` | ⏳ Not Tested Yet |
 | **Claude Code** | IDE | `AGENTS.md` | ⏳ Not Tested Yet |
 | **GitHub Copilot** | IDE | `AGENTS.md` | ❌ Not Working Yet |
-| **Gemini** | CLI | `AGENTS.md` | ❌ Not Working Yet |
-| **Gemini Code Assist (VS Code)** | IDE | `AGENTS.md` | ❌ Not Working Yet |
 
 ## 🔧 Troubleshooting
 

rules/spec-management.rules.md

@@ -64,6 +64,9 @@ Before creating any specification file, agents MUST ask these questions to ensur
 **SOURCE DOCUMENTATION:**
 - "Are there any specific articles, documentation, or resources that influenced your decision?"
 
+### 2.1 Interactive Input Compliance
+All questions in this protocol MUST comply with the rules for asking questions and handling user input as defined in `rules/interactive-input.rules.md`.
+
 ---
 
 ## 3. Specification Workflow
@@ -72,7 +75,7 @@ Before creating any specification file, agents MUST ask these questions to ensur
 
 **MANDATORY: BEFORE CREATING A NEW SPEC, YOU MUST FOLLOW THIS PROTOCOL:**
 
-1.  **Search the Spec Index:** Perform a comprehensive keyword search against the `title`, `summary`, and `keywords` fields in `project-specs/index.json` to find all potentially relevant specs.
+1.  **Search the Spec Index:** Perform a comprehensive keyword search against the `title` and `keywords` fields in `project-specs/index.json` to find all potentially relevant specs.
 
 2.  **Select Candidate Specifications:** From the search results, identify the 2-3 specs that most closely match the current requirement.
 
@@ -98,20 +101,14 @@ Before creating any specification file, agents MUST ask these questions to ensur
 
 ### Step 4: Update Index
 - **After Approval:** Once a new spec is approved, you **MUST** add a new entry to the `project-specs/index.json` file.
-- **Format:** The entry must be a JSON object with `title`, `path`, `summary`, `keywords`, and `affectedFiles` keys.
+- **Format:** The entry must be a JSON object with `title`, `path`, and `keywords` keys.
   ```json
   {
     "title": "Spec Title",
     "path": "project-specs/spec-name.spec.md",
-    "summary": "A brief, one-sentence description of the decision.",
-    "keywords": ["keyword1", "keyword2", "technology"],
-    "affectedFiles": [
-      "path/to/file-one.js",
-      "path/to/file-two.ts"
-    ]
+    "keywords": ["keyword1", "keyword2", "technology"]
   }
   ```
-- **Synchronization:** The `affectedFiles` list in this JSON entry **MUST** be identical to the list in the corresponding spec markdown file.
 
 ---
 

rules/templates/spec.template.md

@@ -1,8 +1,8 @@
 ---
 Status: [Proposed | Approved | Implemented | Deprecated]
 Related Specs:
-  - [link-to-spec-1.spec.md]
-  - [link-to-spec-2.spec.md]
+  - link-to-spec-1.spec.md
+  - link-to-spec-2.spec.md
 ---
 
 ### 1. Problem Statement