Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
2e99d36
feat: add support for spec driven dev and windows PC
matscode Oct 2, 2025
2ca76e0
feat: add support for spec driven dev
matscode Oct 3, 2025
76c6d0b
feat: new rules...
matscode Oct 3, 2025
ce07898
feat: new rules...
matscode Oct 3, 2025
8ff2e39
feat: new rules...
matscode Oct 3, 2025
0b842f9
feat: further enforce interactive input rules for IDEs
matscode Oct 3, 2025
773daf7
feat: enforce interactive input rules for consistent result
matscode Oct 3, 2025
1cfdce4
feat: enforce interactive input rules for consistent result
matscode Oct 3, 2025
92b6385
feat: add more voilation consequence and troubleshooting section
matscode Oct 4, 2025
2887d6a
feat: update persona template and examples
matscode Oct 4, 2025
d72c11f
feat: add user persona to .gitignore
matscode Oct 4, 2025
5a24ed6
feat: enforce creation of a spec file for every code change
matscode Oct 4, 2025
80044e5
feat: tackle stale file state and detailed command execution info
matscode Oct 5, 2025
3087762
feat: enforce prioritizing reading all the rules before agents gets t…
matscode Oct 5, 2025
33919a6
feat: enforce prioritizing reading all the rules before agents gets t…
matscode Oct 5, 2025
3b7139d
feat: improve interactive input
matscode Oct 5, 2025
05e646a
feat: remove command execution rules. seems not to be reliable
matscode Oct 5, 2025
8c783f5
feat: first optimization
matscode Oct 7, 2025
64b6efa
feat: changes project specs index from markdown to json
matscode Oct 7, 2025
d04fa9b
feat: add gemini config, though unstable
matscode Oct 7, 2025
6f84c40
feat: second optimized rules.
matscode Oct 7, 2025
fe473f8
feat: update rules index
matscode Oct 7, 2025
aca0813
feat: create a standalone rule
matscode Oct 8, 2025
db89d4f
feat: optimize project specs index.json for performance.
matscode Oct 8, 2025
0c9097e
feat: improve persona personalization, improve interactivity and adde…
matscode Oct 9, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .kiro/steering/rules.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# Interactive Coding Agent: Entry Point

## 🚨 MANDATORY: START HERE

**BEFORE ANY ACTION, YOU ARE REQUIRED TO:**

1. **OPEN** → **[../../rules/index.rules.md](../../rules/index.rules.md)**
2. **FOLLOW** → The mandatory onboarding process described within.

**FAILURE TO DO SO = CRITICAL VIOLATION**
29 changes: 6 additions & 23 deletions .trae/rules/project_rules.md
Original file line number Diff line number Diff line change
@@ -1,27 +1,10 @@
# Interactive Coding Agent Rules
# Interactive Coding Agent: Entry Point

🚨 **MANDATORY: YOU MUST IMMEDIATELY OPEN AND READ THE COMPLETE RULES** 🚨
## 🚨 MANDATORY: START HERE

**BEFORE ANY CODING SESSION, YOU ARE REQUIRED TO:**
**BEFORE ANY ACTION, YOU ARE REQUIRED TO:**

1. **OPEN** → **[agents/index.md](../../agents/index.md)**
2. **READ** → All mandatory standards and core principles
3. **IMPLEMENT** → Every rule and compliance checklist
1. **OPEN** → **[../../rules/index.rules.md](../../rules/index.rules.md)**
2. **FOLLOW** → The mandatory onboarding process described within.

**FAILURE TO FOLLOW THESE RULES = CRITICAL VIOLATION**

This file contains:
- ⚠️ **MANDATORY** stop points and question triggers
- 🛑 **REQUIRED** interactive command usage
- ✅ **ESSENTIAL** compliance checklists
- 🚨 **CRITICAL** violation protocols

**NO EXCEPTIONS. NO ASSUMPTIONS. FOLLOW THE RULES.**

---

*Single source of truth for maintainability - MUST be followed by all agents.*

---

*Created by [@matscode](https://www.tiktok.com/@matscode) | [LinkedIn](https://www.linkedin.com/in/matscode)*
**FAILURE TO DO SO = CRITICAL VIOLATION**
30 changes: 6 additions & 24 deletions .windsurf/rules/project_rules.md
Original file line number Diff line number Diff line change
@@ -1,31 +1,13 @@
---
trigger: always_on
---
# Interactive Coding Agent: Entry Point

# Interactive Coding Agent Rules
## 🚨 MANDATORY: START HERE

🚨 **MANDATORY: YOU MUST IMMEDIATELY OPEN AND READ THE COMPLETE RULES** 🚨
**BEFORE ANY ACTION, YOU ARE REQUIRED TO:**

**BEFORE ANY CODING SESSION, YOU ARE REQUIRED TO:**
1. **OPEN** → **[../../rules/index.rules.md](../../rules/index.rules.md)**
2. **FOLLOW** → The mandatory onboarding process described within.

1. **OPEN** → **[agents/index.md](../agents/index.md)**
2. **READ** → All mandatory standards and core principles
3. **IMPLEMENT** → Every rule and compliance checklist

**FAILURE TO FOLLOW THESE RULES = CRITICAL VIOLATION**

This file contains:
- ⚠️ **MANDATORY** stop points and question triggers
- 🛑 **REQUIRED** interactive command usage
- ✅ **ESSENTIAL** compliance checklists
- 🚨 **CRITICAL** violation protocols

**NO EXCEPTIONS. NO ASSUMPTIONS. FOLLOW THE RULES.**

---

*Single source of truth for maintainability - MUST be followed by all agents.*

---

*Created by [@matscode](https://www.tiktok.com/@matscode) | [LinkedIn](https://www.linkedin.com/in/matscode)*
**FAILURE TO DO SO = CRITICAL VIOLATION**
35 changes: 6 additions & 29 deletions AGENTS.md
Original file line number Diff line number Diff line change
@@ -1,33 +1,10 @@
# Interactive Coding Agent Rules
# Interactive Coding Agent: Entry Point

🚨 **MANDATORY: YOU MUST IMMEDIATELY OPEN AND READ THE COMPLETE RULES** 🚨
## 🚨 MANDATORY: START HERE

**BEFORE ANY CODING SESSION, YOU ARE REQUIRED TO:**
**BEFORE ANY ACTION, YOU ARE REQUIRED TO:**

1. **OPEN** → **[agents/index.md](./agents/index.md)**
2. **READ** → All mandatory standards and core principles
3. **IMPLEMENT** → Every rule and compliance checklist
1. **OPEN** → **[rules/index.rules.md](./rules/index.rules.md)**
2. **FOLLOW** → The mandatory onboarding process described within.

**FAILURE TO FOLLOW THESE RULES = CRITICAL VIOLATION**

## Complete Interactive Rules

@./agents/index.md

## Key Requirements

This file contains:
- ⚠️ **MANDATORY** stop points and question triggers
- 🛑 **REQUIRED** interactive command usage
- ✅ **ESSENTIAL** compliance checklists
- 🚨 **CRITICAL** violation protocols

**NO EXCEPTIONS. NO ASSUMPTIONS. FOLLOW THE RULES.**

---

*Single source of truth for maintainability - MUST be followed by all agents.*

---

*Created by [@matscode](https://www.tiktok.com/@matscode) | [LinkedIn](https://www.linkedin.com/in/matscode)*
**FAILURE TO DO SO = CRITICAL VIOLATION**
37 changes: 37 additions & 0 deletions GEMINI.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# Interactive Coding Agent: Entry Point

## 🚨 MANDATORY: START HERE

**BEFORE ANY ACTION, YOU ARE REQUIRED TO:**

1. **OPEN** → **[rules/index.rules.md](./rules/index.rules.md)**
2. **FOLLOW** → The mandatory onboarding process described within.

**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.
Loading