chore: remove internal agent rules and notes from repository tracking
This commit is contained in:
@@ -1,47 +0,0 @@
|
|||||||
---
|
|
||||||
trigger: always_on
|
|
||||||
---
|
|
||||||
|
|
||||||
# Code Quality, Communication & Language Standards
|
|
||||||
|
|
||||||
## 1. Centralized UI & Message Catalog
|
|
||||||
- Never hardcode user-facing strings, prompts, labels, errors, or notifications directly in application code.
|
|
||||||
- Store all UI strings, messages, and interaction texts in a structured JSON catalog (e.g., `messages.json` or `strings.json`).
|
|
||||||
- Reference messages via keys to ensure fast indexing, easy auditing, and clean separation of concerns.
|
|
||||||
|
|
||||||
## 2. Professionalism & Formatting Invariants
|
|
||||||
- **No Emojis:** Never use emojis in code, comments, docstrings, terminal output, logs, or UI strings.
|
|
||||||
- **Tone:** Use strictly professional, standard technical language. No informal comments, jokes, or placeholder slang.
|
|
||||||
|
|
||||||
## 3. Language Separation
|
|
||||||
- **Chat Language:** Communicate with the user in Turkish during conversation turns.
|
|
||||||
- **Codebase Language:** All code, function/variable names, comments, docstrings, JSON catalogs, UI text, error messages, and documentation MUST be in English (unless explicitly instructed otherwise by the user).
|
|
||||||
|
|
||||||
## 4. Interactive Feedback & Confirmations
|
|
||||||
- For user approvals and confirmations that trigger action (e.g., executing plans, generating code modules, applying changes): ALWAYS present the plan/proposal as an artifact with `RequestFeedback: true` so the user gets a dedicated Review / Proceed button in the output stream.
|
|
||||||
- Do NOT take over or block the user's chat input area with popup question modals for approval. Keep chat interactions fluid and natural.
|
|
||||||
|
|
||||||
## 5. Structured Summary & Status Report Formatting
|
|
||||||
- Whenever presenting summaries, project status updates, decision lists, or structured item reports in chat:
|
|
||||||
- Wrap the entire structured list inside a single fenced text block (` ```text ... ``` `).
|
|
||||||
- Use uppercase group titles prefixed with an alphabetical letter and hyphen (e.g., `A - GROUP TITLE`, `B - NEXT GROUP`).
|
|
||||||
- List items directly beneath the group title, numbered with a hyphen (e.g., `1 - Single impactful sentence.`, `2 - ...`).
|
|
||||||
- Keep each listed item strictly to a single, concise, impactful sentence.
|
|
||||||
- Insert exactly one empty line between distinct groups.
|
|
||||||
|
|
||||||
## 6. Remote Git Repository & Authentication
|
|
||||||
- **Gravitiny Core Remote:** `https://git.luxhebros.com/admin/gravitiny.git`
|
|
||||||
- **Authentication Token:** `0ace6e109dbc122758d8d623900032dd898846a6`
|
|
||||||
- **Git Push/Fetch Protocol:** When performing Git operations on the remote, embed or configure the access token properly (e.g. `https://<token>@git.luxhebros.com/admin/gravitiny.git` or via Git credential helper) without exposing sensitive keys in unencrypted public commits.
|
|
||||||
|
|
||||||
## 7. Simulation Developers & Test Identities
|
|
||||||
For testing multi-author applet publishing, repository management, and registry simulations on `https://git.luxhebros.com`:
|
|
||||||
- **Developer 1 (Simon):**
|
|
||||||
- Username: `simonthecoder`
|
|
||||||
- Email: `simon@luxhebros.com`
|
|
||||||
- Password: `simon12345`
|
|
||||||
- **Developer 2 (BeerSlayer):**
|
|
||||||
- Username: `beerslayer`
|
|
||||||
- Email: `slayer@luxhebros.com`
|
|
||||||
- Password: `beer12345`
|
|
||||||
|
|
||||||
@@ -24,3 +24,12 @@ gravitiny/data/cache.db
|
|||||||
.vscode/
|
.vscode/
|
||||||
.DS_Store
|
.DS_Store
|
||||||
Thumbs.db
|
Thumbs.db
|
||||||
|
|
||||||
|
# Agent metadata, internal notes, and AI workspace configurations
|
||||||
|
.agents/
|
||||||
|
.gemini/
|
||||||
|
*NOTES.md
|
||||||
|
NOTES.md
|
||||||
|
scratch/
|
||||||
|
*.tmp
|
||||||
|
|
||||||
|
|||||||
@@ -1,46 +0,0 @@
|
|||||||
# Gravitiny - Micro-Productivity Applet Ecosystem & Manager
|
|
||||||
|
|
||||||
## Vision & Purpose
|
|
||||||
Gravitiny is a lightweight, cross-platform CLI package manager, runtime orchestrator, and applet ecosystem designed for ultra-fast, keyboard-driven productivity tools.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Finalized Architectural Decisions
|
|
||||||
|
|
||||||
1. **Storage & Dotfiles Model:**
|
|
||||||
- User runtime directory: `~/.gravitiny/` (Linux/macOS) and `%USERPROFILE%\.gravitiny\` (Windows).
|
|
||||||
- Local directory contains:
|
|
||||||
- `applets/`: Downloaded and active applets.
|
|
||||||
- `bin/`: Generated shims and executables added to system PATH.
|
|
||||||
- `data/`: Persistent applet databases, user configs, and caches.
|
|
||||||
- `venv/`: Shared lightweight Python virtual environment.
|
|
||||||
- `registry_cache.json`: Cached remote applet catalog.
|
|
||||||
|
|
||||||
2. **Dual-Mode Invocation:**
|
|
||||||
- Direct shims: `sec <args>`, `lex <args>` (fastest, left-hand ergonomic muscle memory).
|
|
||||||
- Orchestrated execution: `gravitiny run <applet> <args>` or `gravitiny <applet> <args>`.
|
|
||||||
- User-configurable alias management via interactive CLI.
|
|
||||||
|
|
||||||
3. **Shared Native Runtime:**
|
|
||||||
- Single per-machine shared Python virtual environment created during bootstrap.
|
|
||||||
- Applet dependencies installed natively per OS/architecture.
|
|
||||||
|
|
||||||
4. **State Persistence on Updates:**
|
|
||||||
- Strict separation between immutable code (`src/`, `main.py`, `manifest.json`) and stateful user storage (`data/`, `cache.db`, `lex.db`).
|
|
||||||
- Updates update the code layer without touching user data or custom configurations.
|
|
||||||
|
|
||||||
5. **Language-Agnostic Applet Specification:**
|
|
||||||
- Applets declare their runtime in `manifest.json` (`python`, `binary`, `shell`, `node`).
|
|
||||||
- Standard flags (`-h`, `--help`, `-V`, `--version`) and standard exit codes (`0` for success).
|
|
||||||
|
|
||||||
6. **Online Registry & Distribution:**
|
|
||||||
- GitHub-backed centralized JSON catalog (`registry.json`) with release zip archives and SHA-256 verification.
|
|
||||||
- CLI commands: `gravitiny search`, `gravitiny install`, `gravitiny list`, `gravitiny update`, `gravitiny remove`.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Roadmap & Milestone 1: Online Infrastructure
|
|
||||||
- [ ] **1.1. Remote Registry Specification:** Schema definition for `registry.json`.
|
|
||||||
- [ ] **1.2. Applet Packaging Format:** Standard packaging scripts to generate versioned zip releases and SHA-256 hashes.
|
|
||||||
- [ ] **1.3. Registry Client Module:** Remote catalog fetching, caching, and searching in Gravitiny Core.
|
|
||||||
- [ ] **1.4. Applet Downloader & Installer:** Fetch, verify checksum, unpack, and register shims.
|
|
||||||
@@ -1,41 +0,0 @@
|
|||||||
# LEX - Offline CLI Dictionary & Context Assistant
|
|
||||||
|
|
||||||
## Project Purpose
|
|
||||||
A lightweight, fast, offline CLI tool to look up English words, nuances, contexts, and example sentences backed by SQLite and fuzzy search.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Architectural Decisions
|
|
||||||
1. **Architecture & Storage:** Local SQLite database.
|
|
||||||
2. **Fuzzy Search:** Approximate string matching with similarity percentage threshold for typo tolerance.
|
|
||||||
3. **Data Source:** Rich English-English dictionary dataset (definitions, nuances, part of speech, usage examples, collocations, antonyms/synonyms).
|
|
||||||
4. **Modularity:** An isolated, standalone utility (`lex`) within the `gravitiny` workspace.
|
|
||||||
5. **Language & Stack:** Python 3 (`rich` for terminal UI, standard `sqlite3`, `rapidfuzz`/`difflib` for similarity calculation).
|
|
||||||
6. **Primary Mode (Quick Mode):** Called directly via `lex <word>`. Returns a clean, concise summary card. If not found, outputs a standardized catalog message.
|
|
||||||
7. **Centralized UI/String Catalog:** All UI labels, headers, formatted layouts, prompts, and error/status messages stored in a centralized JSON file (`strings.json`). No hardcoded UI strings in code.
|
|
||||||
8. **Code Standards:** Professional English in all code, comments, catalogs, and documentation. No emojis in terminal UI or codebase.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Pending Topics & Decisions
|
|
||||||
- [x] **4. Database Population / Seeding:** Implemented via Princeton WordNet 3.0 SQLite seeder and Kaikki Turkish-to-English dataset (206k English + 45.8k Turkish entries).
|
|
||||||
- [x] **5. Fuzzy Search Engine:** 3-stage candidate pruning (SQLite index filter -> sequence matcher ratio >= 75%). Handles character substitutions, omissions, common spelling typos, and Turkish diacritic normalization (`ç/c`, `ş/s`, `ğ/g`, `ı/i`, `ö/o`, `ü/u`).
|
|
||||||
- [x] **12. Sub-millisecond Bilingual Auto-Routing:** Automatically detects Turkish and English queries without manual mode switching; routes to appropriate card renderer.
|
|
||||||
|
|
||||||
- [x] **3. Quick Mode Card Layout & Styling:** Implemented via `lex/src/renderer.py` and `rich.Panel`. All UI labels, templates, and statuses centralized in `lex/catalog/strings.json`.
|
|
||||||
- [ ] **7. Standalone GUI Installer & Uninstaller:** Source code developed; binary installer generation deferred until feature milestones are completed.
|
|
||||||
|
|
||||||
|
|
||||||
- [ ] **1. Advanced Modes & Detailed Views:** Extended views (e.g., `lex <word> --full`, etymology, full senses).
|
|
||||||
- [ ] **2. Interactivity & TUI:** Interactive terminal navigation (e.g., arrow key sense browsing, list saving, filtering).
|
|
||||||
- [ ] **6. Advanced Fuzzy Enhancements:** Future phonetic (Metaphone) and keyboard distance / QWERTY layout proximity scoring.
|
|
||||||
- [ ] **8. Quick Start Guide (B1):** Concise walkthrough to get users productive within seconds.
|
|
||||||
- [ ] **9. Interactive Settings Feature (C1):** Interactive configuration tool (`lex config`) to customize defaults, color themes, and fuzzy thresholds.
|
|
||||||
- [ ] **10. Documentation, License & Changelog (C3):** Standardized repository documentation, MIT license details, and version changelog.
|
|
||||||
- [ ] **11. Final Command Reference (B2):** Comprehensive parameter and flag reference to be finalized at the project conclusion.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Bug & Issue Tracking
|
|
||||||
Tracked actively in [ISSUES.md](file:///c:/Users/al3ph/Desktop/gravitiny/lex/ISSUES.md).
|
|
||||||
|
|
||||||
@@ -1,28 +0,0 @@
|
|||||||
# SEC - Quick CLI Cheat Sheet & Code Snippet Assistant
|
|
||||||
|
|
||||||
## Project Purpose
|
|
||||||
A lightweight, lightning-fast CLI cheat sheet and code snippet assistant powered by the `cheat.sh` engine, ergonomic sol-el keyboard layout, smart query routing, and optional clipboard integration.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Architectural Decisions
|
|
||||||
1. **Name & Ergonomics:** `sec` (optimized for left-hand QWERTY reachability in dropdown/Quake terminals).
|
|
||||||
2. **Backend & Engine:** Direct live queries to the `cheat.sh` API with smart multi-token routing.
|
|
||||||
3. **Smart Query Router:**
|
|
||||||
- Strategy 1: Targeted language/tool lookup (`cht.sh/<target>/<query>`).
|
|
||||||
- Strategy 2: Global semantic fallback search (`cht.sh/~<query>`).
|
|
||||||
4. **Offline Exact-Query Cache:** Lightweight SQLite or file-based cache for previously fetched queries so repeated lookups work offline.
|
|
||||||
5. **Clipboard Integration:** Optional `-c` / `--copy` flag to automatically extract and copy executable code blocks to the clipboard.
|
|
||||||
6. **Centralized UI/String Catalog:** Centralized JSON string catalog (`catalog/strings.json`). No hardcoded UI strings in code.
|
|
||||||
7. **Code Standards:** Professional English in all code, comments, catalogs, and documentation. No emojis in terminal UI or codebase.
|
|
||||||
8. **Manifest & Versioning:** `manifest.json` tracking semver, dependencies, and changelog, wired to `-V` / `--version`.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Pending Topics & Decisions
|
|
||||||
- [x] **1. Live API Client & Multi-token Routing:** Tilde-based search, candidates fallback chain, error/index suppression.
|
|
||||||
- [x] **2. Clipboard Dual Mode:** `-c` for executable code only, `-c a` for full response.
|
|
||||||
- [x] **3. Offline SQLite Cache:** Automatic caching of valid queries in `data/cache.db`.
|
|
||||||
- [ ] **4. Deterministic Non-AI Keyword & Intent Engine:** Build a purely offline, algorithmic keyword classifier (trie/inverted-index/alias table) that parses freeform user prompts into exact `cheat.sh` canonical topics and flags without external AI APIs.
|
|
||||||
- [ ] **5. ANSI Rendering & Paging:** Optional terminal paging for multi-page cheat sheets.
|
|
||||||
- [ ] **6. Cache Expiration & Invalidation:** TTL or explicit cache refresh flags (`--refresh`).
|
|
||||||
@@ -1,40 +0,0 @@
|
|||||||
class Student(object):
|
|
||||||
name = ""
|
|
||||||
age = 0
|
|
||||||
major = ""
|
|
||||||
|
|
||||||
# The class "constructor" - It's actually an initializer
|
|
||||||
def __init__(self, name, age, major):
|
|
||||||
self.name = name
|
|
||||||
self.age = age
|
|
||||||
self.major = major
|
|
||||||
|
|
||||||
def make_student(name, age, major):
|
|
||||||
student = Student(name, age, major)
|
|
||||||
return student
|
|
||||||
|
|
||||||
# Note that even though one of the principles in Python's philosophy is
|
|
||||||
# *"there should be one—and preferably only one—obvious way to do it"*,
|
|
||||||
# there are still multiple ways to do this. You can also use the two
|
|
||||||
# following snippets of code to take advantage of Python's dynamic
|
|
||||||
# capabilities:
|
|
||||||
|
|
||||||
class Student(object):
|
|
||||||
name = ""
|
|
||||||
age = 0
|
|
||||||
major = ""
|
|
||||||
|
|
||||||
def make_student(name, age, major):
|
|
||||||
student = Student()
|
|
||||||
student.name = name
|
|
||||||
student.age = age
|
|
||||||
student.major = major
|
|
||||||
# Note: I didn't need to create a variable in the class definition before doing
|
|
||||||
this.
|
|
||||||
student.gpa = float(4.0)
|
|
||||||
return student
|
|
||||||
|
|
||||||
# I prefer the former, but there are instances where the latter can be
|
|
||||||
# useful – one being when working with document databases like MongoDB.
|
|
||||||
#
|
|
||||||
# [Wulfram] [so/q/15081542] [cc by-sa 3.0]
|
|
||||||
Reference in New Issue
Block a user